Troubleshooting

No agent in the picker (or greyed out)

AI Chat only lists agents it finds installed. An agent shows "— not installed" when its CLI isn't on your PATH.

Install and sign in to one: Set up an AI agent.
Claude Code and Codex also need Node.js (for npx) — if npx is missing they won't launch even when the CLI is installed. GitHub Copilot CLI and OpenCode don't need Node.
After installing, reopen the picker (or restart the app) so it re-scans.

"AI Chat is available in the desktop app" / host unavailable

AI Chat runs against a small local host that ships only with the desktop app.

Make sure you're in the desktop app, not a browser build.
If it was working and stopped, restart the desktop app to relaunch the host.

The agent uses the session you created in your terminal — not a key stored in DBConvert. Re-run its sign-in and try again:

claude            # then /login
codex login
copilot           # then /login
opencode auth login

A tool card shows "failed" (red)

Each answer shows the read-only tools the agent called. A single failed card is usually harmless — the agent probes, absorbs the result, and still answers. Common benign cases:

Listing databases on a files connection — file connections have no databases, so that call is expected to fail; the agent moves on.
A first query the agent then corrects and re-runs.

If a tool fails every time for a database operation and the answer suffers, capture the chat (↓ → Download .md) and report it.

The agent forgot our conversation

Returning after a while: older chats are put to sleep to save resources and reattached with their memory when you return — with one exception: GitHub Copilot CLI can't reattach, so a slept Copilot chat resumes as a fresh session (the transcript stays on screen, but the agent no longer remembers it). Switch to another provider if cross-session memory matters.
After restarting the app: sessions don't survive an app restart; the transcript is kept, but the agent starts fresh.
New (header) intentionally starts over in the current scope.

Switching provider cleared my chat

Expected — a different provider is a different agent process, so it resets the conversation. AI Chat warns first when there's history; ↓ → Download .md to keep it before switching.

It's answering about the wrong thing

Check the scope chip in the header — the chat answers about that scope, which is a snapshot from when it was opened, not whatever tab you're on now. Use the chip's switcher (or the right Ask AI button) to point it at what you mean. See Using AI Chat › Scope.