1M context is now generally available for Opus 4.6 and Sonnet 4.6
421–430 of 565 posts
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#422Interesting, I’ve never needed 1M, or even 250k+ context. I’m usually under 100k per request. About 80% of my code is AI-generated, with a controlled workflow using dev-chat.md and spec.md. I use Flash for code maps and auto-context, and GPT-4.5 or Opus for coding, all via API with a custom tool. Gemini Pro and Flash have had 1M context for a long time, but even though I use Flash 3 a lot, and it’s awesome, I’ve neve…
i said well yeah, but its too sophiscated to be practical
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#423Earlier quoted context omitted.
Yes, it's nice to have a strict compiler, so the agent has to keep fixing its bugs until it actually compiles. Rust and TypeScript are great for this.
A big downside with rust is the compile times. Being in a tight AI loop just wasn't part of the design of any existing programming languages. As languages designed for (and probably written by) AI come out over the next decade, it will be really interesting to see what dragon tradeoffs they make.
I would argue that because Rust is so strict having the agent compile and run tests on every iterations is actually less needed then in other languages.
I program mostly in python but I keep my projects strictly typed with basedpyright and it greatly reduced the amount of errors the agent makes because it can get immediate feedback it has done something stupid.
Of course you still need to review the code because it doesn't solve logic bugs.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#424Earlier quoted context omitted.
Context decay is noticeable within 3 messages, nearly every time. Maybe not substantial, but definitely noticeable. It’s lead to me starting new chats with bigger and bigger starting ‘summary, prompts to catch the model up while refreshing it. Surely there’s a way to automate that technique.
[dead]
I generate task.md files before working on anything, some are short, others are super long and with many steps. The models don't deviate anymore. One trick is to make a post tool use hook to show the first open gate "- [ ]" line from task.md on each tool call. This keeps the agent straight for 100s of gates.
After each gate is executed we don't just check it, we also append a few words of feedback. This makes the task.md become a workbook, covering intent, plan, execution and even judgements. I see it like a programming language now. I can gate any task and the agent will do it, however many steps. It can even generate new gates, or replan itself midway.
You can enforce strict testing policies by just leaning into gate programability power - after each work gate have a test gate, and have judges review testing quality and propose more tests.
The task.md file is like a script or pipeline. It is also like a first class function, it can even ingest other task.md files for regular reflexion. A gate can create or modify gates, or tasks. A task can create or modify gates or tasks.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#425Earlier quoted context omitted.
> 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
#426Earlier quoted context omitted.
If it's not coding, even with 200k context it starts to write gibberish, even with the correct information in the context. I tried to ask questions about path of exile 2. And even with web research on it gave completely wrong information... Not only outdated. Wrong I think context decay is a bigger problem then we feel like.
It could also be a skill problem. It would be more helpful if when people made llm sucks claims they shared their prompt. The people I work with who complain about this type of thing horribly communicate their ask to the llm and expect it to read their minds.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#427Earlier quoted context omitted.
> 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.
Are you using AI to write this? Please stop.
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#428Earlier 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…
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#429Earlier quoted context omitted.
You probably just don't have the hang of it yet. It's very good but it's not a mind reader and if you have something specific you want, it's best to just articulate that exactly as best you can ("I want a test harness for , which you can find "). You need to explain that you want tests that assert on observable outcomes and state, not internal structure, use real objects not mocks, property based testing for invarian…
I absolutely have the hang of Claude and I still find that it can make those ridiculous mistakes, like replicating logic into a test rather than testing a function directly, talking to a local pg that was stale/ running, etc. I have a ton of skills and pre-written prompts for testing practices but, over longer contexts, it will forget and do these things, or get confused, etc. You can minimize these problems with TLC…
Re: 1M context is now generally available for Opus 4.6 and Sonnet 4.6
#430The 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.
If it's not coding, even with 200k context it starts to write gibberish, even with the correct information in the context. I tried to ask questions about path of exile 2. And even with web research on it gave completely wrong information... Not only outdated. Wrong I think context decay is a bigger problem then we feel like.