# Five agents ran. Nobody owned it.

> Green checks are not an owner. Narrow tools, real gates, a named person.

- **Format:** short video, 9 steps, ~50 seconds
- **Topic:** Designing a GitHub Copilot multi-agent orchestrator — why five agents with every tool can turn one sentence into a green pull request that breaks on staging, and how least-privilege tools, send: false handoffs, hooks, CI gates and human sign-off put an owner back on the decision.
- **Author:** Suthahar Jegatheesan (MSDEVBUILD)
- **Category:** GitHub Copilot · copilot
- **Published:** 2026-06-14
- **Tags:** githubcopilot, aiagents, softwarearchitecture, legacycode, flutter, devops, aicoding, msdevbuild
- **Canonical URL:** https://blog.msdevbuild.com/shorts/copilot-multi-agent-handoffs-nobody-owned-it/

---
## What you'll learn

- Why leaving out the tools list gives an agent every tool
- How a send: false handoff keeps a person between phases
- Which gates block an agent, and which only ask

## Understand it one step at a time

### 1. One sentence, five agents

You ask for a cancel reason. The agents run one after another, and none of them stops to ask you.

### 2. No tools line means every tool

Leave out tools in an agent file and it defaults to all tools, including edit.

### 3. The tester edits production code

A test fails, so the tester widens canCancel in lib/ and the test goes green.

### 4. The reviewer rewrites the rules

Asked to review, the security agent finds a real hole and edits firestore.rules itself.

### 5. Every check is green

CI passes because no test loads firestore.rules. The next day, cancel fails on staging.

### 6. Fix one: narrow the tools

Write a tools list for every agent. Security and the orchestrator lose edit completely.

### 7. Fix two: send false

A handoff with send: false pre-fills the next prompt and waits for you to read it.

### 8. Fix three: real gates

A hook, required CI checks and CODEOWNERS block. Instructions and charters only ask.

### 9. Design the gates, own what ships

Agents do the work. A person owns what ships.

---

## The takeaway

**Design the gates. Own what ships.**

Narrow tools, send: false, hooks and CI, then a person signs off by name.