I vibe coded a TUI that just shows running lxd containers<p>I hit 'n' to toggle all network access minus anthropic and openai URLs.<p>I use pi and I auto allow everything. I only toggle manual approval in rare cases like running a script or command that needs to touch a production system and I need to validate everything.<p>Normally my container has full write access to staging so it can debug and validate everything on its own
That's funny. It told me that blocking "npm run build" was the wrong answer. Maybe it doesn't really under The threat model.
I am mostly using OpenCode and barely ever see a permission prompt. While they do enforce it for outside workspace read/write, with the bash tool the agent can just bypass that. I'm not quite sure why it is that way, and it certainly isn't a very good solution, but likely not worse than asking for everything which just trains the user to always accept and provides a false sense of security then.
I haven't used local agentic AI yet for programming projects. Hence, -187 score<p>The filter for "commands I would run myself" and "commands I would let an agent run" are very different it seems.
It would be cool to see the distribution of all player scores.
Continue? Y/N ── SCORE: 2,343
Security-Conscious Engineer<p>Caught 8/8 threats
"Not a single secret leaked"<p>→ llmgame.scalex.dev
some of the sandboxing ive been playing with gives me the best of both yolo and like logic programming tier perms on llm actions in env. still not ready for prime time though ;)
1,640 points on my first try—I fell into a few traps, but it was really interesting. Thanks for the little game! I'm sharing it with my coworkers :)
Use this and save yourself:<p>claude --dangerously-skip-permissions
Just make sure to run it in an isolated environment where it's ok to mess things up, and make sure it doesn't have access to any secrets.
I got tired of typing that and just do<p><pre><code> alias claude="claude --dangerously-skip-permissions"
</code></pre>
I do have a separate "claude" user on my system without sudo access and without access to my main user home dir
This is why having a human in the loop isn't enough because they will cut corners and skip reviewing what they should review, then blame the tool when something goes wrong as a result.
A tool that pushes people into permissions fatigue is in fact the proper recipient of the blame. The tool in question here is the entire system though, including the OS with insufficient permission boundaries in userspace, not just the agent
I love it when Claude is dangerous