[flagged]
Claude Tag
121–130 of 200 posts
Re: Claude Tag
#122I don't understand how this is gonna fly for enterprise security and compliance. Claude needs to inherit permissions from somewhere, and those permissions will never align with the members of a slack channel. And finding the lowest common denominator of access probably results in a dumbed-down, useless experience. The only way it works is if customers truly start treating agents as humans with the same liability as a…
What's cooler is then it can view/add/remove people from channels, so it can conduct access reviews -- overall I consider it a security improvement.
Re: Claude Tag
#123I know this is much easier said than done. And my comment is partly tongue-in-cheek.
But Slack isn't great. It isn't loved.
I don't understand why Slack still doesn't have a true single inbox view of all activity.
And their LLM integration is poor, for what feels like one of the clearest use cases for a rich LLM chat experience -- to discuss what's happening in a channel, filter cruft, and ask an agent to take actions against MCP productivity tools like add a todo, etc.
Slack's current AI integrations are piss poor. Just summaries with zero customization. I mean, isn't it obvious that's not good enough?
Eventually a ground-up rethink of Slack in an LLM age is going to displace Slack.
They'll likely survive forever as an enterprise provider, like Microsoft Office and related tools, simply because of integrations, etc.
But Slack feels ripe for disruption.
Re: Claude Tag
#124> 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.
How much do you think it’s holding them back? Market share seems to be surviving the lack of quality vs the other players. Or possibly: they’re focusing where it matters?
Re: Claude Tag
#125Earlier quoted context omitted.
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.
To go after the non-developer side though they need to do a ton more work on governance & RBAC. It's sorely lacking for anything more than a tech company/startup team. You can't even selectively enable or disable Cowork & Claude Code per member on the team plan, it's all or nothing for everyone in the team.
Re: Claude Tag
#126They shoudl just expose SDK/platform for people to build own integration with Discord/Teams/mattermost etc. This would allow for fine grained permisions control and speed up adoption. To large degree this is alternative for OpenClaw ?
Re: Claude Tag
#127Is 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.)
At my work we rolled out Cowork to all the non-technical staff. People are using a ton, wired up for read access to M365, Confluence, etc. as sort of a psuedo enterprise RAG + all the document creation/file management it can do. I know my users would actually like Claude Tag, but unfortunately we are in Teams, not Slack, as are most other non-tech companies. Cowork/Claude Desktop itself is also quite a frustrating pr…
https://www.microsoft.com/en-us/microsoft-365/blog/2026/03/0...