Jeden/Docs

CLI command

jeden doctor

Probe the live health of Jeden's configured runtime dependencies and local subsystems.

Exact invocation#

Shell
jeden doctor [--json] [--cwd path]

Inputs and options#

  • Optional: --cwd. The command always emits its structured doctor report, whose schemaVersion is 1, the version of its format; --json is accepted for CLI consistency.

Output and state effect#

Runs the selected model route, Weles, storage, process, sandbox, MCP, extensions, LSP, browser, TUI keymap, task, memory, collaboration and leftovers probes, then prints a JSON report with per-probe evidence and latency. The route probe is model for a direct provider and brama for Brama; its evidence distinguishes protocol version from the observed catalog revision (a response-body digest when a direct provider declares none). A direct provider that omits a version has an empty version in the probe; Jeden does not assign Brama's version to its response. The sandbox probe reports whether a task can run at all: the helper found beside the executable, its signature verdict, and its enforcement probe. The lsp probe reads the capability registered as tool/lsp; the browser and collab probes read the capabilities whose metadata.service is browser or collab, the service a tool service or a slash command (/collab, /join, /leave) declares. A capability whose id merely contains one of those words is not counted, and a subsystem none declares is reported as not configured.

Refusals and boundaries#

  • The command exits unsuccessfully when any active probe is unavailable; degraded or inactive evidence remains explicit in the report.
  • The model-route probe reads the selected provider's catalog (Brama or an explicit direct endpoint). If it answers but neither config nor JEDEN_MODEL selects a model, the probe is unavailable with that observed state; a catalog answer alone is not a runnable model turn. A direct catalog refusal names its provider response but cannot qualify chat authorization. Direct catalogs are fetched live rather than reused from a cache: removing or exhausting the current credentials cannot leave a stale healthy probe.
  • A missing, unsigned, or non-enforcing jeden-sandbox-helper makes the sandbox probe unavailable, naming the helper path checked and the executable it was looked up beside, so a host that would fail every jeden run fails the doctor first.
  • Signature verification and the helper enforcement probe each run to completion: the verifier's own verdict is the answer, and a slow machine is never reported as an invalid signature. A probe that fails reports the failed operation and the helper path, and the sandbox stays unavailable; neither agent execution nor a successful standalone helper probe overrides missing verification.
  • Storage probe failures and serialization failures are returned as errors instead of a healthy result.
  • The leftovers probe lists every file in ~/.omp/agent/tools whose first line says it was placed by jeden context install --omp, an installer Jeden no longer has: such a tool is loaded by every OMP session and runs whatever Jeden binary it was written with. It is degraded, naming each file and the rm that removes it; a directory or file that cannot be read makes it unavailable naming the path and the cause; no such directory is healthy.
  • A command line of the wrong form (an unknown command or option, a missing, unexpected or invalid argument, a missing confirmation) prints the error and the usage and exits 2; a refusal that retrying unchanged can help (a dependency down or not answering, a rate limit) exits 69; any other refusal or failure exits 1. A refusal a functionality declares ends with fix: … and cause: <operation>.<cause>, and jeden errors show <operation> lists every cause of that functionality.