Given the reliability and general product quality of the Anthropic product team's code, this doesn't sound like a selling point.
Claude Tag
71–80 of 200 posts
Re: Claude Tag
#72Slack is such a simple product, and is so strategic as an interface for AI, Anthropic has to be considering building their own Slack. Hopefully this tag approach is an MVP and it proves the potential of workplace messaging as an interface for AI, but also the limitations of relying on the extension points they salesforce chooses to provide, and it turns into a full fledged slack competitor from anthropic soon.
Why? What does Anthropic have that any other software company that's capable of putting MCP integration in a chat app doesn't?
Re: Claude Tag
#73We ought to rename HN to "The Claude Blog". This is a minor feature update to a slack plugin.
Re: Claude Tag
#74It 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)
Re: Claude Tag
#75Re: Claude Tag
#76It'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.
Devin is model agnostic, and isn't Slack only.
Re: Claude Tag
#77> Today, 65% of our product team’s code is created by our internal version of Claude Tag. Given the reliability and general product quality of the Anthropic product team's code, this doesn't sound like a selling point.
Re: Claude Tag
#78Re: Claude Tag
#79I read this as "Claude integration to Slack is now billed as API usage". Is that wrong?
Re: Claude Tag
#80The 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 collaborative…
Discussing what needs to be done next, and having it automatically sort it into what subtask it is, if it applies or is blocking to multiple other tasks. Recording specifications, measurements, dimensions. Being able to ask other people facts and have them correctly documented into the right task.
Company Brain / Knowledgebase is imho more rear facing, whereas todo is future facing.