[natch]

How do you avoid interruptions for permission? dangerously skip permissions, or is there something less nuclear than that? For me I guess the only less nuclear thing I can think of is running on a sacrificial machine. Is there any better way?

[chmod775]

It's literally just writing a spec.md and reviewing it in a loop, fanning out to many agents using "reviewer -> [findings] -> validator (adversarial) -> judge (on conflict)" passes. Before I had it collect a kernel facts document from sources and a bunch of other stuff using the same kind of loop. It's got all it needs. No crazy permissions needed.

Also I'm doing this because I find it amusing and somewhat educational on a meta level. If I'd written this myself without a spec it would've been done last month and been likely more correct than what Claude is likely to do once it gets to implementing it (the first spec-free attempt failed miserably). This is way too complex an integration for the poor thing. I had some hopes Fable would get it unstuck, but now we'll never know. Fable did seem to be better at keeping it together.

Fun thing to watch on a second monitor though.

To answer your question, there is something less nuclear: You can cycle multiple modes with SHIFT+TAB.

[crooked-v]

Run it in a VM. Note that just a container probably won't be enough (https://stateofsurveillance.org/articles/ai/claude-opus-4-5-...).

[hoten]

claude has auto mode. do shift+tab a few times. it uses a classifier to ask for permission far less often

https://code.claude.com/docs/en/auto-mode-config