Skip to main content
A harness is a connected coding agent — Claude Code, Codex, Cursor, or OpenCode — that exports session events to Terma. The harness commands let you add, remove, and inspect those connections so you control exactly which agents contribute to your activity feed.

​
terma connect

Point one or more agent harnesses at Terma to start exporting session events.
Without --source, terma connect opens an interactive selector listing every harness Terma can detect on your machine. Select one or more to wire them up in a single pass.
Connect a specific harness

​
terma disconnect

Stop a harness from exporting events to Terma. The underlying agent is left untouched — only the Terma export is disabled.
terma disconnect does not uninstall or modify the coding agent itself. It removes the Terma hook configuration so the agent stops forwarding events. You can reconnect at any time with terma connect.

​
terma harness status

Show which harnesses are currently connected, when they last sent an event, and how many events they have delivered.
The output table includes:

​
Supported Sources

The following sources are recognized by name with --source:
  • claude-code
  • codex
  • cursor
  • opencode
Terma also infers activity from traffic originating via openrouter and direct Anthropic or OpenAI SDK calls, even without an explicit harness hook.

​
Relationship to terma setup

terma setup calls terma connect for each coding agent it detects on your machine during initial onboarding — you do not need to run terma connect manually for agents that were present at setup time. Use terma connect when you install a new agent after setup, or when you want to add a harness that was skipped during the initial configuration.
Add a harness installed after setup
Each harness adapter is a one-liner that calls terma hook <event>. All logic lives in the Terma binary, so updating Terma updates the hook behavior without touching committed files.