given their recent speech, I’m sure theyre trying

sorry to post a shallow comment but this is a really excellent joke holy shit. well done.

in my experience, "undocumented tricks" break as often as documented features

like when they removed "clear context and execute plan" option after releasing 1M opus because "context window is not a problem anymore"

It is possible to build automation that efficiently handles low level customization of new versions as they appear.

This is true, but also "temporal hacks" can make or break "cutting edge" workflows. I don't re-architect my claude instructions every release. But some releases justify examining your existing instructions and making sure they still fit the current model. And it has made a noticeable difference.

The pattern across Claude Code, Codex and Cursor does seem to be converging: gather context, make a plan, execute, then verify.

What feels less standardized is how much control the user gets between those stages. Settings like showClearContextOnPlanAccept and disableAutoMode are interesting because they expose that boundary between “agent decides” and “human reviews before execution.”

That seems like the part where different coding agents will continue to feel very different in practice.

> Is anyone collecting and writing on how to understand this architectural style?

Are we on the same site? Is anyone writing about anything else?

Yeah I'd love to see a cookie cutter project with all of the best practices of the boilerplate files

Probably. It does seem to have a built-in tool for exploring its own docs, and it has a special mode for working in a .claude/ directory. It's probably intended that users do this.

There’s a slash command that’ll look through your conversation history to add allow permissions.

I just use /loop now which gives it a motivational prompt to keep the fuck going. Goal can be used too, but for some things a simple loop is better

Yeah, I just had Claude fill out the task list, and then before hitting the end of the task list ask whether I wanted to continue or whether getting some of it done was enough....

I decided to grep the actual binary to check. The current version is 2.1.156, but the post is based on 2.1.87.

Most of it holds up in 2.1.156: the hook response fields (updatedInput, permissionDecision, additionalContext, watchPaths, etc.), extra hook config fields (once, asyncRewake), skill/agent frontmatter (omitClaudeMd, criticalSystemReminder_EXPERIMENTAL, memory, color, context: fork), and autoMode/autoMemoryEnabled/autoDreamEnabled all show up as real Zod-schema config keys, not stray strings. autoMode has the allow/soft_deny/environment shape, plus an undocumented hard_deny.

Two things from the post I couldn't find in 2.1.156: yoloClassifier (the closest flag now is yoloEquivEnabled) and "Magic Docs" / the # MAGIC DOC: regex (the only MAGIC strings left are about file magic bytes).

If software engineering were truly solved, like Anthropic claims, anyone could just vibecode it back. If only they stopped being allergic to the word "open" and open-sourced Claude Code, which, at this point, there is no practical reason not to.

Maybe programmed with Claude Code?

I see the same with OpenAI's webpage on iOS.

weak, even for you

surely concats of user input, stdout of external dependencies, and non-deterministic output feeding back directly to an eval is safe. it's never been a problem before. not even trying to check the boxes when it comes to security anymore.

Can I do

  echo blah blah >> ~/.ssh/authorized_keys

still, far more effective than "NEVER FUCKING GUESS"

Article name: "everything the doc doesn't mention"

You: "they missed this feature that's in the docs !"

You're right that it's an important part of CC's config. But it doesn't fit the article's raison d'être.

Adaptive thinking isn't configurable if you're using 4.7 or higher though, so anybody on modern opus its basically useless.

https://code.claude.com/docs/en/model-config#adaptive-reason...

> Opus 4.7 and later always use adaptive reasoning. The fixed thinking budget mode and CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING do not apply to them.