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...
stephenpontes•1h ago
AI enables quick shipping, but the traditional moat of development no longer applies.