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

31–40 of 200 posts

Re: Claude Tag

#31

Post by mordymoop »

manbash wrote: post #25
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.)

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.

Re: Claude Tag

#32

Post by verdverm »

whalesalad wrote: post #17
jere wrote: post #13

It feels like they release 1 or 2 "products" a week and then we never hear about them again.

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.

Re: Claude Tag

#33

Post by mhegazy2 »

ceroxylon wrote: post #29
SweetSoftPillow wrote: post #11

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

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

Re: Claude Tag

#34

Post by CSMastermind »

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

Lots of people use design

Re: Claude Tag

#35

Post by CGamesPlay »

jere wrote: post #13

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)

Re: Claude Tag

#36

Post by halfmatthalfcat »

CSMastermind wrote: post #34
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.)

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.

Re: Claude Tag

#37

Post by kentm »

SweetSoftPillow wrote: post #11

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

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.

Re: Claude Tag

#38

Post by nate »

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?

Re: Claude Tag

#39

Post by MaxLeiter »

kentm wrote: post #37
SweetSoftPillow wrote: post #11

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

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
Post reply on HN