Diagnostics: checking your install

Open Settings → Diagnostics and press “Run checks”. It takes a few seconds. Nothing is sent anywhere — the results stay on that screen until you choose to copy them. If the app will not open far enough to reach Settings, you can run the same checks from a terminal with the --doctor flag, which prints the report and exits.

“Copy report” puts a text version on your clipboard, with API keys, tokens, email addresses and file paths removed — only the filename at the end of a path is kept, because that is the part that identifies the problem rather than you. Paste it into your support message; it saves the round trip of us asking which version and platform you are on.

Green means the check passed. Amber means something is degraded but not blocking — for example, the model catalogue could not refresh, so the picker is working from the list bundled inside the app and may be missing very new models. Red means something is broken that you cannot work around, and the row tells you what to do about it.

The Atlarix Core row tells three different problems apart: not signed in, our proxy unreachable, and a credit balance of $0.00. Your own API keys and local models keep working in all three cases. The API keys row checks each key you have saved by asking its provider for a model list — never by generating anything, so running diagnostics never costs you money. A key that worked yesterday and fails today has usually been revoked, expired, or run out of quota at the provider; re-enter it under Settings → AI.

These four check the pieces that ship inside the app: bundled ripgrep (how the agent searches your code), the terminal spawn helper, the native SQLite module, and the local proxy worker. A failure in any of them means a broken or partial install, and the fix is to reinstall Atlarix. Your workspaces, chats and settings live outside the app, so they survive a reinstall. If your organisation strips bundled binaries from applications, ripgrep and the terminal helper are the files to allow-list.

This checks that your operating system's keychain can encrypt and decrypt — which is how saved API keys and your sign-in survive a restart. A throwaway value is used; nothing real is decrypted. If it fails, keys and sign-ins will not persist between launches. On macOS this usually means the keychain denied access to the app.

Shell commands normally run inside a per-OS sandbox that confines writes to your workspace. If this row is red, commands still run — but without that confinement, so approve them more carefully until it is fixed. On Windows it is usually a privilege the account does not hold. See the approvals guide for how the sandbox and approvals fit together.

The update section at the bottom of the panel shows your current version, when Atlarix last checked, and what it found, with a button to check now and to install a downloaded update. If it reports that automatic updates are unavailable, download the current installer from atlarix.dev and install once — that heals the updater for every release after it.