> Documentation index: https://docs.kiste.run/llms.txt, a list of every page in this documentation.

# Support

> How to get help, and what to include so a problem can be found fast.

Write to [luka@lukaloehr.com](mailto:luka@lukaloehr.com). For bugs in the CLI,
you can also open an issue in its repository once it is public.

## What to include

Every error in Kiste carries a **code** and a **request ID**; with both, the
problem can be found in minutes:

```text
× kiste.run can't reach the compute service right now. Your Kisten are safe. (code: N01)
  hint Try again in a minute.
  request: 01J9Z8X7W6V5T4S3R2Q1P0N9M8
```

Please send:

1. the **error code** and the **request ID** (the console shows both in its
   error messages too);
2. what you did, such as the command you ran (`kiste --version` tells the CLI
   version);
3. the name of the Kiste, when one is involved;
4. for desktop problems: your browser and system, and the connection details
   from the viewer's overlay.

`kiste doctor` output and a run with `--verbose` help with connection
problems. Never send passwords, API keys or the contents of `session.json`.

## Before you write

- [Errors](https://docs.kiste.run/errors.md) explains every code and its fix.
- [Status](https://docs.kiste.run/resources/status.md) shows ongoing incidents.
- [Security issues](https://docs.kiste.run/security.md) are reported differently; see the security
  section.

## Related topics

- [Status](https://docs.kiste.run/resources/status.md)
- [Changelog](https://docs.kiste.run/resources/changelog.md)
- [Glossary](https://docs.kiste.run/resources/glossary.md)
- [Legal](https://docs.kiste.run/resources/legal.md)
- Previous: [Status](https://docs.kiste.run/resources/status.md)
- Next: [Changelog](https://docs.kiste.run/resources/changelog.md)