Claude Tag

I wouldn't call this minor. The 2 big features seem to be integrated memory + ambient proactiveness. This requires pretty intense tuning to not be annoying.

It's a major rewrite of the slack plugin, with far more functionality and more capabilities. More surfaces will be available in the future

I spoke with a (potentially biased) member of technical staff @ Anthropic today who claimed that tags w/ multi-player capability is the biggest thing they've shipped since Claude Code.

We have the opposite problem. We've tried this slack integration (first with NanoClaw, then Hermes, but now just building our own), and we actually want the OPPOSITE.

In private context, I want to have a per-person conversation with durable context for that person's private chats. I also want that person's permissions to extend. Like contractors in our slack should only be able to ask and get back information about clients that they've been attached to, not our entire knowledgeable.

And we've implemented ALL that, but just with a lot of custom code. We've put in interceptors that put in per-user keys into the MCP connection so only certain tools are even exposed, etc.

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.

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.

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.

I use design. It's nice enough for me.

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.

Lots of people use design

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.

Sliced Bread™

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).

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

Wow, that's absurd

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.