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

151–160 of 200 posts

Re: Claude Tag

#151

Post by wolttam »

NewsaHackO wrote: post #143
MeetingsBrowser wrote: post #109

Earlier quoted context omitted.

Claude code is by far the buggiest piece of software I interact with, If the underlying model weren’t so good, I would never opt to use it. It takes multiple seconds to launch, random lines disappear in the scroll back, it’s internal state gets messed up causing the TUI to show duplicate and/or offset lines, and it frequently causes some kind of GPU buffer corruption causing the entire terminal env to show garbage.

>It takes multiple seconds to launch, Yes, this is the ubiquitous memory issue that I mentioned. Unfortunately, it is now the baseline in all modern apps. >random lines disappear in the scroll back, it’s internal state gets messed up causing the TUI to show duplicate and/or offset lines, I haven't seen this issue, other than when I am using a shell that is bugged and does it with all TUI/console programs (usually a v…

Baseline for “modern” apps, what? We’re talking about a terminal application here, there is definitely, most-assuredly ways to write something that does exactly what Claude Code does with a teeny fraction of the resource requirements.

The trick is not bringing React into the terminal.

(FWIW, I have a link to a TUI harness in my profile that uses 50MB of ram and about 1% CPU while streaming, even in giant contexts)

Re: Claude Tag

#152

Post by pjrog »

atonse wrote: post #62
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…

We have the opposite problem. We've tried this slack integration (first with NanoClaw, then Hermes, but now just building our own), and we actually want the OPPOSITE. In private context, I want to have a per-person conversation with durable context for that person's private chats. I also want that person's permissions to extend. Like contractors in our slack should only be able to ask and get back information about c…

[flagged]

Re: Claude Tag

#153

Post by bitlad »

allan_s wrote: post #150
bitlad wrote: post #149

What if you could do this: @claude collect all the internal knowledge and context. And fire folks who are not required.

Fortunately hr system in most companies are from software vendors that are 2 gen behind so a mcp with a "fire $EMPLOYEE " tool will not come up Would also be funny if it fires the one who done the request.

You could use coworks for that. Use Tools please.

Re: Claude Tag

#154

Post by Lightbody »

on_meds wrote: post #142
Lightbody wrote: post #141

It's interesting to see the market movements from the big players. This announcement is all about Claude extending its reach beyond single-player workflows and into multi-player workflows. On the flip side, Slack just announced MCP support for the Slackbot AI chat capability embedded within Slack. It is, for now, exclusively single-player. Single-player is the "safe place" (relatively speaking). The context, permissi…

If your mixing work with personal calendars that’s a bigger problem. Work should be entirely separate calendars with things from personal added to it in generic blocks the owner can understand but protects from this leakage. Work calendars are owned by companies (generally) and should be treated like the are looked at by coworkers.

They are separate. That’s how Reclaim works :) Happy to share more here but not trying to pitch my product since it’s off topic.

My point is: context and privacy is HARD in multi-player modes.

Re: Claude Tag

#156

Post by tills13 »

MeetingsBrowser wrote: post #109
NewsaHackO wrote: post #104

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.

Claude code is by far the buggiest piece of software I interact with, If the underlying model weren’t so good, I would never opt to use it. It takes multiple seconds to launch, random lines disappear in the scroll back, it’s internal state gets messed up causing the TUI to show duplicate and/or offset lines, and it frequently causes some kind of GPU buffer corruption causing the entire terminal env to show garbage.

+1. Claude Code shows that _even while the model is incredible_, you still need proper engineering discipline to ship stable (and good) software.

Re: Claude Tag

#157

Post by LZ_Khan »

brandensilva wrote: post #147
holografix wrote: post #146

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 exactly what I'm doing. Push for model flexibility, cost control, and reliability. The moat is to be anti lock in. The open source model needs to be amped up on steroids to avoid this permiating every facet of your org you cannot escape.

Good luck. Anthropic gets to co-train their harness with their model. Can't see people competing with that unless they own the model.

Re: Claude Tag

#158

Post by theshrike79 »

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

If a coworker "hijacks" your session, you go "Yo, dude, fuck off" or walk over to their desk and slap them on the back of the head.

Anyway, if that happens, you've got organisational issues. Claude can't fix that.

Re: Claude Tag

#159

Post by theshrike79 »

nijave wrote: post #110
NewsaHackO wrote: post #104

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 "safety" system that arbitrarily flags things. Tons of examples of innocuous strings setting it off and sometimes with financial impact like the OpenClaw/hermes thing (just having the word "hermes" would insta deplete your quota and start charging you API rates in extra usage)

The hermes trigger was a bug and they fixed it in a few hours. But bad news carries far and wide.

Re: Claude Tag

#160

Post by theshrike79 »

Topology1 wrote: post #100

No way they announced a new product before commenting on access to Fable/Mythos.

Mythos was banned because the MAGA admin doesn't like Anthropic. That's it.

They can't really comment the truth about it publicly or the rest of the company gets banned too.

Post reply on HN