Original Reddit post

Just had an idea during my 3-5am insomnia rant. Ive been using parrallel agents spawned on docker containers with their own branch to test different solutions . Then I look at the solutions, choose what fits most and lock it in with a pr. Issue is I’m letting claude make mistakes and try things, so I am using dangerously-skip-permission. Thats how I can let it run and come back to it. But any way we can tweak the claudeconfig.json so its like a mimick of dangerously-skip-permission with a few guardrails I set myself? im 99% sure there’s a way. Esp with docker to spawn CC instances with a prebuild claudeconfig that has all the permissions I blindly say yes to, and guardrails towards infra modif stuff etc. Anyone has ressources on that? I’ll post my findings tomorrow if theres any traction here submitted by /u/Davidroyblue

Originally posted by u/Davidroyblue on r/ClaudeCode