cones.

Harness support

cones discovers native sessions, reads what each harness reports and runs the harness's own operations. Missing state, context and usage stay absent. It installs no global session hooks. Five harnesses have report readers; six more have experimental terminal adapters. Full reference, with the versions each path was checked against: harness.md.

Capabilities

"Owned" means a client in a terminal cones hosts. "Others" are Gemini, Cursor Agent, Copilot, Amp, Droid and Kimi.

VerbClaude CodeCodexpiOpenCodeGrokOthers
ls✓✓✓✓✓Process only
show, search✓✓✓✓✓Copilot, Cursor; owned screens
launch✓✓✓✓✓✓
resume✓✓✓✓✓Copilot, Cursor
fork✓✓✓✓✓–
send✓DaemonOwnedOwned––
wait✓✓✓Owned✓–
rename✓✓OwnedOwned––
btw✓✓✓✓––
compactBackground✓OwnedOwned––
stopBackgroundDaemonOwnedOwnedOwnedOwned
rm✓✓✓✓✓✓
Join from the dashboardBackgroundDaemonOwnedOwnedOwnedOwned

wait needs a reported state, so a session with none never settles. OpenCode 2 native forks are refused.

Discovery

HarnessNative homeLive source
Claude Code$CLAUDE_CONFIG_DIR, otherwise ~/.claudeSession registry
Codex$CODEX_HOME, otherwise .codex beside the Claude homeProcesses, writer locks, saved threads
pi$PI_CODING_AGENT_DIR, otherwise .pi/agent beside the Claude homeProcesses and session files
OpenCode$XDG_DATA_HOME/opencode, otherwise ~/.local/share/opencodeProcesses, owned-client reports, SQLite
Grok$GROK_HOME, otherwise .grok beside the Claude homeProcesses and the session folder each holds open

Extra homes can be listed under homes in jobs.yaml. A headless run such as claude -p or codex exec has no client to join and is read like any other external session.

State

HarnessWhere state comes from
Claude CodeThe registry's own status: busy, shell, waiting, idle. Background sessions add job records.
CodexDaemon threads: native runtime state, including approvals and questions. Standalone clients: the rollout's task events only, so an approval wait reads as working.
piThe last entry in the session file. Owned clients also report idle, working and dialogs.
OpenCodeOwned clients only, through the reporter. External process rows show -.
GrokThe last turn event in the session it holds open.

Quiet output never changes a reported state. Only Claude Code reports a finished turn with a background shell still running.

Context, tokens and cost

Every column is read from what the harness writes: transcripts, rollouts, session files or databases.

Context window for Claude Code

Only Claude Code's status line receives the context window size. To let cones read it, add this after input=$(cat) in your statusLine command:

claude_dir=${CLAUDE_CONFIG_DIR:-$HOME/.claude}
mkdir -p "$claude_dir/statusline"
printf '%s' "$input" > "$claude_dir/statusline/$(jq -r .session_id <<<"$input").json"

Without it, context shows prompt tokens only. cones does not modify Claude settings or your statusLine command.

Message delivery

cones sends a note only through a channel the harness provides, and never types a note into a terminal.

HarnessChannel
Claude CodeThe cross-session inbox Claude's own SendMessage uses. A session that bypasses permission prompts holds the note for its user's approval unless "crossSessionInbound": "accept" is set.
Codexqueue --thread on the daemon that owns the thread.
pi, OpenCodeThe reporter cones loads into clients it launched. Clients in other terminals are refused.
Grok and othersNone found; sending is refused.

Permissions

Sessions the composer starts skip permission prompts by default, with each harness's own flag. skip_permissions: false starts every harness with its configured permissions; a per-harness key overrides it. Scheduled jobs always run without prompts.

HarnessKeyNative flag
Claude Codeclaude_skip_permissions--dangerously-skip-permissions
Codexcodex_skip_permissions--dangerously-bypass-approvals-and-sandbox
OpenCodeopencode_skip_permissions--auto
Geminigemini_skip_permissions--yolo
Cursor Agentcursor_skip_permissions--force
Copilotcopilot_skip_permissions--allow-all
Droiddroid_skip_permissions--auto high
Kimikimi_skip_permissions--auto
Grokgrok_skip_permissions--always-approve

pi has no permission prompts, and Amp has no flag for skipping them.

What cones writes outside its own state

cones keeps its own state in ~/.cones. It installs no global session hooks. These are the other places it writes:

WriteWhen
skills/cones/SKILL.md in the Claude Code home and ~/.agents/skillsDashboard start. A copy you edited or deleted is left alone.
Folder trust in Claude's .claude.json and Codex's configBefore a launch into an untrusted folder; the same record the harness's own trust dialog writes. Grok launches pass --trust.
A reporting extension loaded into pi and OpenCode clientsClients cones launches. It changes no tools or permissions.
~/.codex-<provider>First launch on a Codex provider other than the default home's.
~/Library/LaunchAgents/local.cones.*.plistSaving a scheduled job.
A custom-title line in a Claude transcriptRenaming an external interactive Claude session by hand.

Before a start, fork or resume, cones runs your $SHELL -l -i in the folder to pick up its environment, so rc files and direnv apply as they would for a harness you typed there.

Experimental terminal harnesses

Gemini, Cursor Agent, Copilot, Amp, Droid and Kimi get launch, process discovery, ctrl+z return, viewer reuse and stop. They have no external-terminal join, message delivery or scheduled jobs. State, model, context, tokens, cost and last reply stay absent. Copilot and Cursor Agent conversations appear in history and can be resumed.

Gemini, Cursor Agent, Copilot, Amp and Droid were each launched with no login and no network, then named, listed, reopened and stopped. None got past its trust or sign-in screen, so whether it takes the instruction is unverified. Kimi starts only without an instruction. Model-backed turns, permission questions and opening a Copilot or Cursor history row in the dashboard are unverified.