After a month of running this daily, I’ve settled on what I call the Hybrid Method: keep Claude.ai (the chat) as my only surface, and delegate engineering work in the background to Claude Code. The chat writes the engineering prompt, launches the executor, supervises through the filesystem and git log, and reports back without me ever opening a terminal. The piece I find most useful to share is the **allocation matrix** — which kind of work goes to which engine. Took weeks of measurement to stabilize. **Background agent (Claude Code) handles:**
- Large refactors across many files
- Tedious mechanical work (renaming patterns, applying fixes from a list)
- Anything that needs filesystem + git access without back-and-forth
- Tasks that take more than ~2 minutes of pure execution **Chat (Claude.ai) handles:**
- Architecture decisions and tradeoffs
- Reviewing the agent’s diff and discussing the output
- Sprint planning while the agent runs the current sprint
- Quick edits where the round-trip to a background process is wasted
- Anything where the answer needs human reading anyway **The hand-off:** The chat writes a detailed prompt for the background agent (including a fail-fast spec and what to commit at the end). It launches `claude --headless --instruction “…”` as a subprocess via a small MCP bash bridge (~200 lines of Python using Anthropic’s MCP SDK; community implementations exist too). Then it polls the git log and a status file every 30–60 seconds while I plan the next thing. When the agent finishes, the chat reads the diff and reports. **Why “hybrid”:** The analogy is the hybrid car. Two engines with different load profiles. The chat is electric — instant startup, smooth low-load, great for transitions and decisions. The background agent is combustion — cold-start cost (5–15 seconds while it loads the project’s memory file and explores the repo), but sustained throughput once running. They specialize, they hand off, the user never feels the seam. **What changes from running Claude Code alone:** Context-switching cost drops to near-zero — I never leave the chat session Strategic and execution work happen in parallel (the chat plans the next sprint while the current one runs) The chat acts as supervisor — better wired for high-level reasoning than the executor agent which is wired for action **Caveats:**
- This is the operator pattern Anthropic has documented elsewhere; the specific assembly (Claude.ai web as the chat + an MCP bash bridge + Claude Code as the executor) is what I haven’t found written up specifically
- No sandboxing on personal hardware; if any of this ever runs on someone else’s machine, careful sandboxing is non-negotiable
- The chat saturates beyond ~2 parallel background tasks — past that, the supervision quality drops Curious whether anyone else has converged on something similar, or what variations work for you. submitted by /u/Krycekk
Originally posted by u/Krycekk on r/ClaudeCode
You must log in or # to comment.