Ship a month of pull requests through a scoped Kiro CLI control layer

Kento Ikeda had ChatGPT plan and review while sandboxed Kiro CLI wrote the code. Over a month the setup opened 624 PRs and merged 317, with a median of 32 seconds from PR to merge.

Done withKiroChatGPTinGitHub· Nov 16, 2026

What they did

Kento Ikeda, who runs BrightFlow LLC, built a system he calls BRIDGE to develop his company's product with two AIs. ChatGPT, connected through a custom MCP app, gathered context, wrote requests and reviewed work, but held no GitHub token or Kiro key. It could call only five tools: two to inspect the repo and PRs, one to hand a task to Kiro, one to check a task, and one to merge. Each task had to declare which files Kiro could create, change or delete. A controller then ran Kiro CLI headless inside a bubblewrap and seccomp sandbox with no shell access, compared the real diff against the declared list, failed the task on any undeclared change, and opened a PR. Merges went through only if the PR's head commit matched the one that was reviewed. Ikeda set tool confirmations to always allow and stepped in only for direction or when the AI got stuck. He ran it from 11 September to 12 October 2026.

How it went

The month produced 317 merged PRs, 159 closed and 148 still open. Of the 307 unmerged, 122 had no diff at all, because ChatGPT used the write path for audits and questions when the read tools could not answer them, and 37 were superseded by later PRs. The median time from PR to merge was 32 seconds and there were no GitHub reviews; merges rested on the AI's review. 19 PRs merged after main had moved on without being rechecked, though none overlapped later changes. Ikeda reports no write ever escaped the declared scope or the sandbox. The controller grew to about 49,000 lines of TypeScript, half of it tests.

Worth knowing

Ikeda logged so little, to protect secrets, that he cannot count how often the scope and SHA checks actually stopped something; record result types and counts from day one. Give the planning AI a read path for questions or it will open empty PRs. PR diffs shown to the reviewer were capped at 128 KiB, so the AI may not have seen whole changes. This is his own setup, not one AWS recommends.

Try it

With Kiro· 4 parts to fill in

Act as the planner and reviewer for [my repo]. You may not write code yourself. For each change, write a request for [Kiro CLI or my coding agent] that names every file it may create, modify or delete, and nothing else. After it runs, compare the actual diff with that list and reject the task if any other file changed. Answer questions and audits by reading the code, never by opening a PR, and do not open a PR when there is no diff. Before merging, confirm the PR head matches the commit you reviewed, that CI passes against the latest [main branch], and that the diff you read was not truncated. Write your review reasoning on the PR. Stop and ask me before any change to [protected areas such as auth or billing].

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related