Live data from Hacker News

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

claude.com

311–320 of 565 posts

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

#311

Earlier quoted context omitted.

I'm directly conveying my actual experience to you. I have tasks that fill up Opus context very quickly (at the 200k context) and which took MUCH longer to fill up Codex since 5.2 (which I think had 400k context at the time). This is direct comparison. I spent months subscribed to both of their $200/mo plans. I would try both and Opus always filled up fast while Codex continued working great. It's also direct experie…

This has been my experience too.

Have any of you heard of map reduce

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

#312

Opus 4.6 is nuts. Everything I throw at it works. Frontend, backend, algorithms—it does not matter. I start with a PRD, ask for a step-by-step plan, and just execute on each step at a time. Sometimes ideas are dumb, but checking and guiding step by step helps it ship working things in hours. It was also the first AI I felt, "Damn, this thing is smarter than me." The other crazy thing is that with today's tech, these…

[flagged]

LLM written comments are not allowed on HN. This comment is written by an LLM and the account is fresh.

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

#314

Opus 4.6 is nuts. Everything I throw at it works. Frontend, backend, algorithms—it does not matter. I start with a PRD, ask for a step-by-step plan, and just execute on each step at a time. Sometimes ideas are dumb, but checking and guiding step by step helps it ship working things in hours. It was also the first AI I felt, "Damn, this thing is smarter than me." The other crazy thing is that with today's tech, these…

I wish I had this kind of experience. I threw a tedious but straightforward task at Claude Code using Opus 4.6 late last week: find the places in a React code base where we were using useState and useEffect to calculate a value that was purely dependent on the inputs to useEffect, and replace them with useMemo. I told it to be careful to only replace cases where the change did not introduce any behavior changes, and…

Start over, create a new plan with the lessons learned.

You need to converge on the requirements.

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

#315
post #244

Earlier quoted context omitted.

100% agree with this, as much as I hate the term "game-changer"... it truly is, I'm working on projects that I've always wanted to do but never had the capacity (or money to pay a small team of devs to build something)-- all these things that you thought you'd never have a chance to do, are suddenly now real and completely possible. I know there's a lot of AI haters out there but I'm pretty sure in time, all devs wil…

If anyone thought there was value to those projects they would have paid for it before.

Yeah, and likely still pay for it now (hopefully!)

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

#316

Earlier quoted context omitted.

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

I'm directly conveying my actual experience to you. I have tasks that fill up Opus context very quickly (at the 200k context) and which took MUCH longer to fill up Codex since 5.2 (which I think had 400k context at the time). This is direct comparison. I spent months subscribed to both of their $200/mo plans. I would try both and Opus always filled up fast while Codex continued working great. It's also direct experie…

I agree even though I used to be a die hard Claude fan I recently switched back to ChatGPT and codex to try it out again and they’ve clearly pulled into the lead for consistency, context length and management as well as speed. Claude Code instilled a dread in me about keeping an eye on context but I’m slowly learning to let that go with codex.

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

#317

Earlier quoted context omitted.

I've been building a new task manager in C for Linux. If you're not using AI you are cooked. You just don't realize it yet. https://i.imgur.com/YXLZvy3.png

> If you're not using AI you are cooked. You just don't realize it yet. Truth. But not just “using”. Because here’s where this ship has already landed: humans will not write code, humans will not review code. I see mostly rage against this idea, but it is already here. Resistance is futile. There will be no “hand crafted software” shops. You have at most 3-4 years left if you think this is your job.

I don't really agree.

People should still understand the code because sometimes the AI solution really is wrong and I have to shove my hand in it's guts and force it to use my solution or even explain the reasoning.

People should be studying architecture. Cause now I can orchestrate stuff that used to take teams and I would throwaway as a non-viable idea. Now I can just do it. But no you will still be reviewing code.

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

#319

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

Thanks for the video. His fix for "the dumb zone" is the RPI Framework: ● RESEARCH. Don't code yet. Let the agent scan the files first. Docs lie. Code doesn't. ● PLAN. The agent writes a detailed step-by-step plan. You review and approve the plan, not just the output. Dex calls this avoiding "outsourcing your thinking." The plan is where intent gets compressed before execution starts. ● IMPLEMENT. Execute in a fresh…

How is that Plan strategy not "outsourcing your thinking" because that's exactly what it sounds like. AI does the heavy lifting and you are the editor.

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

#320

Earlier quoted context omitted.

> RESEARCH. Don't code yet. Let the agent scan the files first. Docs lie. Code doesn't. I find myself often running validity checks between docs and code and addressing gaps as they appear to ensure the docs don’t actually lie.

I have Codex and Gemini critique the plan and generate their plans. Then I have Claude review the other plans and add their good ideas. It frequently improves the plan. I then do my careful review.

This is exactly how I've found leads to most consistent high quality results as well. I don't use gemini yet (except for deep research, where it pulls WAY ahead of either of the other 'grounding' methods)

But Codex to plan big features and Claude to review the feature plan (often finds overlooked discrepancies) then review the milestones and plan implementation of them in planning mode, then clear context and code. Works great.

Post reply on HN