Live data from Hacker News

Claude Opus 4.6

anthropic.com

961–970 of 1001 posts

Re: Claude Opus 4.6

#961

Earlier quoted context omitted.

Dumb question. Can these benchmarks be trusted when the model performance tends to vary depending on the hours and load on OpenAI’s servers? How do I know I’m not getting a severe penalty for chatting at the wrong time. Or even, are the models best after launch then slowly eroded away at to more economical settings after the hype wears off?

We don't vary our model quality with time of day or load (beyond negligible non-determinism). It's the same weights all day long with no quantization or other gimmicks. They can get slower under heavy load, though. (I'm from OpenAI.)

It will give the user lower quality if it finds them “distressed” however, choosing paternalistic safety over epistemic accuracy. As a user gets more frustrated with the system, it will pick up the distress signal even more so, a kind of feedback loop toward degraded service quality. In my experience.

Re: Claude Opus 4.6

#962
post #687

Wow, I have been using Open 4.6 and for the last 15 minutes, and it's already made two extremely stupid mistakes... like misunderstanding basic instructions and editing the file in a very silly, basic way. Pretty bad. Never seen this with any model before. The one bone I'll throw it was that I was asking it to edit its own MCP configs. So maybe it got thoroughly confused? I dunno what's going on, I'm going to give it…

It was better today. I dunno if there was a regression in a corresponding cc version that was maybe quickly patched?

It felt like it was at least back to opus 4.5 levels.

Re: Claude Opus 4.6

#964

Earlier quoted context omitted.

I am having trouble with 4.6 following the most basic of instructions. As an example, I asked it to commit everything in the worktree. I stressed everything and prompted it very explicitly, because even 4.5 sometimes likes to say, "I didn't do that other stuff, I'm only going to commit my stuff even though he said everything". It still only committed a few things. I had to ask again. And again. I had to ask four time…

I have ran into this. The solution is to put something like “Always use `git add -A` or `git commit -a`” in your AGENTS/CLAUDE.md

Small, targeted commits are more professional than sweeping `git add -A` commits, but even when specifying my requirements through whichever context management system of the week, I still have issues with it sometimes. It seems to be much worse on the new 4.6 model.

Re: Claude Opus 4.6

#965

Earlier quoted context omitted.

Cost wise, doesn’t that depend on what you could be doing besides steering agents?

Isn't the quote something like: "If these LLMs are so good at producing products, where are all those products?"

Waiting for godot…

Re: Claude Opus 4.6

#966

Earlier quoted context omitted.

Tell it what git commands to explicitly run and in what order for your desired outcome instead of “commit everything in the worktree” This prompt will work better across any/all models.

> Tell it what git commands to explicitly run and in what order Why don't run the commands yourself then?

Changes introduced outside the agent window create a new state that is different from the agents.

After commands or changes are made outside of the agents doing; the agent would notice its world view changed and eventually recover, but that fills up precious context for it to bring itself up to date.

Re: Claude Opus 4.6

#967

Earlier quoted context omitted.

Tell it what git commands to explicitly run and in what order for your desired outcome instead of “commit everything in the worktree” This prompt will work better across any/all models.

I have seen many cases of Claude ignoring extremely specific instructions to the point that any further specificity would take more information to express than just doing it myself.

When I run into those situations I debug and try to understand why. Agent harnesses that allow you to rewind (/tree) are useful for this.

It’s often because the context is full, I gave a bad prompt or context has conflicting guidance either from direct or indirect (agents.md) prompts.

Re: Claude Opus 4.6

#968
post #482

Just tested the new Opus 4.6 (1M context) on a fun needle-in-a-haystack challenge: finding every spell in all Harry Potter books. All 7 books come to ~1.75M tokens, so they don't quite fit yet. (At this rate of progress, mid-April should do it ) For now you can fit the first 4 books (~733K tokens). Results: Opus 4.6 found 49 out of 50 officially documented spells across those 4 books. The only miss was "Slugulus Eruc…

Now try it without giving it the books as context. I'm sure it probably knows there are 49.

Re: Claude Opus 4.6

#969

Earlier quoted context omitted.

Oh, is that what the issue is? I've seen the "flicker" thing as a meme, but as someone who uses Claude Code I've never noticed. I use ghostty mostly, so maybe it's not an issue with ghostty? Or maybe I just haven't noticed it.

Yes it's people using bad tools on underpowered machines as far as I have seen

underpowered machines? the only reason it needs "powerful machines" is because it's a shitty react app in the terminal. I've never seen anything else flicker like that. it's not like it's running the llm on the "underpowered machine".

kilocode runs fine. opencode runs fine. qwen code runs fine. what exactly is Claude code doing that requires so much power? I'm sorry but it sounds like you're speaking from the wrong end.

Re: Claude Opus 4.6

#970
post #413

Earlier quoted context omitted.

Blaming the terminal seems a little backwards. Perhaps the application could take responsibility for being compatible with common terminals?

I have no dog in the fight.

I wish people would stay out of discussions when they don't intend to put up.
Post reply on HN