Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Tag

anthropic.com

Post reply on HN
Print view View original

131–140 of 200 posts

Re: Claude Tag

#131

Post by threecheese »

WRT “Claude learns over time” - this is the biggest gap for me in the current system. As I scale my usage of Claude at work, I observe that it’s quite bad at distinguishing what it should “learn” (memorize) from experimental or just wrong data. It builds and builds on a foundation of sand, making sometimes hidden assumptions and turning them into actionable insight thats just not correct.

It recently wrote an entire dissertation for an epic, assuming it was related to some other project, where it had earlier made the wrong guess about a vendor capability (from their marketing materials, no less), and it all had to be thrown away. I cleared the memory, but it appears to be still pulling from some corporate data source i cant control or locate.

Re: Claude Tag

#132

Post by kylecazar »

SAK_ATAK wrote: post #98

I 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…

An admin scopes permissions on a per-channel basis. It doesn't allow external actions until an owner specifically provisions that tool for that channel. I think.

But people can be invited to a channel after @Claude is provisioned. So yeah, I suppose you'll need to be deliberate about channel memberships.

Re: Claude Tag

#133

Post by subarctic »

Chyzwar wrote: post #126

Why Slack? Everything about this product sucks: bad video calls, no meeting recording, limited screen sharing, janky authentication, and predatory pricing. They 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 ?

This looks like a great enterprise product. Lots of companies will just enable it and voila they'll have claude in slack. They already have slack and their employees are probably used to Claude. I'm sure this will kill a few existing businesses and bring both companies more revenue

Re: Claude Tag

#134

Post by CRSilkworth »

I don't actually understand why this sort of thing isn't everywhere theres a discussion. Engineering wise, it's nothing to add. People use grok all the time on twitter.

Re: Claude Tag

#135

Post by sarracin0 »

thewebguyd wrote: post #66
phaser wrote: post #10

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

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…

[dead]

Re: Claude Tag

#136

Post by [deleted] »

threecheese wrote: post #131

WRT “Claude learns over time” - this is the biggest gap for me in the current system. As I scale my usage of Claude at work, I observe that it’s quite bad at distinguishing what it should “learn” (memorize) from experimental or just wrong data. It builds and builds on a foundation of sand, making sometimes hidden assumptions and turning them into actionable insight thats just not correct. It recently wrote an entire…

[deleted]

Re: Claude Tag

#137

Post by lowsong »

Yes connect the 3rd party company with a vested interest to capture as much of your data as possible with a direct pipe into all your internal sensitive discussions about your product, business, and market positioning in real time.

Has everyone collectively lost their minds? Suggesting anything like this even five years ago would get you laughed out of the room, and actually doing this would be a career ending mistake.

Re: Claude Tag

#138

Post by deadbabe »

kylecazar wrote: post #132
SAK_ATAK wrote: post #98

I 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…

An admin scopes permissions on a per-channel basis. It doesn't allow external actions until an owner specifically provisions that tool for that channel. I think. But people can be invited to a channel after @Claude is provisioned. So yeah, I suppose you'll need to be deliberate about channel memberships.

Which is a bad pattern. Around here, you can be granted access to most channels just with vague reasons for why you need to be in there. This is a disaster. Culture will degrade. Suspicions will grow. Security theater.

Re: Claude Tag

#140

Post by mukbangpervert »

SAK_ATAK wrote: post #98

I 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…

Meanwhile, at an actual enterprise, we have lots of Slack channels where membership is controlled by an LDAP group... so this would be a non-issue.
Post reply on HN