Live data from Hacker News

1M context is now generally available for Opus 4.6 and Sonnet 4.6

claude.com

101–110 of 565 posts

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#101
post #51

Earlier quoted context omitted.

A person has a supervision budget. They can supervise one agent in a hands-on way or many mostly-hands-off agents. Even though theres some thrashing assistants still get farther as a team than a single micromanaged agent. At least that’s my experience.

Just curious, what kind of work are you doing where agentic workflows are consistently able to make notable progress semi-autonomously in parallel? Hearing people are doing this, supposedly productively/successfully, kind of blows my mind given my near-daily in-depth LLM usage on complex codebases spanning the full stack from backend to frontend. It's rare for me to have a conversation where the LLM (usually Opus 4.6…

I've passed that bottleneck with a review task that produces engineering recommendations along six axis (encapsulation, decoupling, simplification, dedoupling, security, reduce documentation drift) and a ideation tasks that gives per component a new feature idea, an idea to improve an existing feature, an idea to expand a feature to be more useful. These two generate constant bulk work that I move into new chat where it's grouped by changeset and sent to sub agent for protecting the context window.

What I'm doing mostly these days is maintaining a goal.md (project direction) and spec.md (coding and process standards, global across projects). And new macro tasks development, I've one under work that is meant to automatically build png mockup and self review.

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#102

Earlier quoted context omitted.

Is it ever useful to have a context window that full? I try to keep usage under 40%, or about 80k tokens, to avoid what Dex Horthy calls the dumb zone in his research-plan-implement approach. Works well for me so far. No vibes allowed: https://youtu.be/rmvDxxNubIg?is=adMmmKdVxraYO2yQ

Since I'm yet to seriously dive into vibe coding or AI-assisted coding, does the IDE experience offer tracking a tally of the context size? (So you know when you're getting close or entering the "dumb zone")?

Cline gives you such a thing. you dont really know where the dumb zone by numbers though, only by feel.

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#103

Earlier quoted context omitted.

Also, when you hit compaction at 200k tokens, that was probably when things were just getting good. The plan was in its final stage. The context had the hard-fought nuances discovered in the final moment. Or the agent just discovered some tiny important details after a crazy 100k token deep dive or flailing death cycle. Now you have to compact and you don’t know what will survive. And the built-in UI doesn’t give you…

I've found compactation kills the whole thing. Important debug steps completely missing and the AI loops back round thinking it's found a solution when we've already done that step.

[dead]

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#104
post #7

This is super exciting. I've been poking at it today, and it definitely changes my workflow -- I feel like a full three or four hour parallel coding session with subagents is now generally fitting into a single master session. The stats claim Opus at 1M is about like 5.4 at 256k -- these needle long context tests don't always go with quality reasoning ability sadly -- but this is still a significant improvement, and…

Random: are you personally paying for Claude Code or is it paid by you employer? My employer only pays for GitHub copilot extension

GitHub Copilot CLI lets you use all these models (unless your employer disables them.

https://github.com/features/copilot/cli

Disclosure: work at Msft

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#105

Earlier quoted context omitted.

I’ve been using 1M for a while and it defers it and makes it worse almost when it happens. Compacting a context that big loses a ton of fidelity. But I’ve taken to just editing the context instead (double esc). I also am planning to build an agent to slice the session logs up into contextually useful and useless discarding the useless and keeping things high fidelity that way. (I.e., carve up with a script the jsonl…

til you can edit context. i keep a running log and /clear /reload log

double escape gets you to a rewind. not sure about much else.

the conversation history is a linked list, so you can screw with it, with some care.

I spend this afternoon building an MCP do break the conversation up into topics, then suggest some that aren't useful but are taking up a bunch of context to remove (eg iterations through build/edit just needs the end result)

its gonna take a while before I'm confident its worth sharing

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#106

Earlier quoted context omitted.

Just curious, what kind of work are you doing where agentic workflows are consistently able to make notable progress semi-autonomously in parallel? Hearing people are doing this, supposedly productively/successfully, kind of blows my mind given my near-daily in-depth LLM usage on complex codebases spanning the full stack from backend to frontend. It's rare for me to have a conversation where the LLM (usually Opus 4.6…

I've passed that bottleneck with a review task that produces engineering recommendations along six axis (encapsulation, decoupling, simplification, dedoupling, security, reduce documentation drift) and a ideation tasks that gives per component a new feature idea, an idea to improve an existing feature, an idea to expand a feature to be more useful. These two generate constant bulk work that I move into new chat where…

What are you using to orchestrate/apply changes? Claude CLI?

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#107

Earlier quoted context omitted.

I'd been on Codex for a while and with Codex 5.2 I: 1) No longer found the dumb zone 2) No longer feared compaction Switching to Opus for stupid political reasons, I still have not had the dumb zone - but I'm back to disliking compaction events and so the smaller context window it has, has really hurt. I hope they copy OpenAI's compaction magic soon, but I am also very excited to try the longer context window.

Hmm I’ve felt the dumb zone on codex

From what I've seen, it means whatever he's doing is very statistically significant.

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#109

Earlier quoted context omitted.

I'd been on Codex for a while and with Codex 5.2 I: 1) No longer found the dumb zone 2) No longer feared compaction Switching to Opus for stupid political reasons, I still have not had the dumb zone - but I'm back to disliking compaction events and so the smaller context window it has, has really hurt. I hope they copy OpenAI's compaction magic soon, but I am also very excited to try the longer context window.

1m context in OpenAI and Gemini is just marketing. Opus is the only model to provide real usable bug context.

Codex high reasoning has been a legitimately excellent tool for generating feedback on every plan Claude opus thinking has created for me.

Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6

#110

The big change here is: > Standard pricing now applies across the full 1M window for both models, with no long-context premium. Media limits expand to 600 images or PDF pages. For Claude Code users this is huge - assuming coherence remains strong past 200k tok.

Is it ever useful to have a context window that full? I try to keep usage under 40%, or about 80k tokens, to avoid what Dex Horthy calls the dumb zone in his research-plan-implement approach. Works well for me so far. No vibes allowed: https://youtu.be/rmvDxxNubIg?is=adMmmKdVxraYO2yQ

Yes. I’ve used it for data analysis
Post reply on HN