Quick Start¶
This guide walks you through your first AgentPair session.
Your First Paired Session¶
Navigate to a project directory and run:
AgentPair will:
- Create a new run with a unique ID
- Start Codex as the primary worker
- Start Claude as the reviewer
- Execute the task in a loop until completion
Understanding the Output¶
2024/03/28 10:00:00 INFO starting agentpair version=dev
2024/03/28 10:00:00 INFO created run run_id=1 prompt="Add input validation..." agent=codex review_mode=claudex
2024/03/28 10:00:00 INFO starting paired-agent mode primary=codex secondary=claude
2024/03/28 10:00:01 INFO iteration started iteration=1 state=working
...
2024/03/28 10:05:00 INFO run complete iterations=3 state=completed
Using tmux Mode¶
For a visual side-by-side view of both agents working:
This creates a tmux session with:
- Left pane: Claude
- Right pane: Codex
- Bottom pane: Status dashboard
Attach to watch:
Single-Agent Mode¶
For simpler tasks, use one agent:
# Claude only
agentpair --claude-only "Fix the typo in README.md"
# Codex only
agentpair --codex-only "Add unit tests for utils.go"
Specifying Proof Requirements¶
Use --proof to tell agents how to verify their work:
Viewing the Dashboard¶
Monitor all active runs:
Checking Bridge Status¶
See message flow between agents:
Example Workflows¶
Feature Implementation¶
agentpair --tmux --prompt "Implement OAuth2 login with Google" \
--proof "Run the app and verify login works"
Bug Fix¶
agentpair --prompt "Fix the race condition in cache.go" \
--proof "Run 'go test -race ./...' with no races detected"
Code Review¶
Refactoring¶
agentpair --worktree --prompt "Refactor the database layer to use repository pattern" \
--proof "All existing tests must pass"
Next Steps¶
- Configuration — Customize default settings
- Paired Sessions — Deep dive into paired mode
- Bridge — Understand agent communication