harness-multitool

Delegates: Claude Code and Codex inside the harness

A delegate is a vendor's own agent CLI, Claude Code or Codex, that the harness runs as the agent of a conversation. The harness does not patch, wrap or imitate these programs. It runs the unmodified binaries in their documented JSON-stream modes, reads their events, and adds its own tools through MCP. The user signs in to each program through the vendor's own flow, and the harness never touches those credentials.

What it is

The harness has two kinds of agent backend (IF-17):

Both kinds draw the same transcript, the same tool cards, the same journal and maps, and the same status line. The harness reads the delegate's event stream into its own event log (ADR 0023).

How it works

Claude Code

The harness starts the unmodified claude binary in print mode, with JSON streams in both directions (crates/backend-claude-code/src/lib.rs):

claude -p --input-format stream-json --output-format stream-json --verbose \
  --include-partial-messages --replay-user-messages ...

Codex

The harness starts the unmodified codex binary in its documented JSON mode (crates/backend-codex/src/lib.rs):

codex exec --json --skip-git-repo-check ...
codex exec resume <thread> ...

Isolated or the user's own

A delegate either runs in the user's own Claude Code or Codex setup, with their plugins, servers and rules (CON-145), or isolated, with none of them. A slave of an orchestra always runs isolated (CON-108).

One conversation in every form

A conversation can move between the harness's own loop, Claude Code and Codex. The daemon writes it into each program's own session format and keeps the forms in step, so each program reads a session of its own kind (ADR 0025, CON-134, CON-136). See Adapters and providers.

Terms and subscriptions

The harness runs Claude Code and Codex within their vendors' published rules. It runs the unmodified programs, each user signs in to their own copy through the vendor's own flow, and the harness never touches those credentials or pays for, resells or routes anyone's usage. The conditions, quoted below, are met point by point. This page quotes the vendors' terms; it is not legal advice.

A plan's usage limits are its user's own: the harness is a tool, and each user keeps to their plan.

What the harness does:

What Anthropic's terms say, as read on 2026-11-19 (Legal and compliance):

How the harness meets them: every point in the list above. Each user's own Claude Code is signed in by that user, and the harness only starts it and reads its stream.

What is for the project's owner, not for the users:

Limits and status

Specs and decisions

This page's source