Live data from Hacker News

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

claude.com

231–240 of 565 posts

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

#231
post #192

Earlier quoted context omitted.

What kinds of things are you building? This is not my experience at all. Just today I asked Claude using opus 4.6 to build out a test harness for a new dynamic database diff tool. Everything seemed to be fine but it built a test suite for an existing diff tool. It set everything up in the new directory, but it was actually testing code and logic from a preexisting directory despite the plan being correct before I tol…

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 mean I’ve been using AI close to 4 years now and I’ve been using agents off and on for over a year now. What you’re describing is exactly what I’m doing.

I’m not seeing anyone at work either out of hundreds of devs who is regularly cranking out several thousand lines of pretty good working code in 30-45 minutes.

What’s an example of something you built today like this?

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

#232

The weirdest thing about Claude pricing is their 5X pricing plan is 5 times the cost of the previous plan. Normally buying the bigger plan gives some sort of discount. At Claude, it's just "5 times more usage 5 times more cost, there you go".

5 times the already subsidised rate is still a discount.

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

#233
If this is a skill issue, feel free to let me know. In general Claude Code is decent for tooling. Onduty fullstack tooling features that used to sit ignored in the on-caller ticket queue for months can now be easily built in 20 minutes with unit tests and integration tests. The code quality isn't always the best (although what's good code for humans may not be good code for agents) but that's another specific and directed prompt away to refactor.

However, I can't seem to get Opus 4.6 to wire up proper infrastructure. This is especially so if OSS forks are used. It trips up on arguments from the fork source, invents args that don't exist in either, and has a habit of tearing down entire clusters just to fix a Helm chart for "testing purposes". I've tried modifying the CLAUDE.md and SPEC.md with specific instructions on how to do things but it just goes off on a tangent and starts to negotiate on the specs. "I know you asked for help with figuring out the CNI configurations across 2 clusters but it's too complex. Can we just do single cluster?" The entire repository gets littered with random MD files everywhere for directory specific memories, context, action plans, deprecated action plans, pre-compaction memories etc. I don't quite know which to prune either. It has taken most of the fun out of software engineering and I'm now just an Obsidian janitor for what I can best describe as a "clueless junior engineer that never learns". When the auto compaction kicks in it's like an episode of 50 first dates.

Right now this is where I assume is the limitation because the literature for real-world infrastructure requiring large contexts and integration is very limited. If anyone has any idea if Claude Opus is suitable for such tasks, do give some suggestions.

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

#234
post #148

Earlier quoted context omitted.

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…

One tip I have is that once you have the diff you want to fix, start a new session and have it work on the diff fresh. They’ve improved this, but it’s still the case that the farther you get into context window, the dumber and less focused the model gets. I learned this from the Claude Code team themselves, who have long advised starting over rather than trying to steer a conversation that has started down a wrong pa…

IMO it seems to start "forgetting" or "overlooking" claude.md well before the context window is full.

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

#235

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")?

In Claude code I believe it's /context and it'll give you a graphical representation of what's taking context space

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

#236

It’s interesting because my career went from doing higher level language (Python) to lower language (C++ and C). Opus and the like is amazing at Python, honestly sometimes better than me but it does do some really stupid architectural decisions occasionally. But when it comes to embedded stuff, it’s still like a junior engineer. Unsure if that will ever change but I wonder if it’s just the quality and availability of…

I've found it's ok at Rust. I think a lot of existing Rust code is high quality and also the stricter Rust compiler enforces that the output of the LLM is somewhat reasonable.

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

#237
post #153

Friends, just write the code. It’s not that hard.

I hear what you're saying, but for a lot of people coding isn't something we can throw 40+ hours per week at. My main job is running a small eComm business, and I have to both develop software automations for the office (to improve productivity long-term) while also doing non-coding day to day tasks. On top of this, I maintain an open source project after hours. I've also got a young family with 3 kids. I'm not sayin…

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 will embrance it and truly enjoy working with it

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

#240
post #223
post #92

Earlier quoted context omitted.

Source? I ask because I use 500k+ context on these on a daily basis. Big refactorings guided by automated tests eat context window for breakfast.

How many big refactorings are you doing? And why?

How is that relevant? we are talking about models, now what you do with them.
Post reply on HN