Cursor has had this a while, integrated with their web agents. It was a bit buggy to begin with, not working well with non-github repos, but it was improving last time I checked and was pretty decent.
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.
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.
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."
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.
Every channel has its own Claude, and Claude's access is configurable per-channel and per-workspace. Private channels don't leak information to other channels
Is this still using Claude Web sessions? Also, has anyone used Claude Web environments to do anything besides stuff with repo access? Like running real environments? SSHing into anything more super powered? Anyone putting real creds into those environments?
yeah. exactly. they have these "self-hosted sandboxes" which seems to be the unlock we'd need. https://platform.claude.com/docs/en/managed-agents/self-host... but those only seem available to their "managed agents" so like "scheduled prompts" i think. one day i assume they'll merge Claude Web sessions with these self-sandboxes maybe
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.)
I use Claude Desktop (& essentially equivalent mobile app) to ask frivolous aspie questions about things society long ago accepted. I enjoy its responses, interpret how you wlll. (my claude.md file has instructions to tell it that the premise of any question i ask is as likely as not wrong, and to never be sycophantic).
But beware the userMemories file (ask Claude to give you a dump of it). bonus points if you can figure out where that file lives.
At first I was freaked out that usermemories is a subpoena’able psychological profile on me. Then I realized that the same file will be produced for spooks all over Langley, so that the day Anthropic gets hacked those profiles will see the light of day (caveat along with the rest of the user base of course) and so I felt more catharsis as a result.
And it sometimes feels like these teams are not talking to each other. Using Claude Design? The way to hand it over to Claude Code is to download a .zip file with the html mockup and some description, which you then have to copy into Claude Code so it can use it.
The latest version of Claude code as of yesterday or day before has Claude design Mcp so you don’t need to do this now.
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.
This happened at Google because there aren’t enough engineers to maintain all these services. This situation may not apply to Anthropic, as they can set up features to be maintained in perpetuity by Claude.
They are going after the non-developer side of the business. Many developers are far less sticky and want to try out different harnesses and models. Case in point, our biz team all has Claude Desktop / Enterprise, developers get choice and there are a lot of setups.
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).
I actually think that "multiplayer" AI usage is very neat I've done a few things where I made a simple telegram wrapper and me alongside a couple of other people were prompting it at the same time to improve a website design / ux. But definitely not whatever the hell this is, how can anthropic make products so much worse when presumeably having access to infinite fable/mythos.
Cursor has had this a while, integrated with their web agents. It was a bit buggy to begin with, not working well with non-github repos, but it was improving last time I checked and was pretty decent.
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.
We ought to rename HN to "The Claude Blog". This is a minor feature update to a slack plugin.
It's a major rewrite of the slack plugin, with far more functionality and more capabilities. More surfaces will be available in the future
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.
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."
this is discussed in https://claude.com/blog/agent-identity-access-model
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.
Every channel has its own Claude, and Claude's access is configurable per-channel and per-workspace. Private channels don't leak information to other channels
Is this still using Claude Web sessions? Also, has anyone used Claude Web environments to do anything besides stuff with repo access? Like running real environments? SSHing into anything more super powered? Anyone putting real creds into those environments?
That seems to be the biggest limiter, hard to have it do real work on a codebase without it's own environment set up that we can control.
yeah. exactly. they have these "self-hosted sandboxes" which seems to be the unlock we'd need. https://platform.claude.com/docs/en/managed-agents/self-host... but those only seem available to their "managed agents" so like "scheduled prompts" i think. one day i assume they'll merge Claude Web sessions with these self-sandboxes maybe
Maybe we can start adding these things to the list.
https://news.ycombinator.com/item?id=48641261
Hermes can also do this when you connect it to Slack, and having Hermes in slack where multiple teammates can share a context window is indeed nice.
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.)
I use Claude Desktop (& essentially equivalent mobile app) to ask frivolous aspie questions about things society long ago accepted. I enjoy its responses, interpret how you wlll. (my claude.md file has instructions to tell it that the premise of any question i ask is as likely as not wrong, and to never be sycophantic). But beware the userMemories file (ask Claude to give you a dump of it). bonus points if you can figure out where that file lives. At first I was freaked out that usermemories is a subpoena’able psychological profile on me. Then I realized that the same file will be produced for spooks all over Langley, so that the day Anthropic gets hacked those profiles will see the light of day (caveat along with the rest of the user base of course) and so I felt more catharsis as a result.
And it sometimes feels like these teams are not talking to each other. Using Claude Design? The way to hand it over to Claude Code is to download a .zip file with the html mockup and some description, which you then have to copy into Claude Code so it can use it.
The latest version of Claude code as of yesterday or day before has Claude design Mcp so you don’t need to do this now.
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.
They're pretty much going the Google (how Google was until recently), trying to fan out to every market share.
I expect many of those to be shut down sooner than later, if learning anything from Google.
This happened at Google because there aren’t enough engineers to maintain all these services. This situation may not apply to Anthropic, as they can set up features to be maintained in perpetuity by Claude.
Lots of people use design
Design has been very hit or miss for me. I've had more success with Claude Code and the frontend-design skill.
They are going after the non-developer side of the business. Many developers are far less sticky and want to try out different harnesses and models. Case in point, our biz team all has Claude Desktop / Enterprise, developers get choice and there are a lot of setups.
I use design. It's nice enough for me.
A bit strange to create a brand name for "I tagged the slack app I want to interact with"
Sliced Bread™
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?
This is explicitly answered in this post:
> 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).
It feels like they release 1 or 2 "products" a week and then we never hear about them again.
If they find another success half as good as Claude Code it will all be worthwhile. (Monetarily good, not like, quality good)
we're in the throw shit at the wall and see what sticks phase
They are very proud of their approach if you listen to them on Lenny's Podcast. I find their products to be rather sloppy.
Meh. They are still behind current Agents mainstream IMHO
I actually think that "multiplayer" AI usage is very neat I've done a few things where I made a simple telegram wrapper and me alongside a couple of other people were prompting it at the same time to improve a website design / ux. But definitely not whatever the hell this is, how can anthropic make products so much worse when presumeably having access to infinite fable/mythos.
It's interesting to see Anthropic branching out into different areas now. First artifacts and now taking market share from companies like devin.
AI enables quick shipping, but the traditional moat of development no longer applies.
for 8,000 USD / month, no thanks.
Just got a stupid safety restriction on opus 4.8. Perhaps they should focus fixing that instead delivering this garbage chat integration.
Didn't they already have this?
>Set a limit on your organization’s monthly spend
A tiny detail...
I do this already with the Claude code telegram plugin and telegram groups
And here I was thinking we'd be getting Sonnet 5. Or maybe even poor old Fable back. Not this junk.
Ow. No.
I feel a great disturbance in the SAAS. As if millions of Slack API startups suddenly cried out in terror, and were suddenly silenced.
> Today, 65% of our product team’s code is created by our internal version of Claude Tag.
That explains a lot.
claude is too safety pilled to do anything useful these days anyways
Is there anything specific (and hopefully reasonable) that it refuses to do for you?
I'm still using it all the time and getting an immense benefit.