Sep 23, 2026 · 30 min · 13 segments
SPONSORED BY SLACK BY SALESFORCE In this episode, Ryan chats with the GM of Slack, Rob Seaman, about how their new Code Channels feature is bringing multiplayer AI to your team chats. They discuss…
Rob SeamanGuestRyan DonovanHostYeah, you talked about spinning up these code channels and treating them, I assume, a little bit more disposable.
Do you have recommended behaviors? Do you spin up a code channel for a feature? Do you do it for a single bit of programming and then kill it? Or what's the patterns you've seen?
I mean, you could have multiple PRs, but it's more like that session or PR, couple PR level than it is an entire feature.
And we did this particularly so we didn't clutter up your sidebar, but also encouraged you to use it as much as makes sense for you.
And so you'll see they actually show up in a new section in your sidebar on the left in Slack.
And as soon as they're done and you spin down the infrastructure, it effectively archives the channel, leaves your sidebar, but it's still a searchable asset.
So all the things that happened in that particular channel, the session artifacts, the code itself.
One was how they show up in your sidebar next to all the other work that you're doing and making sure it doesn't clutter it.
And then two, the actual chattiness of the interface with the agent so it doesn't become annoying.
I know one of the problems that's arisen or at least become visible because of agentic coding is code review.
You know, because you're seeing, I mean, frankly, it's a lot of the process that's getting mashed together.
It's like problem identification, you know, screenshot, like this doesn't look right.
Yeah, you talked about spinning up these code channels and treating them, I assume, a little bit more disposable.
Do you have recommended behaviors? Do you spin up a code channel for a feature? Do you do it for a single bit of programming and then kill it? Or what's the patterns you've seen?
I mean, you could have multiple PRs, but it's more like that session or PR, couple PR level than it is an entire feature.
And we did this particularly so we didn't clutter up your sidebar, but also encouraged you to use it as much as makes sense for you.
And so you'll see they actually show up in a new section in your sidebar on the left in Slack.
And as soon as they're done and you spin down the infrastructure, it effectively archives the channel, leaves your sidebar, but it's still a searchable asset.
So all the things that happened in that particular channel, the session artifacts, the code itself.
One was how they show up in your sidebar next to all the other work that you're doing and making sure it doesn't clutter it.
And then two, the actual chattiness of the interface with the agent so it doesn't become annoying.
I know one of the problems that's arisen or at least become visible because of agentic coding is code review.
You know, because you're seeing, I mean, frankly, it's a lot of the process that's getting mashed together.
It's like problem identification, you know, screenshot, like this doesn't look right.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.