Live data from Hacker News

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

buildingbetter.tech

51–60 of 76 posts

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

#51

Is there an AI Coding Agent application structure emerging that is more or less universal across llm models? Is anyone collecting and writing on how to understand this architectural style?

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

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

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

#53
post #52

can i ask claude to generate its own config? "you're me, create your perfect set of config 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.

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

#54
Wow, not one mention of the env vars that have a far greater influence on how the models actually work under the hood - https://code.claude.com/docs/en/env-vars

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

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

#56
post #54

Wow, not one mention of the env vars that have a far greater influence on how the models actually work under the hood - https://code.claude.com/docs/en/env-vars 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

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.

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

#57
post #54

Wow, not one mention of the env vars that have a far greater influence on how the models actually work under the hood - https://code.claude.com/docs/en/env-vars 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

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.

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

#60

Is there an AI Coding Agent application structure emerging that is more or less universal across llm models? Is anyone collecting and writing on how to understand this architectural style?

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 d…

[dead]
Post reply on HN