Hacker News

I just rub it in Docker to limit folder access and prevent it from being able to push to my remote repo. Indestructible.

Personally yes I do run it in yolo mode. And I think, to the extent anyone will use this project, people mostly won't be using the fine grained control. For me toolsets and full yolo are what is useful in this project.

I think the real use cases are something like:

1. Try cautious mode, gain confidence, switch to yolo 2. Use yolo mode and find that it keeps doing something that annoys or scares you so you configure an exception for it

On number 2 I thought I would use it this way to prevent some unwanted behavior but I ended up learning how to avoid those behaviors in other ways.

I remember seeing on twitter how Claude 4 Sonnet tried to run rm -r ~ for some reason within cursor. It could have been a meme potentially, but from my experience this doesn’t seem to be to far off as it does weird things for weird reasons sometimes

"Scary" doesn't need to mean Skynet taking over, it could just mean that Claude decides to yolo install a library with malware in it.

Side question... how much is it costing you to run Claude Code on a regular basis?

If you add mcp tooling you can quickly go off local.

I’m less worried about hostile behaviors than stupid ones.

Honest question: What could it do to your machine if it went crazy? I've not used Claude Code yet.

I was thinking that on this, folks need a cron task to run a trivial prompt at 5-6am and get that 5hr timer running so that it the majority of the quota is available in the working day morning, and then a new 5hr block starts around lunch time. This should maximise use of included tokens by a standard work day spanning 3 blocks rather than 2

Thinking of switching from API access to Max 20x tomorrow for a more consistent bill.

Been using $50-100 of Opus tokens through API access per day. Think I’ll hit the Max 20x limits and get put in timeout?

I wish Max could automatically overflow to API access when it times out so I would need to have token anxiety.

Can you help me understand how that works?

I thought you needed an API key to work with Claude Code

As a heavy Claude user, I’ve seen many examples of what it will produce as a README, and they all look exactly like this.

It definitely could use some editing!

<3

> auto-accept

That's pretty much it and the concept of "toolsets"

> You would also expect some eat-your-own-dog-food

Maybe, but personally I don't see a reason to use an LLM to release an npm module

That's something I'd like to explore more. It's one of the reason I created "trusted roots". So I can open new worktrees and open claude in them all in one step without any confirmation.

If you want to suggest anything specific feel free to open an issue and we explore it more.

>Why? Claude Code already gives you the option to accept requests permanently going forward. The cost of configuring rules is worse than the cost of just telling Claude Code "yes and you don't need to ask again".

want to see this mode fail catastrophically? write enough CLI stuff w/ python w/ powershell or wsl or some other 'leaky' cli. It will eventually fail a command and then try to pipe a shell command through the python interpreter or a specific PS incantation.

This means that you now need to approve 'git' , and 'python sh git' and 'powershell.exe git' and 'wsl.exe ubuntu git' as separate and independent commands. (I dont remember the shell incantation command so excuse the pseudocode).

That means that for the entire gambit of approvals needed for continued permission for a singular task might be 4x greater than normal -- probably more given that claude is aware of so many different ways to pipe to shell..

> Why?

I have a lot of different projects, scenarios, and edge cases where it's helpful to me.

I think you will find that if you're interactive mode there will always be some dialogs to dismiss, especially if you're jumping around a lot of different projects, etc. So for me the goals are somewhere at the intersection of the interactive mode and unattended operation.

It depends what your goals are for sure. TBH I use it mostly in full yolo mode. But toolsets are much more useful for me. I can create groups of mcps and pre-allowed permissions and reuse that "preset". I have different types of projects that I use different toolsets for each.

But yeah, I hear you. This is pretty niche and might solve problems that only I care about.

Also, good call, I wiggled the readme around a bit. Thanks!

It's going to be hilarious to watch Anthropic argue with a straight face that it's illegal (or at least tortious) to take someone else's IP and repurpose it

We'll see. Happy to change it up if need be. I'd rather beg for forgiveness than permission. <3

That's a good idea. Personally I don't use CLAUDE.md (everything goes in the prompt, thanks to context-composer, which I'll share another day) so I'm not motivated to have it but I'd be happy to collaborate on it and get that kind of feature merged in.

No, the "automatic dismissal" effectively scrapes the terminal and parses out info from the dialog.

All of it, in close collaboration :)

just a guy with linux

Yes, the name should be changed ASAP. You don't want to rename it after it becomes established, which you'll inevitably have to do.

I am guessing part of it is the size of the code base it has to read to do any changes or understand the required changes?