My First Coding Agent Fleet with Enterprise Tooling

Last week I was at the AI Tour in Munich. Andreas Krüger introduced me to Squad. A GitHub project from a group of Microsoft Engineers. (THX Brady Gaster)

And what can I say, it’s been rattling around in my head ever since.

The Idea

In our internal app, users can submit feedback and ideas. Screenshot it, add details, send it. All gets processed internally and simultaneously synced to a GitHub issue list.

I get a notification in Teams, follow the link, look at the feedback and tag the issue with squad:copilot if I think it’s the right one for the job.

And from there, the GitHub Copilot Agent takes over. It looks at the feedback and starts implementing. When it’s done, I check what came out and decide if it fits or not. Theoretically even on my phone. No matter where I am.

So features and ideas end up in the app without me having to sit at a desk.

Squad in the Terminal

And when I do take a seat at my desk? Squad is a whole team of agents in the GitHub Copilot CLI that supports me with ideas and implementations right in the terminal.

I knew this day would come. But now that it’s here, it feels pretty surreal.

The Reality

For a couple of weeks now we’ve been seeing similar things from the open source and consumer world. Coding Agent Fleets aren’t a concept anymore. They’re reality.

This here is my first Coding Agent Fleet with Enterprise tooling. From user feedback to finished feature. Orchestrated by agents and put together in a way that makes it super easy for devs to develop things themselves too.

What This Means for Companies

We never had such good opportunities to go with “Make” instead of “Buy” as we do now. How sensible that is at scale is a whole other story.

But I’m pretty sure this exact discussion will be pretty intense in the coming months.

It won’t get slower anymore…

Many thanks to Andreas Krüger for introducing me to Squad and to Brady Gaster for the project!