Why We Structure AI Coding Workflows Around Three Modes — Not One Tool
Terminal-autonomous (Claude Code), persistent chat-agent (Codex), IDE-integrated (Cursor). Each mode solves a distinct problem. Mixing them without intent creates context-switching tax. Here's our decision matrix.
Published 2026-06-09
Why We Structure AI Coding Workflows Around Three Modes — Not One Tool
TL;DR: AI coding isn’t one workflow — it’s three distinct modes. We map every task to a mode first, then pick the tool. Terminal-autonomous for greenfield, persistent chat-agent for long refactors, IDE-integrated for precision edits. No single tool wins all three. Full framework →
The Context
Two-dev team, 5 active codebases (monorepo + 4 client sites). Jan–Mar 2026 we treated “AI coding” as one activity, swapped tools weekly, lost 15–20% capacity to context switching. April 2026 we codified the Three-Mode Framework after tracking 200+ task outcomes.
What We Tested
| Mode | Best Tool (2026-06) | Task Archetype | Anti-Pattern |
|---|---|---|---|
| Terminal-Autonomous | Claude Code | Greenfield features, auth, infra, payments, test generation | Using for surgical TS edits (no LSP) or 5-min fixes (session overhead) |
| Persistent Chat-Agent | Codex (ChatGPT Plus) | Multi-hour refactors, debugging, migrations, archaeological code reading | Using for greenfield (no terminal autonomy) or quick edits (chat UI friction) |
| IDE-Integrated | Cursor Pro | <30 min TypeScript surgical edits, type-error fixing, component extraction | Using for long sessions (Composer context loss) or autonomous loops (no --allowed-tools equiv) |
The Pivot Point
April 15, 2026: Stripe webhook migration (14 files, 3 hrs estimated). Assigned to Cursor Composer “because it’s in the IDE.” Result: 5.5 hrs, 3 context losses, 2 type regressions missed. Same task next week in Codex (Persistent Chat-Agent mode): 2.8 hrs, zero context loss, caught 2 type issues via manual review. The mode-task mismatch cost 2.7 hrs. We wrote the decision matrix that day.
What We Use Now
Decision Matrix (pinned in #dev-ai Slack, in .toolcrucible/decision-matrix.md):
| If Task Is… | Use Mode | Tool | Trigger Phrase |
|---|---|---|---|
| New feature, 0→1, needs tests | Terminal-Autonomous | cc | ”greenfield” / “new endpoint” / “auth flow” |
| Refactor >2 hrs, touches >5 files | Persistent Chat-Agent | cx | ”migrate” / “refactor” / “debug” / “archaeology” |
| Type error, rename, extract component <30 min | IDE-Integrated | cursor | ”fix type” / “extract” / “rename” / “quick” |
| Boilerplate, imports, simple props | Inline Completion | Copilot | (passive) |
Enforcement: PR template includes “AI Mode Used:” dropdown. CI fails if blank. Retro reviews mode-task fit monthly.
When You’d Choose Differently
- Solo dev: Pick one mode, master it. Terminal-first → Claude Code only. VS Code loyalist → Cursor only (accept Composer limits).
- Team >5: May need 4th mode — “onboarding/standardization” → Windsurf (shared IDE config) or Cline (shared prompts).
- Mobile/React Native: Expo integration makes IDE-Integrated mode higher value; might drop Persistent Chat-Agent.
- Strict local-only: Terminal-Autonomous → Aider + Ollama; Persistent Chat-Agent → not available locally yet.
Tool Crucible Rating
| Dimension | Rating (1–5) | Notes |
|---|---|---|
| Overall | 5 | Framework eliminates tool FOMO; measurable velocity gain |
| Ease of Use | 4 | Requires team discipline; PR gate helps |
| Value | 5 | Zero cost (framework); tool costs unchanged |
| Support | N/A | Internal process; evolves with tool landscape |
This is part of our AI Coding Tool Evaluation series. See full framework: AI Coding Workflow Modes: The Three-Mode Decision Matrix
Last reviewed 2026-06-09. See our methodology and affiliate policy.