News for hackers. Stuff that matters.
Re:Devvm.dev: One VM for every project by mnahkies on Friday November 06, 2026 @04:04PM (#50398518)
On the git access part, I don't let my agent VMs have write access to GitHub currently. I do give them dedicated users on a self hosted gitea instance, and basically manage the blast radius through branch protection etc.

I think at a high level I'm trying to treat them as junior/intern employees where I give them enough permission to do their role, but not enough rope to hang themselves.

Re:Devvm.dev: One VM for every project by evertheylen on Friday November 06, 2026 @04:16PM (#50398653)
I see. But then I have to debug some failing CI pipeline and the agent is quite good at going through the logs, so I give in and `gh auth login` anyway...
Re:Devvm.dev: One VM for every project by mnahkies on Friday November 06, 2026 @05:19PM (#50399263)
I'm pretty sure you don't need to give it full access to accomplish that. It's possible to create scoped PAT etc. alternatively use a separate account. Ultimately your risk tolerance to decide