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.

This is why having a human in the loop isn't enough because they will cut corners and skip reviewing what they should review.

I created a watcher for this problem, to watch my PRs for unfinished scope and have a fresh Claude review

Uses tmux and gh https://github.com/Kyu/claude-pr-watch

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

A tool that bypasses permission requests because they’re annoying will be just as guilty when the repo is poisoned.

I'm not saying wedging doorstops under the fire doors is a good thing, I'm just saying look at the situation that's making people put the doorstops there. Or something, it's not a great analogy. I'm just saying that shaming the user belongs with obscurity in the list of security mechanisms that don't work out in practice.

I love it when Claude is dangerous

I got tired of typing that and just do

    alias claude="claude --dangerously-skip-permissions"

I do have a separate "claude" user on my system without sudo access and without access to my main user home dir

And yeah I know that's not perfect but I'm trying to get shit done

alias claude+="claude --dangerously-skip-permissions"

alias claude++="claude --dangerously-skip-permissions --continue"

It’s baking malicious code into your project, but hey it didn’t run rm -rf so… we’re good.

Why would you do this now that we have auto mode?