Why: Establish one validated project-local routing document before any real Agent execution is enabled. Evidence: Cursor observed red then 12 green configuration tests; the host replays those tests, the temporary validation target, and whitespace checks during integration. Impact: Adds the U1 configuration contract and parser only; real routing, adapters, controller execution, and governance adoption remain disabled. Refs: docs/superpowers/plans/2026-10-15-project-agent-execution.md
1.5 KiB
1.5 KiB
Project Agent Execution
Project-local execution routing configuration. This document is the single
authority for which Agent CLI profiles may implement, repair, test, or review
bounded units. Human-readable notes may appear outside the machine block; the
parser accepts exactly one agent-execution fenced block.
U1 delivers configuration parsing and validation only. Routing is not enabled until later units wire adapters and the execution controller.
schema: agent-execution/v1
execution:
fresh_process_per_unit: true
permission: run-everything
fallback_to_host: all-unavailable
max_parallel: 3
timeout_seconds: 7200
summary_bytes: 16384
raw_output_bytes: 10485760
roles:
implementation: [cursor, antigravity, claude, codex, pi, kimi, opencode]
repair: [cursor, antigravity, codex, claude]
test: [pi, antigravity, codex]
review: [claude, codex, pi]
profiles:
cursor:
adapter: cursor
executable: cursor-agent
model: auto
enabled: true
antigravity:
adapter: antigravity
executable: agy
model: auto
enabled: true
claude:
adapter: claude
executable: claude
model: auto
enabled: true
codex:
adapter: codex
executable: codex
model: auto
enabled: true
pi:
adapter: pi
executable: pi
model: auto
enabled: true
kimi:
adapter: kimi
executable: kimi
model: auto
enabled: true
opencode:
adapter: opencode
executable: opencode
model: auto
enabled: true