Skip to main content

​
Agent integration model

Termyte supports Codex, Claude Code, and Aider without requiring an agent plugin, cloud service, or changes to the agent itself.

​
Supported names

termyte run codex
termyte run claude
termyte run claudecode
termyte run aider
claudecode can resolve to the claude executable.

​
What launch preparation does

Before launch, Termyte:
  • identifies the repository root;
  • verifies repository-local state;
  • loads built-in, global, and repository YAML policy;
  • creates a session ID;
  • passes agent, workspace, and runtime-mode context;
  • reports which agent executable was resolved.

​
Limited mode

The current agent runner starts agents in limited mode. It does not automatically route the agent through termyte shell, and full subprocess interception is not guaranteed. This means:
  • Termyte context is available to the launched process;
  • repository policy can be prepared and reviewed before launch;
  • termyte check remains the dependable way to test commands and policy;
  • the experimental governed shell must be started explicitly.

​
Runtime profiles

The default profile describes planned shims and shell hooks. A codex-windows profile is available for Codex on Windows and keeps high-value command shims while disabling shell-host shims and hooks for compatibility. Other profile names may be accepted as labels, but only codex-windows has specialized behavior today.

​
Recommended adoption workflow

  1. Install Termyte and run doctor.
  2. Review built-in policy.
  3. Add global and repository YAML rules.
  4. Test representative commands with policy test and check.
  5. Launch the agent in limited mode.
  6. Evaluate termyte shell separately before relying on experimental interception.