Dev builds three agent "Sparks" that run Codex, file GitHub issues, and ship PRs to replace engineers
abhi9u · x · 2026-11-19
Developer abhi9u shared how he replaced an engineering team with three "Sparks" in Composal to automate himself out of the loop:
- The pain: he used to sit and supervise Claude; onboarding a new podcast often required code changes for new platforms, transcripts, and artwork.
- Spark 1 (Engineering assistant): handles feature development — launches and supervises Codex, runs tests, gets code reviewed, and opens a PR for human sign-off.
- Spark 2 (Onboarding Manager): researches a new podcast (artwork, transcripts, episode monitoring) and files the request as a GitHub issue.
- Spark 3 (Catalog Manager): watches for new GitHub issues and handles podcast onboarding; on bugs or missing features it can launch and supervise Codex to fix the code, then retry.
Only the final PR review stays human — a hands-on multi-agent orchestration case study.
Related event: Developer Automates Himself Out of the Loop with Agent Team(2 posts)→
More from coding & agent
- Google Labs launches Stitch Loop, an always-on product agent for post-launch improvement — GoogleLabs · 2026-11-19
- lineup: Open-Source CLI That Catches Coding Agents Making Sneaky Edits — Several-Coyote3534 · 2026-11-19
- Wanted: an LLM Assistant Inside ComfyUI — External MCP Feels Too Clunky — dustynjerman · 2026-11-19
- Running untrusted agents on GKE: sandboxing, cold starts, and state — rseroter · 2026-11-19
- Agentrooms: An MCP Server Letting Claude Code Ask Codex to Review Commits — terzigolu · 2026-11-19
- Jane Street opens first Formal Methods internship to validate agent-generated code — hargup13 · 2026-11-19