What problem does it solve?
Verifying that the Cyrus agent system works end-to-end requires manually checking issue creation, agent session execution, and activity output across multiple components, which is slow and error-prone without a structured test protocol.
Core Features & Use Cases
- End-to-End Pipeline Validation: Runs a phased test drive covering issue-tracker behavior, EdgeWorker worktree/session execution, and activity rendering quality.
- Slack Chat Session Verification: Optionally validates the Slack to ChatSessionHandler to ClaudeRunner path using a synthetic app_mention dispatch endpoint, including shared auto-memory and per-thread workspace isolation checks.
- Structured Reporting: Produces standardized test drive reports under apps/f1/test-drives/ with checklists, session logs, and retrospectives.
- Use Case: Before merging a major runner or harness change, run an F1 test drive to confirm the server starts, issues are created, sessions produce coherent activities, and everything stops cleanly.
Quick Start
Run an F1 test drive to validate the full Cyrus pipeline from issue creation through agent session activity rendering and write the report.