181–190 of 200 posts
>Today, 65% of our product team’s code is created by our internal version of Claude Tag. Yeah, that explains a lot.
To lay my cards out, I think the negativity towards it isn't driven by anything objective, but by anti-AI / anti-big-tech sentiment.
How is this multiplayer? Claude-slackbot needs to inherit my permissions for accessing scoped context and data / tools. Sounds like I need to setup specific credentials for each instance of the agent. More importantly, claude-slackbot automatically remembering sounds like it'll be company wide AI slop? 75% of the stuff on slack should not be remembered for the future. And 90% of the stuff worth having in context is n…
Earlier quoted context omitted.
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…
Not really, and neither does the doc it links to. It explains the difference between a personal agent (that acts as you) and a multiplayer agent (that has its own identity). But they walk all this back by saying that for PRs in GitHub it uses the upstream Claude for GitHub app - that is one installation of a GH app, which means one identity, one list of repos it can access. In the audit logs it will be impossible to…
You’re welcome.
>Today, 65% of our product team’s code is created by our internal version of Claude Tag. Yeah, that explains a lot.
I keep seeing this sentiment. Claude Code cli works very well for me. To lay my cards out, I think the negativity towards it isn't driven by anything objective, but by anti-AI / anti-big-tech sentiment.
Wowza this will be a token guzzler. Assuming Claude is parsing every message posted on multiple slack channels, compacting knowledge etc. Looks like Anthropic is progressing further into platform territory and conquering Agentic use cases left right and centre. If you’re building an agent platform for workforce productivity today, your best best is model agnosticism and focus on token cost control.
That’s… a lot of credits. Clearly they expect to make it back fast.
>Today, 65% of our product team’s code is created by our internal version of Claude Tag. Yeah, that explains a lot.
They're playing a cat and mouse game hoping LLM intelligence will outpace the growing complexity and unmaintainability of their code base.
>Today, 65% of our product team’s code is created by our internal version of Claude Tag. Yeah, that explains a lot.
I keep seeing this sentiment. Claude Code cli works very well for me. To lay my cards out, I think the negativity towards it isn't driven by anything objective, but by anti-AI / anti-big-tech sentiment.
There are even blatant UX issues in the consumer Claude app that have gone unfixed for months and months and months. For example, if Claude asks you a question and it runs over 2 lines? It's truncated and you can't read it. This would never pass QA, if they employed any.
It's immensely frustrating to me that this company has the best models but yet their product strategy is so bad.
Earlier quoted context omitted.
How are Anthropic's production applications poor quality? Other than memory use (which unfortunately is the industry standard nowadays) Claude Code is pretty solid.
Their product features are a venn diagram, so depending on the tool you use, you may or may not have access to a "Claude" feature i.e. - design is only available in web - cowork is only available in desktop, sharing projects only works in chat, not cowork, which is arguably the more valuable place to have that feature (re: multiplayer like tag). SSO only works if you type your email, the "login with google" button be…