Stitching four coding agents into one body for Kiroween 2026

I pay for more than one coding agent. Codex, Claude Code, Gemini CLI and OpenCode each have their own CLI, their own login and their own quota meter, and I usually find out one is empty when it dies halfway through a task. For Kiroween 2026 (Frankenstein category) I built Stitchwork: one MCP gateway that stitches those four limbs into a single body. What it does Any MCP client (Kiro, Claude Desktop, Cursor) sees one set of tools: agent_run, skill_run, agents_list, skills_list, quota_status. A shared rolling-window quota ledger is checked before every run, so an exhausted agent is refused before a call is wasted. agent: "auto" routes to the healthy agent with the most headroom. When a vendor answers 429 or "usage limit", the run fails over to the next agent and the limited one cools down for 15 minutes. Run stitchwork demo to watch the whole story with stand-in CLIs, no subscriptions and no tokens. What the real CLIs taught me I ran every adapter against the real releases and kept the raw output as test fixtures. Codex prints "tokens used" and the number on two lines, so my parser had silently fallen back to estimates; Gemini CLI exits with code 55 outside a trusted folder; OpenCode only reports usage with --format json. None of these showed up in tests written from documentation. Building the lab in Kiro The last milestone, a local dashboard called stitchwork lab, was built in Kiro CLI. To be upfront: earlier milestones were drafted with another AI coding assistant in Kiro's spec format before I had Kiro credits, and that assistant drove the Kiro CLI sessions on my account. Transcripts and prompts are in docs/kiro. Spec first. From one paragraph, Kiro read the existing specs, steering and ledger code, then wrote Requirements 15 to 19, properties P7 to P12 and ten tasks. It caught that the ledger never recorded duration or fallbacks, and made that task 1. Steering held. Zero runtime dependencies: the lab is plain node:http, no bundler. Tests after every task: 128 became 195, and two bugs were caught on the way. MCP both ways: Kiro called agents_list, skills_list and quota_status on the gateway it was helping build. The whole spec plus implementation cost about 27 Kiro credits. What I'd do differently: start in Kiro from day one. The spec-first session found a missing requirement before any code existed. Try it git clone https://github.com/YanYunCY/stitchwork && cd stitchwork && node bin/stitchwork.js demo Code: https://github.com/YanYunCY/stitchwork (MIT) This post was written as part of the Kiroween 2026 hackathon. #KiroweenHackathon26