Skip to content

Reference

Troubleshooting

The usual first-run failures: a missing CLI, a signed-out session, a framed page that stays blank, and a rate limit.

The CLI does not start

  • Confirm the binary is on PATH, or set the path under Settings → Defaults and use Test.
  • An expired login shows a sign-in card. Authenticate runs claude /login, codex login, or cursor-agent login in a terminal.
  • Gemini must be 0.33.0 or newer. The turn tells you how to upgrade when it is older.
  • The backend still boots when the binary cannot be resolved, so you can open Settings and fix the path.

The preview is blank

Some apps send a frame-blocking header. Web and the overlay load the address through Brompter’s frame proxy. If the workspace has no app URL, set one in the workspace or type a path in the toolbar. Standalone desktop mode does not show the iframe tools; switch to Overlay if you want the app underneath.

The widget cannot reach the backend

The UI origin must be listed in DEVCHAT_CORS. The default is http://localhost:5195. Binding the API off localhost, or opening CORS to every origin, requires DEVCHAT_AUTH_TOKEN. The desktop app does not use that browser origin; it talks to loopback with the handshake token.

A turn stops on a limit

Rate and usage limits come from the CLI. Notifications can schedule a single continue at the reset time the CLI reported. A session budget cap stops the next API turn before the process starts and reports that the budget was exceeded. Neither one retries in a loop.