At this point I literally have no idea what modern coding is supposed to look like. I still open my editor, type stuff in and run make. All these tools are released daily and they just fly over my caveman head.
Oh great, I look forward to our next Slack renewal when they foist another 125% licensing increase on us for yet another AI add-on we don't want. This year, they decided that our Enterprise plan wasn't paying for another floor on Benhioff's tower fast enough and so forced an 125% license increase. They then played the game of "if you renew early, we're going to cut you a special one-time deal because we're feeling generous and allow you to renew at a slightly discounted rate, subject to the approval of our deal desk, of course ". barf.
SaaS companies have run out of ideas. No one truly needs another coding agent. I weep for SaaS's future.
I'm going to chock this one up as a yet-another "X is your agentic coding hub" PR nonsense.
What are people actually using to manage semi-collaborative agentic coding workflows nowadays? We've moved from on-dev-machine coding to @claude in GitHub, but of course GitHub purposefully weakens the capability of that approach to the point that it's kind of a hack. Github/Linear have somewhat more cohesive experiences but it still feels like tooling for agent teaming is quite lacking and unergonomic.
Given that like omnigent and qm already integrate with Slack, it's not a huge surprise that Slack is building agent capabilities directly in.
Personally, I'm getting ecosystem fatigue. Who even has the time to set up pilots to feature-test all these different systems?
Somehow I was hopeful that this would be an announcement about adding syntax highlighted code blocks to Slack messages.
I'm shocked Teams + GitHub haven't already done something like this. But I suppose that's asking a lot from Teams.
I've been using Claude and other agents in Slack for some code tasks. It's mostly fine for simpler projects and products. Things like docs or specific libraries. But I'm not really convinced this is the ideal interface yet. Reviews are my bottleneck and GitHub has a great UI for this. Plus, token consumption with Slack is out of control.
Maybe in time this will be the way we work, but for now I still find myself using GitHub, a terminal, and slack together.
Is this basically trying to do something similar to Zed's https://delta.dev/, but from Slack instead of an IDE?
Looks like a great way to replicate the setup of "four guys standing around watching one guy do the work" but the one guy is Claude now.
Hey Slack, how about making workflows less of a pain in the neck to use? In them there is no ability to have branches rejoin to a common path. Worse, an item isn't found in a list it just throws an exception instead of giving me a null item, which oddly I can test for in an if even though it will never happen?
This is probably getting close to the right interface for these things, and that's coming from someone who is religious about using terminals, neovim, etc.
Sounds useful for a PM wanting to spin up a throwaway PoC. But you’d have to rip my IDE from my cold dead hands for any work that extends past the threshold of KTLO.
Every time I'm reminded that Slack is part of Salesforce, I become nostalgic for the good old days
Slack is fine, but the moment they start bringing that stuff into Jira...
The title got me thinking Slack had open source its code
When we can code in English, now we can code in group chats.
Maybe it’s the future. Where I can join to coding/spec driven channels to observe or help.
I would do this - coding/spec driven in public. Hope it will be the future.
It would allow also non devs to join.
Coding in slack was not on my bingo card.
I feel at this point all new AI announcements can be auto generated by AI.
Next up - Slack releases a model router. Cloudflare builds an agents platform. OpenAI acquires a dev tools startup.
A new way to make Slack more annoying
What even is this feature?
You can’t just “spin Claude up in slack”; it can’t magically just connect to GitHub and your code.
I presume this feature basically is like… if you’re already using your agents in cloud hosted runtimes, then you can connect to those agents like you already are, but via slack.
…
Did I misunderstand?
This seems like a non feature; if you’re bring to want it, you can’t have it because you have to setup Complicated External System, and if you’re already using cloud hosted agents, you’re already using it (eg. Claude tag or whatever).
So it’s what… a diff viewer in slack? An agents tab so slack becomes like cursor?
The videos seem enormously light on examples of how it actually works, did someone find a more detailed example of usage to show why you want this?
wish i could use slack again, stuck with teams and the code sharing experience is meh
Oh look it's a Buzz clone
> This isn't just a new feature — it’s a new way to build software
I imagine they smushed 2 of the most well-known AI-isms together on purpose here to troll the AI-weary. Might as well I guess, if this type of language annoys you then the whole feature probably will too.