Case: Cross-CLI Handoff¶
Star on GitHub Compare Workflows Case Library
When to Use¶
Use this when one model should analyze, another should implement, and another should review without losing context.
Run¶
scripts/ctx-agent.sh --agent claude-code --project Harness CLI --prompt "Analyze blockers and propose top fix."
scripts/ctx-agent.sh --agent codex-cli --project Harness CLI --prompt "Implement the top fix from latest checkpoint."
scripts/ctx-agent.sh --agent gemini-cli --project Harness CLI --prompt "Review regression risk and missing tests."
Evidence¶
- Shared session/checkpoints updated in:
ls .aios/context-db/sessions
- Timeline shows cross-agent continuity:
cd mcp-server
npm run -s contextdb -- timeline --project Harness CLI --limit 12
- Exported context packet exists for latest session:
ls .aios/context-db/exports | tail -n 5
Why This Matters¶
Without a shared layer, cross-agent handoff often degrades into copy/paste context. With Harness CLI, all agents read/write the same project context path and checkpoint stream.