TALKTOAI

Practical guides · Start here

Help us reproduce the problem

A small, clear report is often more useful than a large log. Include what happened, what you expected and the steps that connect them.

Choose the right project

Search existing issues for the same error before opening a new one. If it is already reported, add your version and any new steps that help reproduce it.

Include these details

  1. App and version. Add the installed version, operating system and whether you use Microsoft Store, a direct installer or a source build.
  2. What you tried. Number the smallest sequence of actions that reproduces the problem, beginning from a clear state.
  3. Expected result. Describe the result you were trying to achieve in one sentence.
  4. Actual result. Copy the relevant error text or explain the visible behaviour. Say whether it happens every time.
  5. AI route, when relevant. State local, self-hosted or API; include runtime version and non-secret model ID. Say whether the runtime itself responds independently.
  6. Recent changes. Mention an app update, changed route or relevant setting if the issue started afterward.

Copy this report outline

App and installed version:
Installation channel:
Operating system:

Steps to reproduce:
1.
2.
3.

Expected result:
Actual result / relevant error:
How often it happens:

Model route and runtime version (if relevant):
Does a harmless prompt work directly in the runtime?
Recent changes:
Redacted screenshot or minimal example (optional):

Public issues are visible to other people. Remove API keys, tokens, email contents, private prompts, personal files and identifying paths before posting. Prefer a made-up sample that reproduces the issue. Do not attach an entire project or configuration folder.

Make the example smaller

If a project task fails, try it with a new disposable folder and a small text file. If a model connection fails, try a harmless prompt in the runtime first. This helps distinguish a runtime problem from an app connection problem without exposing your actual work.

A screenshot should show the relevant error and nearby controls. Crop account information and private content. Logs can include sensitive text; share only a short redacted excerpt needed to understand the failure.

Privacy questions and sensitive reports

For privacy questions or a concern that should not be placed in a public issue, use [email protected] with a brief description. Start without secrets or private attachments. Email is a contact route and does not imply a guaranteed response time.