logoalt Hacker News

SweetSoftPillowtoday at 5:40 PM2 repliesview on HN

The most important difference from other products:

> @Claude is multiplayer. Within a given Slack channel, there’s one Claude that interacts with everyone. This means that anyone can see what it’s working on, and can pick up the conversation from where the last person left off. This makes tagging Claude very different from working within a single chat or for a single task—it’s much more like interacting collaboratively with a teammate.


Replies

ceroxylontoday at 6:04 PM

Hopefully there is some sort of version history implemented or planned like they have in Cowork[0]... this sounds great until a co-worker hijacks your Claude session with a worse idea and derails it from what you were intending.

[0] "Editing this message will create a new conversation branch. You can switch between branches using the arrow navigation buttons."

show 1 reply
kentmtoday at 6:14 PM

Thats a double-edged sword in some scenarios. If you're trying to keep info private then feeding it into a shared agent basically means that you can't guarantee that privacy. I'd imagine the approach here would be to have separate agents for private data and then restrict Slack access, but I could imagine tons of accidents from managers that habitually @Claude without understanding the implications.

show 1 reply