condensate docs
Operate / Condensate

Troubleshooting

Diagnose a missing server, empty task list, failed model turn, or stalled stream.

Start with the failing boundary: browser, application server, runtime, engine, or provider. Restarting everything makes that boundary harder to identify and can interrupt active tasks.

The page does not load

Confirm the application's startup command and port. Opening index.html from disk does not start its backend. Dex defaults to 5189, the runtime to 4741, the review hub to 4700, and Dojo to 4800.

The page loads but tasks do not

curl -i 'http://127.0.0.1:4741/threads?limit=5'
curl -i http://127.0.0.1:4741/workspaces

Distinguish a successful empty page from a transport error. Check CONDENSATE_AGENTS_URL on the application server, the selected workspace, and pagination. A loaded page is not a complete inventory.

A model turn fails

Inspect the selected thread's event history and provider error. Verify the engine/model pair, account binding, workspace policy, and provider availability. A working list endpoint does not prove that model credentials work.

Streaming pauses

Check the durable tail and current turn status before assuming the task stopped. Reconnect from a sequence cursor. Verify that a reverse proxy preserves streaming and does not buffer or prematurely time out the response.

Context reductions repeat

Inspect window records, curator failures, and thrash or blocked-window errors. Keep the durable log. Deleting history is not a diagnosis of a model-facing context problem.

Update a running installation

Use the configured drain/update procedure. Back up SQLite consistently and preserve blob files and engine resume state. Copying only threads.db from an active WAL database is not a complete backup strategy. This guide does not restart or migrate an existing deployment.

Condensate developer documentation · Source ba6d28952e