Live data from Hacker News

Claude Code – Everything you can configure that the docs don't tell you

buildingbetter.tech

11–20 of 76 posts

Re: Claude Code – Everything you can configure that the docs don't tell you

#11
post #8
post #7

Earlier quoted context omitted.

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"

I so miss that clear context and execute plan mode! Now i have to keep clearing it manually again.

fyi you can re-enable it with `{ "showClearContextOnPlanAccept": true }` in ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/settings.json

also find `"disableAutoMode": "disable"` useful, since I'm typically switching between yolo and plan

Re: Claude Code – Everything you can configure that the docs don't tell you

#15

claude package has ten new versions published per week, and one new model every few months, one should definitely not rely on some undocumented tricks around it: it'll change, it'll break deep ultra-specific configurations

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

Re: Claude Code – Everything you can configure that the docs don't tell you

#18
most of these are in fact documented, the rest either no longer exists, is still gated by feature flags (i checked), or has little use to most users.

you can however convince claude to create a local command with the extracted prompts for stuff like autodream

Re: Claude Code – Everything you can configure that the docs don't tell you

#20
post #2

What’s up with scrolling on that page?! I was locked into a page region several times until I finally gave up. Safari/Orion iOS current

Maybe programmed with Claude Code?

Substack is such a big platform that they should have resources to make sure their product works fine on common device/browser combinations.
Post reply on HN