ghrl 8 minutes ago

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.

Liftyee 6 minutes ago

I haven't used local agentic AI yet for programming projects. Hence, -187 score

The filter for "commands I would run myself" and "commands I would let an agent run" are very different it seems.

MeetingsBrowser 19 minutes ago

It would be cool to see the distribution of all player scores.

sevenseacat 15 minutes ago

Continue? Y/N ── SCORE: 2,343 Security-Conscious Engineer

Caught 8/8 threats "Not a single secret leaked"

→ llmgame.scalex.dev

carterschonwald 22 minutes ago

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 ;)

cadwell 25 minutes ago

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 :)

nardib 2 hours ago

Use this and save yourself:

claude --dangerously-skip-permissions

  • wildpeaks 26 minutes ago

    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.

    • chuckadams 21 minutes ago

      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

  • tasuki 18 minutes ago

    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.