They see the entire universe building their own version of Claude Tag and custom internal bots connected to your internal ecosystem, and realizing that they can fight for some enterprise revenue within their own product that everyone else is currently extracting
Slack wants to be primary place people do their work. And they're almost there... It's certainly where you "work" (communicate) with people, it's where many engage with and/or control other platform like project trackers, and it's increasingly the place you interact with whatever AI agents your company uses. It makes perfect send they want to bring the coding agent into the fold (into their UI) as well. And, given Anthropic's release of Claude Tag, they're probably not wrong about that.
> 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, if this type of thing annoys you than the whole feature probably will too.
The collective harm that this kind of language does to a human skill of writing by oneself is probably immeasurable (that is until some clever social science researcher finds a controlled way to quantifying this).
The full statement:
> This isn't just a new feature — it’s a new way to build software: open, collaborative, and powered by both human ingenuity and judgement and agent scale. Teams that build this way won't just move faster. They'll build things no one else can.
I am not sure how just drawing contrasts between two things without actually drawing any kind of causal relationship to explain _why_ something is better or _how_ it does it, came to be a good thing. It is the kind of vaccuous statement that some poor tired sod with his remaining system 1 capacity just YOLOd into the blogoshpere and, like you said, the weary who don't know any better get FOMOed by. PSA: you arent missing anything.
I don't understand what you want to hear. You can still code manually all you want, but people will not pay you for doing that in the near future. You can still do it for your personal projects.
I like writing code too. What I don't like doing is debugging code that just isn't doing what I want. Debugging CSS layout issues in Safari vs Chrome vs Firefox? Screw that...agent do it. Debugging layout issues in a React Native mobile app on Android on that one weird screen layout phone? Screw that....agent do it.
I dunno dude, it's getting scary fast. You tried a fable/5.6sol maximum effort on a chunky task yet?
Maybe in a few years being a good coder will be like being a good taxi driver with self driving. You know the best spots and the ai can't drive the most unusual roads but effectively 95% of all driving is self driving.
Interesting that you use self driving as the metaphor here, when we've been told for years that self driving will be taking over the roads any day now... and yet...
I use waymo all the time? It's literally here. I massively prefer it to a cab. Only question left is how long it takes to scale and make cheap.
Prolly what, 30yrs? Places like SV or other advanced locations will hit majorty faster than that. The rest of the world ~50yrs.
Hype is fast but tech is a decades rollout. AI will hit its stride in 5-10yrs. Which is scary because it's already stupidly powerful. Saturation of AI though is still a 20yr+ horizon.
Remember six months ago when linkedin people were adamant you needed to keep on top of everything not to get "left behind"? Agents, skills, mcps, swarms ...
If anything, my setup has gotten ever so simpler as models got better.
I open my editor, I need to implement a feature, I tell chatGPT what I need, it reviews my code and provides suggestions. I then tell it to implement it. I then tell it to write tests. I review the code.
I test it. I have another AI do code review. I push it to test, then after tests to production.
For some common tasks, that I don't find interesting it is great. I do a lot of CRUD, I honestly cannot imagine writing these apps without AI.
It made curious and freed my brain to think about other things. I am now playing with hardware and plan on launching a niche product. This would not be possible if I 100% committed to programming without AI.
Letting it rip and give it full infra, db, dns, all the keys to the castle, drinking from a telemetry firehose the whole time, a huge tangled web of integrations that all kind of works. I think just offloading as much as possible is the state of things.
"I know folk's got their ways of doing things. Live where the low fruit hangs, that's how it is." - Charley Crockett
There's plenty of ideas, they just don't have them [1]. It's kind of hilarious to watch all of these people copy each other out of fear while pretending they're being original.
SaaS companies never had any ideas in the first place past turning a one off software cost into a monthly one and making you an addict of their crack supply. The coding agent just puts them between you and getting shit done again so they can monetize it. Milk you dry.
Seriously just fuck the whole industry and walk away! Go back to emailing spreadsheets and documents around. Save your shit to your own hard disk. You don't need a todo app - just post-its stuck to your fucking monitor. Call someone on the fucking phone. Crack your software or use OSS. Run it all on recycled PCs. Stop giving everyone money for this shit because it's only normalising your subscription future.
Note: I work for a SaaS company. They are bastards. They all are.
Like they say this is a new way of coding, anyone can build ANYTHING and they chose to make another Claude Code and presents it like its an original invention
This is how software trends go. AI has already had several of these; it started with every site needing their own chatbot powered by AI. A decade ago, every product was trying to integrate some sort of blockchain. It takes time for them to shake out to where they actually belong.
The amazing thing is that there is almost always an open-source alternative that is 10x better in many ways, in the case of slack https://mattermost.com/
I'm looking forward for AI to make it very easy to deploy your own tools and walk away from all this SAAS.
slack, jira, notion, even google suite
AI makes the cost of software development much lower, which means you can have a very good alternative that you can self host.
I'm thinking of companies that has 1000+ employees that pay millions annually in SaaS subscriptions.
SaaS is a tax on b2c business that will be reduced.
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?
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.
Two things: (1) models are far more autonomous and run for longer coherently, (2) visibility into the development process was lost in local development.
Because models run for a long time autonomously developers need to manage more agents simultaneously. At that point you basically need a tracker for tasks in flux, and compute for each agent. It also means that the interactive monitoring isn’t as helpful anymore.
Regarding visibility, developers now think in high level architecture rather than lines of code, but implementation details are still important to document. We also want to understand when agents are hitting pain points. Both of these basically require archiving agent outputs more deeply than just code changes and commits.
I see. What would the proper solution then look like for when we should consider moving our teams? Sounds like you you said they're all current ones are missing ergonomics. Do you think it's slack code?
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.
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.
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.
93 comments
[ 0.23 ms ] story [ 4.0 ms ] threadhttps://www.youtube.com/watch?v=Z0GFRcFm-aY
Personally, I'm getting ecosystem fatigue. Who even has the time to set up pilots to feature-test all these different systems?
I imagine they smushed 2 of the most well-known AI-isms together on purpose here to troll the AI-weary. Might as well, if this type of thing annoys you than the whole feature probably will too.
The full statement:
> This isn't just a new feature — it’s a new way to build software: open, collaborative, and powered by both human ingenuity and judgement and agent scale. Teams that build this way won't just move faster. They'll build things no one else can.
I am not sure how just drawing contrasts between two things without actually drawing any kind of causal relationship to explain _why_ something is better or _how_ it does it, came to be a good thing. It is the kind of vaccuous statement that some poor tired sod with his remaining system 1 capacity just YOLOd into the blogoshpere and, like you said, the weary who don't know any better get FOMOed by. PSA: you arent missing anything.
- my very late grandfather b1913, in my view warning me about people looking for suckers
> so building software — from idea to shipped product — isn't just for engineers anymore.
> No ticket, no meeting, no waiting — just a fix, shipped.
> This isn't just a new feature — it’s a new way to build software
It's the same damn structure again and again. It's so gross.
Is yours?
Good times ahead!
We're still paying leagues of people to install systems from USB keys. PXE has existed for decades. You have absolutely no idea.
I still like reviewing code, but I don’t need to physically write it
Maybe in a few years being a good coder will be like being a good taxi driver with self driving. You know the best spots and the ai can't drive the most unusual roads but effectively 95% of all driving is self driving.
Coding has changed butbuissness has not.
1.5 million people use it for 90%+ of their drives
Prolly what, 30yrs? Places like SV or other advanced locations will hit majorty faster than that. The rest of the world ~50yrs.
Hype is fast but tech is a decades rollout. AI will hit its stride in 5-10yrs. Which is scary because it's already stupidly powerful. Saturation of AI though is still a 20yr+ horizon.
If anything, my setup has gotten ever so simpler as models got better.
I test it. I have another AI do code review. I push it to test, then after tests to production.
For some common tasks, that I don't find interesting it is great. I do a lot of CRUD, I honestly cannot imagine writing these apps without AI.
It made curious and freed my brain to think about other things. I am now playing with hardware and plan on launching a niche product. This would not be possible if I 100% committed to programming without AI.
There's plenty of ideas, they just don't have them [1]. It's kind of hilarious to watch all of these people copy each other out of fear while pretending they're being original.
[1] https://www.youtube.com/watch?v=nMfHYUFeiJo
Seriously just fuck the whole industry and walk away! Go back to emailing spreadsheets and documents around. Save your shit to your own hard disk. You don't need a todo app - just post-its stuck to your fucking monitor. Call someone on the fucking phone. Crack your software or use OSS. Run it all on recycled PCs. Stop giving everyone money for this shit because it's only normalising your subscription future.
Note: I work for a SaaS company. They are bastards. They all are.
I'm looking forward for AI to make it very easy to deploy your own tools and walk away from all this SAAS.
slack, jira, notion, even google suite
AI makes the cost of software development much lower, which means you can have a very good alternative that you can self host.
I'm thinking of companies that has 1000+ employees that pay millions annually in SaaS subscriptions.
SaaS is a tax on b2c business that will be reduced.
https://buzz.xyz/
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.
Next up - Slack releases a model router. Cloudflare builds an agents platform. OpenAI acquires a dev tools startup.
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.
Im not convinced of any of these cloud or tagging solutions where I get to the point of moving coding away from my dev's machines.
Because models run for a long time autonomously developers need to manage more agents simultaneously. At that point you basically need a tracker for tasks in flux, and compute for each agent. It also means that the interactive monitoring isn’t as helpful anymore.
Regarding visibility, developers now think in high level architecture rather than lines of code, but implementation details are still important to document. We also want to understand when agents are hitting pain points. Both of these basically require archiving agent outputs more deeply than just code changes and commits.
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.