Check your setup and report a problem

What is ready, what is missing

talos doctor            # one line per check: runtime, folders, providers, credentials, catalog
talos doctor --json     # the same, for a script

/doctor runs the same checks from the interactive screen. For one provider, talos provider test <provider> says whether it answers, its latency and what to do.

When something fails

• --verbose shows more detail, with the trace id.
• talos logs --tail 100 prints the last lines of each log file.
• The exit code says how a run ended: see Exit codes.

Report a bug

talos diagnostic bundle --out talos-diagnostic.zip

It writes a ZIP with the doctor report, the effective configuration and the last 200 log lines — secrets removed and paths replaced, and no prompt or file content. Attach it to your report.

A newer version

talos update --check

With an npm install, talos update says whether a newer version exists and prints the command to run (npm i -g talos-code@latest); it changes nothing by itself.

Known limits

• Only Windows 11 x64 is tested; macOS and Linux are not yet.
• Context compaction with a local Ollama model is not yet verified end to end.
• A local provider that answers 401 or 403 without needing a key can be set aside as if its key were wrong.