Doctor

Doctor is the platform's self-check: one board that probes everything the product depends on — binaries, Python environments, configuration, daemons, engines, media tools, and your account state — and shows one row per check. Open it at Settings ▸ Doctor. It works even when you are signed out or your entitlement has lapsed, by design: it is the surface that helps you fix exactly that state.

How it runs

• Checks run automatically when you open the view; the Refresh button in the header re-runs everything.
• Rows fill in independently as each probe resolves — one slow or offline service never blocks the rest of the board.
• The header sub-line summarizes the board: all clear, or how many rows need attention and how many are informational. A healthy machine reads quietly — no wall of red.
• Each row shows a status, a detail line, and — where a failure has a one-click remedy — a fix button. Running a fix re-probes just that row, so you see the result immediately.

The five groups

Core

The foundation: required binaries (Python, Node.js, npm, and the claude agent CLI), the per-service Python environments, and the configuration spine — the environment file, the API keys the knowledge and image systems need, the generated agent tooling manifest, folder trust for the agent CLI, the platform tree, and the doctrine set. Failing rows carry the exact install command or a fix action such as Generate (rebuild the agent config) or Trust this folder.

Daemons

The background services: the app-managed daemons plus the shared memory service and the graph database. A stopped daemon gets a Start button; an unprovisioned local database gets Provision. This group overlaps the Dashboard's Platform Health panel on purpose — Platform Health is the live control surface, Doctor is the diagnosis with remedies.

Engines

The video engines (Remotion and Hyperframes). These are opt-in installs — an absent engine is informational, not a failure, until you use the video features.

Media

The media toolchain: ffmpeg/ffprobe and the Whisper transcription models. Fix actions fetch ffmpeg directly or take you to the Speech-to-Text settings for model downloads.

Account

Sign-in and entitlement state, with Sign in and Refresh actions that land on Settings ▸ Account.

When to run it

• After install — the install flow ends with a green Doctor board; see install.
• After changing configuration — keys, the database backend, daemon endpoints. Doctor verifies the change actually took.
• When a view goes quiet — an offline daemon, a missing key, or a missing dependency shows up here with the remedy attached. The troubleshooting section is organized around exactly this flow: start with Doctor, then follow the symptom.

Related pages

• Doctor checks reference — every check in the catalog, one by one
• Troubleshooting — symptom-first fixes seeded from these checks
• Dashboard — the live daemon control surface
• Settings — where the configuration Doctor verifies is written