Curious how others split work. My current setup:
- Claude Code = eyes + brain. Explores the repo, reads related files, builds context, plans.
- Codex = hands. Once the context is loaded, it’s noticeably faster at writing code and doing code review. Codex’s weakness: it doesn’t look at information or code well on its own. Drop it in a fresh repo and it acts on shallow context. Fast hands, not great eyes. So what I actually want: one continuous conversation, swap the harness underneath. Plan and explore in CC → switch to Codex for the grind → pop back into CC when I need to re-strategize. Context persists across the swap. This isn’t multi-agent orchestration in the AutoGen / CrewAI / LangGraph sense (one harness, N roles inside it). It’s multi-agent harness orchestration — the harness itself is the swappable unit.
- Traditional:
1 harness × N roles - This:
N harnesses, 1 threadQuestions: - How do you split work between CC and Codex / Cursor / Antigravity ?
- Anyone bridging conversation history across harnesses?
- Does “harness as a building block” land, or is this obvious? submitted by /u/maestrojeong
Originally posted by u/maestrojeong on r/ClaudeCode
You must log in or # to comment.