@SlackHQ team invited me to a private launch of Slack Code, which went live this morning. A few of us in the room on the 61st floor of @salesforce Tower, which is a very different experience from a launch keynote. You can actually ask the real question and get an answer. The short version: coding agents move out of private tabs and into a channel. You tag an agent, it opens a channel for the task, and the plan, the code changes, and a live preview all sit there where the team can watch, steer, or stop it. Claude, Devin, Copilot, ChatGPT, and Vercel's agents are all in it on day one. Always good to catch up with Rob Seaman, EVP and GM of Slack at Salesforce, who opened the session, and with @jeffwang, President of New Enterprise at @cognition, on where Devin fits in a shared channel. Two things landed for me. As a founder, building alone is lonelier than anyone admits. You make ten decisions before noon and nobody sees nine of them. Watching agent work happen in a channel where a teammate can just walk in and redirect it felt like the first time this stuff stopped being single player. As a vibe coder, the win is context. Every version of this I've tried lives in a tab that forgets what my team already decided. Here the conversation, the code, and the history sit in the same place, so the next person picks up where you left off instead of starting over. What I'm watching now is who ends up using it. If the people steering these channels aren't only engineers, the interesting question stops being how fast teams ship and starts being what a team even looks like. Also spent time with the @SalesforceVC team and their port cos, a good number of Salesforce and Slack execs, and ran into a few amazing tech creator friends. Slack picked the one room in San Francisco where you can see the whole ecosystem out the window and half of it standing next to you. Huge thanks to Slack and Salesforce for having me. See you at @Dreamforce. #salesforce# #slack# #ai# #dreamforce#