echo blah blah >> ~/.ssh/authorized_keys
And that'd be auto approved?The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
like when they removed "clear context and execute plan" option after releasing 1M opus because "context window is not a problem anymore"
also find `"disableAutoMode": "disable"` useful, since I'm typically switching between yolo and plan
(It's not easy to find though, and lots of other docs doesn't mention it or link to this)
you can however convince claude to create a local command with the extracted prompts for stuff like autodream
> Not at 100% - and I want to be straight about why that's a longer road...
https://github.com/user-attachments/assets/961eff6c-0060-45d...
I just want Claude Code to stop giving up on achieving tasks. It's so annoying. Even with `/goal` or the new `ultracode` it gives up constantly.
My project is very complex (https://github.com/mohsen1/tsz) but Codex has no problem keep grinding without stopping like that
So it's already possible for someone to "vibecode it back". It's just perhaps not legal.
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.
Are we on the same site? Is anyone writing about anything else?
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).
@dang I know you have so far resisted a rule for AI-generated content (as we now have for comments), but I personally would prefer a flag for articles so that I don't waste my time on slop.
Very important for bedrock deployments and other not-as-standard deployments
Key for how I've deployed it - disable adaptive thinking, max thinking tokens, disable telemetry, etc
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.
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.
47282847•8h ago
steve1977•7h ago
FinnKuhn•4h ago
steve1977•4h ago
sscaryterry•2h ago