71–76 of 76 posts
This is all documented [1]. Once is documented [2], async and asyncRewake are documented [3] too. Skills frontmatter is fully documented [4]. Automode environment strings are documented [5]. This article is pure AI-written clickbait and I'm surprised to see such an uptake here. [1] https://code.claude.com/docs/en/hooks#pretooluse-decision-co... [2] https://code.claude.com/docs/en/hooks#common-fields [3] https://code.…
Claude Code’s feature cardinality is breathtaking. At this rate, the next pope will be from Anthropic
Jokes aside I find it hard to trust in the amount of things Anthropic throws out. It can’t be a well thought out and stable product this way.
I've never seen any company iterate on a product as quickly as Anthropic has with Claude. When you drill down into the details, it is well thought out and stable and well documented.
It seems the feedback loop is so fast, they address issues before they can fester into major problems. The entire company uses Claude; there's not better dogfooding than that.
It reminds me of how, back in the day, when continuous integration and continuous deployment were new; it seemed nuts to push code to production every day. And now, it's the norm.
can i ask claude to generate its own config? "you're me, create your perfect set of config files."
CLAUDE_CODE_NEW_INIT
Set to 1 to make /init run an interactive setup flow. The flow asks which files to generate, including CLAUDE.md, skills, and hooks, before exploring the codebase and writing them. Without this variable, /init generates a CLAUDE.md automatically without prompting.
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
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 then show me banner that I can clean up "xxx.x k" of context by typing clear right after it started on the plan.
Related from then: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode https://news.ycombinator.com/item?id=47586778
weak, even for you
Earlier quoted context omitted.
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