Work is a team sport. We can get good results working alone, but when a team gets in a room and focuses on the same problem at the same time, something changes. It can be a real power-up. Slack has fueled that kind of collaboration for a decade. Today, Slack is evolving into what we think of as an AI-driven work operating system. Collaboration is still at the center, but now it’s also a shared workspace where agents are real teammates, not tools sitting off to the side.
Today, most AI and agent use isn’t shared. One person, one screen, one agent in a private tab solving one problem. The person and the agent both learn something, and then the project ends, they move on, and the rest of the company never sees any of it. The knowledge stays in the tab.
AI is worth far more to a business when it works out in the open, in the same places people already work. That’s the idea behind this next era of Slack. Share context, build on it together, and generate more context as you go. That loop is how companies move faster and make AI work at real scale.
And that context is your edge. When an agent works in a shared space instead of a private chat, it picks up how your company actually operates — the projects, the debates, the decisions, all living in the conversations your team is already having. Every exchange with an agent out in the open becomes something the next person, and the next agent, can build on.
Picture a deal that hits a snag because a new competitor shows up. The instinct is for everyone to go back to their own screen and quietly ask their own assistant what to do. Instead, you just tag an agent — Slackbot — right there in a shared channel. Slackbot answers using everything it’s allowed to see: the account history, past research, the Salesforce records, the team’s own back-and-forth. Everyone in the channel sees the same answer at the same time, learns from each other, and works out a response together. And the agent gets smarter with every step.
We’re bringing that same idea to software development. Most coding agents today live in interfaces made for engineers and no one else. With Slack Code, a coding agent can open a shared channel around a piece of work, and anyone can join, watch it happen, and weigh in.
In that channel, the team and the agent build together and nobody’s left out of the loop. Each code channel maps to one project, so the space stays focused — live when you need it, archived when you don’t. Non-developers can weigh in conversationally; they don’t have to know how to operate within a technical environment. Because the work happens in real time and in the open, there are fewer status meetings and fewer tickets. Everyone can follow the plan, the code, the previews as they unfold.
And later, when someone asks why the team made a particular call, the reasoning is right there to look at. How and why the work happened stays with the team, ready to build on. The reasoning didn’t leave with the person who made the decision.
The single-player era of AI made people faster. The multiplayer era is what makes a whole company smarter, together.
Go deeper:
- Agentic coding is now multiplayer. Introducing Slack Code.
- For Gen Z workers, software has to be as intuitive as social media
- Pioneering Salesforce Engineering’s agentic shift: Part 2
