alt Hacker NewsDeterministic boundaries appear to be best solved with sandboxes/microVMs/remote infra and unique identities with probabilistic guardrails on top. The old deterministic allow/deny list running on bare metal didn't meaningfully solve the problem of giving Claude determinism. Humans got approval fatigue, and eventually, Claude got access to something like 'python3 FILE.py' and Claude could go to the races by updating 'FILE.py'.
The allow/deny list functionality was trash though. If I have a once-off workflow and I want to execute Claude within it, I can't even give it a whitelist of allowed tools.
I definitely prefer auto-mode to the granularity of prompts I was getting from Claude. But I also want to be able to use deterministic rules, and Claude Code's functionality for it sucks.