11–20 of 200 posts
> @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.
During an incident, how do I know which Claude Tag called AWS?
Is someone here using a Claude product that's not code? I'm puzzled about the amount of products they put out. I know a lot of people using Claude but we're all using the terminal-based code. Even for non-engineering stuff it suits great (tax documents, 3D modeling with blender through MCP, academic research, etc.)
Is someone here using a Claude product that's not code? I'm puzzled about the amount of products they put out. I know a lot of people using Claude but we're all using the terminal-based code. Even for non-engineering stuff it suits great (tax documents, 3D modeling with blender through MCP, academic research, etc.)
It feels like they release 1 or 2 "products" a week and then we never hear about them again.
I’d be curious how they’ve solved the attribution/provenance/identity problem here. Are instances of Claude Tag, across channels, sharing the same identity? Can I grant one instance access to a range of AWS roles and another instance access to other roles? 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).
Is someone here using a Claude product that's not code? I'm puzzled about the amount of products they put out. I know a lot of people using Claude but we're all using the terminal-based code. Even for non-engineering stuff it suits great (tax documents, 3D modeling with blender through MCP, academic research, etc.)