Hacker News Reader

Comment by rkuska | Hacker News Reader

For 4.7 it is no longer possible to disable adaptive thinking. Which is weird given the comment from Boris followed with silence (and closed github issue). So much for the transparency.

> Claude Opus 4.7 (claude-opus-4-7), adaptive thinking is the only supported thinking mode. Thinking is off unless you explicitly set thinking: {type: "adaptive"} in your request; manual thinking: {type: "enabled"} is rejected with a 400 error.

https://platform.claude.com/docs/en/build-with-claude/adapti...

For my claude code I went with following config:

* /effort xhigh (in the terminal cli) - To avoid lazying

* "env": {"CLAUDE_CODE_DISABLE_1M_CONTEXT": "1"} (settings.json) - It seems like opus is just worse with larger context

* "display": "summarized" (settings.json) - To bring back summaries.

* "showThinkingSummaries": true (settings.json) - Should show extended thinking summaries in interactive sessions

Freaking wizardry.

View on HN

It's early days for Opus 4.7, but I will say this: Today, I had a conversation go well into the 200K token range (I think I got up to 275K before ending the session), and the model seemed surprisingly capable, all things beings considered.

Particularly when compared to Opus 4.6, which seems to veer into the dumb zone heavily around the 200k mark.

It could have just been a one-off, but I was overall pleased with the result.

I’m super envious. I can’t seem to do anything without a half a million tokens. I had to create a slash command that I run at the start of every session so the darn thing actually reads its own memory- whatever default is just doesn’t seem to do it. It’ll do things like start to spin up scripts it’s already written and stored in the code base unless I start every conversation with instructions to go read persistence and memory files. I also seem to have to actively remind it to go update those things at various parts of the conversation even though it has instructions to self update. All these things add up to a ton of work every session.

I think i’m doing it wrong

This does kind of smell like the wrong way to use it. Not trying to self-promote here, but the experiences you shared really made me think I headed the right direction with my prompting framework ("projex" - I once made a post about it).

I straight up skip all the memory thing provided by harnesses or plugins. Most of my thread is just plan, execute, close - Each naturally produce a file - either a plan to execute, a execution log, a post-work walkthrough, and is also useful as memory and future reference.

Something sounds very wrong with your setup or how you use it.

Is your CLAUDE.md barren?

Try moving memory files into the project:

    (In your project's .claude/settings.local.json)

    { ...
      "plansDirectory": "./plans/wip",
      "autoMemoryDirectory": "/Users/foo/project/.claude/memory"
    }

(Memory path has to be absolute)

I did this because memory (and plans) should show up in git status so that they are more visible, but then I noticed the agent started reading/setting them more.

If i had to guess i think you have probably overstuffed the context in hopes of moulding it and gotten worse outcomes because of that. I keep the default context _extremely_ small (as small as possible) and rely on invoked slash commands for a lot of what might have been in a CLAUDE.md before

Something seems wrong. A half-million tokens is almost five times larger than I allow even long-running conversations to get too. I've manually disabled the 1M context, so my limit is 200K, and I don't like it to get above 50%.

Is it... not aware of its current directory? Is its current directory not the root of your repo? Have you maybe disabled all tool use? I don't even know how I could get it to do what you're describing.

Maybe spend more time in /plan mode, so it uses tools and the Explore sub-agent to see what the current state of things is?

Two quick thoughts:

- Use the Plan mode, create a thorough plan, then hand it off to the next agent for execution.

- Start encapsulating these common actions into Skills (they can live globally, or in the project, per skill, as needed). Skills are basically like scripts for LLMs - package repeatable behavior into single commands.

Your display and thinking summery settings aren’t working for me (v2.1.112 on macOS). Any advice?

It seems like the correct way is to use:

`claude --thinking-display summarized`

The thinking is then visible with ctrl+o in the claude cli (shortcut available at least on mac).

Well you can't really trust the documentation I guess. I can't edit my original comment anymore.

Reply on news.ycombinator.com