> For the complete documentation index, see [llms.txt](https://docs.telys.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.telys.ai/resources/support.md).

# Support

Telys is in public beta. This page lists the ways to get help and what to attach so a first reply is useful.

## Where to get help

| Channel         | Use it for                                                | Link                                         |
| --------------- | --------------------------------------------------------- | -------------------------------------------- |
| Email           | Bugs, questions, licensing, anything with account details | <eng@thyn.ai>                                |
| Contact form    | General and enterprise / licensing enquiries              | [telys.ai/contact](https://telys.ai/contact) |
| Accounts portal | Sign-in, subscription, device management                  | [accounts.thyn.ai](https://accounts.thyn.ai) |
| Documentation   | How-tos, references, troubleshooting                      | [docs.telys.ai](https://docs.telys.ai)       |

## Try troubleshooting first

Many issues have a documented fix. Before filing, skim [Troubleshooting](/troubleshooting/overview.md) — it covers [install & runtime](/troubleshooting/install-and-runtime.md), [license & login](/troubleshooting/license-and-login.md), [signature verification](/troubleshooting/signature-verification.md), [poor recall](/troubleshooting/search-and-recall.md), [dimension mismatches](/troubleshooting/dimension-mismatches.md), and [MCP client](/troubleshooting/mcp-client.md) problems.

## File a good bug report

Email <eng@thyn.ai> with the details below, or use the [contact form](https://telys.ai/contact). Keep account and license details to email so they stay private.

{% hint style="warning" %}
Never include secrets. Do not paste API keys, license tokens (`login_license.jwt`), or access tokens into an issue. Redact `$TELYS_API_KEY`, `$TELYS_TOKEN`, `$TELYS_ACCESS_TOKEN`, and `$TELYS_LICENSE` before sharing logs.
{% endhint %}

Include the essentials so we can reproduce:

{% stepper %}
{% step %}

#### Capture your versions

Run these and paste the output.

```bash
telys version           # e.g. telys 0.1.0b2 (format v1)
telys runtime status    # 0 = ready, 1 = not installed
python3 --version
```

{% endstep %}

{% step %}

#### Confirm the runtime is trusted

A verification failure explains a whole class of errors.

```bash
telys runtime verify
```

{% endstep %}

{% step %}

#### Describe what happened

State your OS and architecture (for example `macos-arm64` or `linux-x86_64`), the exact command or code you ran, the full error text, and what you expected. A minimal snippet that reproduces the problem beats a description.
{% endstep %}
{% endstepper %}

## What you will get back

A pointer to the fix or the relevant docs page, a request for more detail, or — for a confirmed bug — confirmation that we have logged it. Licensing and subscription questions are handled over email and the [accounts portal](https://accounts.thyn.ai).

## Next steps

* [Resources & links](/resources/resources.md) — every official Telys link in one place.
* [FAQ](/resources/faq.md) — the fastest answers to common questions.
* [Troubleshooting](/troubleshooting/overview.md) — self-serve fixes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.telys.ai/resources/support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.