I would not trust auto mode in the first place.

Wrap your agent of choice in e.g. docker sandbox, nono.sh, Nvidia OpenShell, microsanbox or any other sandboxing tool and run it without any checks (i.e. "yolo mode", dangerously-skip-permissions etc.)

IMHO it makes the whole category of problems around permission fatigue, trusting the harness (or plugin) authors etc go away.

Well yeah, the whole point of pi is that you build it to your workflow. If you dislike the entire point of a project, it’s not for you. I run my agents in a sandbox. When Claude or Codex then double sandbox themselves, it gets really annoying.

I use https://pi.dev/packages/pi-warden with Jev (but can use other Decisions API), it would make sense to combine with pi-permission-system to get the CC two stage "default auto" mode.

I wrote pi-automode for exactly that reason. Works well enough for me, YMMV.

https://github.com/czottmann/pi-automode

You'd have to install an extension or write a function that intercepts tool calls.

gotgenes/pi-permission-system and the ai-guard authorizer can do a lot here, it feels very similar to cc auto mode.

I built a policy authorizer on top of pi-permission-system that looks kinda like nftables that models commands/subcommands/options as read/write and enfores policies depending on if the sub agent is read only or write, which really cuts down on the stupid decisions and nicely complements AI cmd review. Pi shines for making things like that possible.

You have time to watch over your agents?

like the auto mode classifier? if it doesn't then... that's a risky tradeoff

Sounds to me like it isnt basic functionality if it all works ;)

> bear bones

*bare