Files
Agent-System-Dev/AGENT-EXECUTION.md
T
weichen 8c98635dfd Route project work through Cursor agy and PI
Why: make the three approved CLIs the only active implementation and test routes

Evidence: adapter unit tests, configuration validation, diff check, and real marker probes for all three profiles

Impact: narrows project routing and fixes agy prompt binding for noninteractive execution

Refs: feature/goal-first-delivery
2026-10-15 06:48:06 +00:00

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.

U3's execution controller and U4's project wiring are integrated. This file is the execution-routing authority for implementation, repair, test, and review. Active routes are intentionally limited to Cursor, Antigravity (agy), and PI. model: auto lets each CLI use its configured default model; PI therefore uses the operator-selected MiniMax default. A provider that makes no successful stdin write or stdout/stderr read for idle_timeout_seconds is stopped before timeout_seconds.

schema: agent-execution/v1

execution:
  fresh_process_per_unit: true
  permission: run-everything
  fallback_to_host: all-unavailable
  max_parallel: 3
  timeout_seconds: 7200
  idle_timeout_seconds: 600
  summary_bytes: 16384
  raw_output_bytes: 10485760

roles:
  implementation: [cursor, antigravity, pi]
  repair: [cursor, antigravity, pi]
  test: [pi, antigravity, cursor]
  review: [pi, antigravity, cursor]

profiles:
  cursor:
    adapter: cursor
    executable: cursor-agent
    model: auto
    enabled: true

  antigravity:
    adapter: antigravity
    executable: agy
    model: auto
    enabled: true

  pi:
    adapter: pi
    executable: pi
    model: auto
    enabled: true