How one engineer went from juggling AI agents to letting AI run the team

#ai #opensource #showdev #vscode

You can see the exact day it happened.

That purple line in Amr Elsayed's contribution graph marks when he crossed from Sphere 5 Chess Grandmaster to Sphere 6 Chief of Staff. The green to the left is the Grandmaster. The darker green to the right is the Chief of Staff. Same engineer.

Those terms come from Waleed Kadous' "The Seven Spheres of Human-AI Co-Development." Quick version of the two stages on either side of that line:

- Sphere 5 Chess Grandmaster: You run several AI agents in parallel and move between them, like a grandmaster playing multiple boards at once. One builder is working while you check on another. It's fast, but you are the one doing all the coordinating, so you are the bottleneck.
- Sphere 6 Chief of Staff: You hand the coordination to the AI. You set the direction, the Architect breaks it into specs, spawns the builders, reviews their work, fits the pieces together. You oversee. Waleed calls the move that unlocks this "delegating the delegation".

Amr read the article when it came out in December. Then he spent six months trying to make the jump without losing sight of what every agent was doing:

"I've spent six months trying to make the Sphere 5 to Sphere 6 transition work, from Chess Grandmaster to Chief of Staff. The hard part isn't delegating; it's maintaining visibility and control when you do.

The VS Code extension was what closed that gap: every builder visible at a glance, dev-approvals that drop me into a running worktree to test, plan and diff review in-editor, and the architect coordinating the delegation, handing back 'what's next?' the moment I'm ready. Delegation with visibility intact. That's what makes Sphere 6 viable in real-world production scenarios."

He got there about two weeks ago. The backlog UX overhaul in v3.1.6, the Builders tree clarity, the VS Code extension work across recent releases all came from the right side of that line. And Codev built Codev, since that VS Code extension is the thing that got him across.

It's Codev all the way down.

Try Codev: