What does your orchestrator layer for coding agents look like?
W1141175 · reddit · 2026-11-13
A developer describes their coding-agent orchestrator: Claude Code for main edits, Codex as second pass, and a Python script that fans out tasks and polls them—no queue, no state, too much babysitting. They ask the community about four problems: dispatch (is a real queue overkill at 5-10 parallel tasks?), verification (tests as gate, second model as reviewer, or diff inspection?), runaway control (what's your actual kill switch?), and tooling (T3 Code or public repos, or everyone rolls their own?). They want to know whether the sane answer is using an existing orchestrator rather than welding one together.
Related event: Dev Tackles Orchestration Challenges of Multi-Coding-Agent Systems(2 posts)→
More from coding & agent
- Burkov roasts Codex: nudging it repeatedly just to get from 15% to 26% done — burkov · 2026-11-13
- lclip CLI turns Liveclip tables into a Redis-style key-value store with a built-in web admin — firasd · 2026-11-13
- Founder vibe-codes a Calendly clone and shares the result — kylegawley · 2026-11-13
- HeyGen shares its MCP prompts for free, again — HeyGen · 2026-11-13
- Orchestrator rolls out to Pro subs, pairing Hydrogen and Argon to save quota — clmt · 2026-11-13
- Burkov: vibe coding turned failed projects from 'can't start' into 'so close to done' — burkov · 2026-11-13