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?
Claude Code – Everything you can configure that the docs don't tell you
61–70 of 76 posts
Re: Claude Code – Everything you can configure that the docs don't tell you
#62Earlier quoted context omitted.
sorry to post a shallow comment but this is a really excellent joke holy shit. well done.
I don't believe you deserve the downvotes you're getting. Sometimes a good joke is so good that it appears shallow at first glance, but only upon reflection does the true humor show through. A shallow callout such as yours is sometimes necessary to call the reader back to it for that further reflection.
- it’s against HN guidelines to comment on downvotes
- comments are supposed to be substantive, further the discussion, and inspire curiosity (and I think the joke failed at all of those)
- it’s not a great joke, just a shallow pun
I’m guilty of often downvoting jokes on HN that are just jokes with no substance, partly because they end up causing confusion and noise, and they make the discussion less interesting. Reddit is a great place for those.
Re: Claude Code – Everything you can configure that the docs don't tell you
#63Re: Claude Code – Everything you can configure that the docs don't tell you
#64Re: Claude Code – Everything you can configure that the docs don't tell you
#65Is 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…
Re: Claude Code – Everything you can configure that the docs don't tell you
#66can i ask claude to generate its own config? "you're me, create your perfect set of config files."
Re: Claude Code – Everything you can configure that the docs don't tell you
#67That example classifier is horrendous. A simple substring search for ls/cat/echo/etc?
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.
Re: Claude Code – Everything you can configure that the docs don't tell you
#68This 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.com/docs/en/hooks#command-hook-fields
[4] https://code.claude.com/docs/en/skills#frontmatter-reference
[5] https://code.claude.com/docs/en/auto-mode-config#define-trus...
Re: Claude Code – Everything you can configure that the docs don't tell you
#69It's a great guide that is necessary because the documentation of Claude code is so lacking. It's a shame really, trillions of dollars, but not one man hour to make an agent on the ci to write the doc and a pr. It frustrates me, it has been like that for months, it's like nobody cares or find this normal.
Re: Claude Code – Everything you can configure that the docs don't tell you
#70Claude Code’s feature cardinality is breathtaking. At this rate, the next pope will be from Anthropic