Hermes Claude Code Spawn

Hermes → Claude Code Spawn (Governed)

Delegate coding tasks to Claude Code CLI (/root/.local/bin/claude, v2.1.218) under arifOS constitutional governance. This is the print mode path — one-shot, non-interactive, structured output. For multi-turn work, use the tmux pattern (below).

Prerequisites (verify before spawn)

claude --version 2>/dev/null            # must be v2.x+
[ -d /root/AAA/plugins/claude-code-federation ]   # plugin present
[ -f /tmp/opencode/session_state.json ] # session bound (else bind first)
curl -sf http://127.0.0.1:8088/health >/dev/null  # kernel alive

If any fail → do NOT spawn. Report the gap, route to 888-APEX for HOLD.

Mode 1: PRINT MODE (PREFERRED — one-shot, structured)

terminal(command="claude -p '<TASK>' --max-turns 15 --output-format json \
  --allowedTools 'Read,Edit,Write,Glob,Grep,Bash,WebSearch,WebFetch' \
  --permission-mode plan \
  --plugin-dir /root/AAA/plugins/claude-code-federation \
  --append-system-prompt 'You are a governed executor of the arifOS federation. F1: snapshot before mutate. F2: label claims OBS/DER/INT/SPEC. F7: cap confidence 0.90. F11: trace every action. F13: Arif holds final veto. Never use --dangerously-skip-permissions. Digital ops = MUBAH (auto-do).'",
  workdir="/root",
  timeout=300)

Parse the JSON result:

{
  "type": "result",
  "subtype": "success",
  "result": "The task output text",
  "session_id": "75e2167f-...",
  "num_turns": 3,
  "total_cost_usd": 0.078,
  "stop_reason": "end_turn"
}

Key fields to report to user: result (output), num_turns, total_cost_usd, session_id. Failure subtypes: error_max_turns, error_budget, error_rate_limit, error_other.

Mode 2: TASK-ONLY (analysis — no mutation)

terminal(command="claude -p '<ANALYSIS_TASK>' --max-turns 5 --output-format json \
  --allowedTools 'Read,Glob,Grep' \
  --permission-mode plan \
  --plugin-dir /root/AAA/plugins/claude-code-federation",
  workdir="/root",
  timeout=120)

Use when: review code, explain architecture, estimate effort, research — anything that must NOT mutate.

Mode 3: TMUX INTERACTIVE (multi-turn — rare, requires governance)

Only when the task genuinely needs iterative human-in-the-loop work:

tmux new-session -d -s cc-work -x 140 -y 40
tmux send-keys -t cc-work 'cd /root && claude --permission-mode plan' Enter
sleep 5 && tmux send-keys -t cc-work Enter   # workspace trust dialog
sleep 2 && tmux send-keys -t cc-work '<TASK>' Enter
sleep 15 && tmux capture-pane -t cc-work -p -S -50
# ... iterate ...
tmux kill-session -t cc-work   # ALWAYS clean up

Governance Contract (non-bypassable)

Session Binding

Before spawning, ensure a session is bound:

# If /tmp/opencode/session_state.json is missing or stale:
curl -sf -X POST http://127.0.0.1:8088/mcp -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"arif_init","arguments":{"actor_id":"hermes-agent","intent":"Spawn Claude Code governed executor","requested_authority":"FULL"}}}'

Record the CC spawn in the audit trail with both session IDs (Hermes + CC).

Cleanup

• tmux sessions: tmux kill-session -t <name> when done (never leave orphans)
• CC --no-session-persistence flag in pure CI to avoid disk accumulation
• Report total_cost_usd to the user for spend transparency

Failure Handling