The next big thing is Asynchronous Coding Agents.
Such Agents change our role as engineers from Conductor (directing one agent at a time) to Orchestrator (defining tasks for a "fleet" of agents working in parallel), for very well-defined tasks with human review.
@github's ed at #githubuniverse, is one such example I've been trying and liking.
There are a number of options also worth considering, including @julesagent (also great!), Codex web by @OpenAIDevs, and Anthropic's Claude Code for web. Editors like @cursor_ai are also exploring this with some very interesting UX ideas.
For the more advanced, orchestrators like Claude Squad, Magnet and Conductor by @charlieholtz (nice balance on the engineering/product spectrum) are certainly worth considering.
Some caveats: Orchestration has been working well for me in small-medium sized projects: for fixing UI bugs, adding small features etc. This can be good for tackling migrations, upgrading dependencies etc. Enterprise teams are very much still figuring out their "Conductor" patterns but eventually, I do see more orchestration becoming a standard part of the engineering workflow.
Such Agents change our role as engineers from Conductor (directing one agent at a time) to Orchestrator (defining tasks for a "fleet" of agents working in parallel), for very well-defined tasks with human review.
@github's ed at #githubuniverse, is one such example I've been trying and liking.
There are a number of options also worth considering, including @julesagent (also great!), Codex web by @OpenAIDevs, and Anthropic's Claude Code for web. Editors like @cursor_ai are also exploring this with some very interesting UX ideas.
For the more advanced, orchestrators like Claude Squad, Magnet and Conductor by @charlieholtz (nice balance on the engineering/product spectrum) are certainly worth considering.
Some caveats: Orchestration has been working well for me in small-medium sized projects: for fixing UI bugs, adding small features etc. This can be good for tackling migrations, upgrading dependencies etc. Enterprise teams are very much still figuring out their "Conductor" patterns but eventually, I do see more orchestration becoming a standard part of the engineering workflow.
12
15
158
17,579
@addyosmanis@githubomes a true skill! but I see EaaO/EaaS to happen at some point sooner.
Orgs maintained by a fleet of agents.
Orgs maintained by a fleet of agents.
Oct 29, 2025 · 4:12 PM UTC
1
0
0
213
@sendilkumarn @github Oh for sure. Lots of discussions happening right now about quality of PRs, velocity vs. sufficient reviewers where slop is concerned.
0
0
2
271