Skip to main content

​
Verify Termyte with doctor

Run: 
termyte doctor
For machine-readable output: 
termyte doctor --json

​
Status meanings

  • PASS: the required behavior worked.
  • WARN: an optional capability is missing or attention is recommended.
  • FAIL: a required behavior is broken.

​
What doctor checks

​
System

  • platform and architecture;
  • Node.js version;
  • npm and Git availability;
  • Windows PATHEXT behavior.

​
Workspace

  • current directory;
  • write access;
  • SQLite write access;
  • policy loadability and runtime-policy drift;
  • .termyte directory creation.

​
Shell runtime

  • governed session and shim directories;
  • shim manifest integrity;
  • shim-first PATH;
  • guard daemon communication;
  • a real shim smoke request;
  • nested shim resolution;
  • stale pending shim records.

​
Tools and package

  • optional Codex, Claude Code, and Aider executables;
  • supported shells and Windows environment capabilities;
  • packaged CLI and benchmark assets.

​
How to interpret results

Missing optional agents, bash/zsh, PowerShell features, or WSL support may be warnings. You can still use the stable check and YAML policy workflows. Treat these as blockers for experimental interception:
  • guard daemon IPC failure;
  • shim smoke failure or timeout;
  • shim manifest failure;
  • session creation failure;
  • SQLite or workspace write failure.
A zero-failure doctor report proves that tested Termyte runtime surfaces worked on the current machine. It does not turn Termyte into a sandbox or prove that every process path is intercepted.