Post

...communication that deeply integrate with coding agents Current versions of Github, Linear, Slack, etc. were built for a previous era of development. They're too isolated from agentic coding tools. Trying to duct tape coding agents onto them isn't working. Coding agents and realtime...

...multiplayer humans all have to be in the same workspace. At @githubnext.com we've made a new research prototype called "Ace" in this direction It's like Slack, Github, Claude/Copilot, and a bunch of sandboxed cloud computers had a baby. Some demos:

1 repost22 likes

It's multiplayer chats, plus agents, and everyone working in sandboxed vms so you're all sharing the same code and context. Prompt and code together, in real time. You're all connected to the same computer. You can all see the same outputs. No one is stashing work and switching git branches.

Plans are also shared and editable as a team in real time. Because it is kind of insane to make elaborate plans with your coding agent alone in your terminal without getting anyone else's input. And then send it off to be implemented without checking if it's any good.

something we are trying to out in my team is using PR descriptions as a "plan"/"spec" document and i'm pretty happy with it for now. but love the idea of mixing slack + claude code + terminal

managing the flood of information and wall-o-text that will come from agents will be important. it's like a Slack that that gets 100 messages a day from the CI/CD process. and one of those is important. sometimes, you want to know what the agent did and sometimes, not. also, diff? +1

The definition of "good" for any system never sits in just one person's head (unless they're the only user of the system). Collaboration, communication and shared understanding have been challenges since the first days of software dev. It will be interesting to see how this is addressed.

Not sure I understand - each session here is its own branch. And you can make forks off of each branch. Or roll back to a previous commit. It's all just git under the hood. Or did you mean something else?

The 'duct tape' framing matches what broke for us building multi-agent coordination. Slack/Github/Linear treat every interaction as human-paced. Agents blow through that model. We ended up writing a JSON-file message bus because channels-and-threads just didn't work.