That explains a lot.
edit: note this may not be official release, and may be unavailable for some users. I saw it show up yesterday listed as available Mcp and used it to view projects in Claude design.
I expect many of those to be shut down sooner than later, if learning anything from Google.
> @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.
[0] "Editing this message will create a new conversation branch. You can switch between branches using the arrow navigation buttons."
From reading that and materials on it, it seems unclear if – let's say you do what's done in the demos on the site and 'dispatch work' from a thread in a shared channel (e.g. from some discussion) – that if any one of your coworkers replies below you and says, "Actually, could you fold in <blah> as well?" that Claude wouldn't listen to them and thus derail the work.
During an incident, how do I know which Claude Tag called AWS?
> Think of it as creating separate Claude identities for different uses: everything, including its memories, will stay scoped to the channels defined by the administrators. For example, a model set up for sales work won’t pass on memories to one set up for engineering; nor will it give engineers access to any sales data or tools. More information about provisioning access is available here (https://claude.com/blog/agent-identity-access-model).
I'm still using it all the time and getting an immense benefit.
A tiny detail...
I think that people see the word "claude" and smash the upvote button. I don't think it's botted. My guess is that people just want another place where they can discuss ai coding workflows.
The best part for me is seeing non-technical folk spec out something in a thread that they discussed something and letting the agent go ahead and build it ready for the humans to review later.
Yeah, that explains a lot.
The difference between this and our agents is that they are context aware - i.e. you can use them privately to access personal information safely.
Can provide a link if interested.
We do signal to Claude that there's a difference between a conversation's initiator versus incoming participants and we've found that in situations where people disagree on an approach, Claude patiently waits for a resolution while correcting any misunderstandings.
It's also worth mentioning that since Claude has its own identity, a coworker cannot enter a thread and commandeer _your_ identity; you collectively steer how Claude acts with its _own_ identity (it opens PRs as itself, browses Datadog as itself, etc).
stephenpontes•1h ago
AI enables quick shipping, but the traditional moat of development no longer applies.