Hacker News Reader

Comment by brookst | Hacker News Reader

Same plan, same experience. Trying to get it to develop and execute tests and it frequently modifies the test to succeed even if the libraries it calls fail, and then explains that it’s doing so because the test itself works but the underlying app has errors.

Yes, I know. That’s what the test was for.

View on HN

Anthropic, if you're listening, please allow zoned access enforcement within files. I want to be able to say "this section of the file is for testing", delineated by comments, and forbid Claude from editing it without permission.

My fear when using Claude is that it will change a test and I won't notice.

Splitting tests into different files works but it's often not feasible, e.g. if I want to write unit tests for a symbol that is not exported.

Does already, read the docs

I think a link would have been far more helpful than "RTFM". Especially for those of us reading this exchange outside of the line of fire.

Don't put the onus (Opus!) on me! Just a dad approach to helping. If there's enough time to writ prose about the problem you could at least rtfm first!

If you know something is covered by the documentation it's useful to provide a link, especially if that documentation is difficult to find.

(I couldn't find that documentation when I went looking just now.)

Step 1: https://docs.anthropic.com

Step 2: Type 'Allowed Tools'

Step 3: Click: https://docs.anthropic.com/en/docs/claude-code/sdk/sdk-headl...

Step 4: Read

Step 5: Example --allowedTools "Read,Grep,WebSearch"

Step 6: Profit?

The original question was about this:

> allow zoned access enforcement within files. I want to be able to say "this section of the file is for testing", delineated by comments, and forbid Claude from editing it without permission.

So you've completely misunderstood what the discussion is about...

Maybe rtft ? Read the fucking thread.

I think you missed a critical step: 1.5: know that "allowed tools" is the correct incantation required to summon the relevant documentation; which, at least to me, is not obvious at all in the context of the OP.

I've had some middling success with this by utilizing CLAUDE.md and language features. Two approaches in C#: 1) use partial classes and create a 'rule' in CLAUDE.md to never touch named files, e.g. User.cs (edits allowed) User.Protected.cs (not allowed by convention) and 2) a no-AI-allowed attribute, e.g. [DontModifyThisClassOrAttributeOrMethodOrWhatever] and instructions to never modify said target. Can be much more granular and Claude Code seems to respect it.

Reply on news.ycombinator.com