Slightly safer vibecoding by adopting old hacker habits

Post by creata » Wed, Apr 08, 2026, 5:10 AM UTC

kstenerud wrote: post #20

creata wrote: post #16

Earlier quoted context omitted.

The part that worries me here is the diff. Does it happen in the host or in the guest? What code gets run when you run `yoloai diff`?

It actually runs git (with hooks disabled) to generate the diff. It happens on the host when using copy mode, and inside the sandbox when using overlay mode. The above example doesn't specify workdir mounting mode, so it would be copy, not overlay.

Post by monksy » Wed, Apr 08, 2026, 5:14 AM UTC

Post by [deleted] » Wed, Apr 08, 2026, 5:24 AM UTC

thwarted wrote: post #6

dddddaviddddd wrote: post #4

Earlier quoted context omitted.

I believe the author's idea is to do dev work from a Github account that only has access to the fork, but not to the main repo. Then, as a contributor, you'd open PRs from your fork to the main repo. I think this would only work if your Github account doesn't have write access to the main repo, though. I know you can use 'deployment keys' to give read-access to a single repo using an SSH key, but not sure if you can…

Oh, a separate GitHub account that has its own forks of the repos the agent is working on. Yeah, that's probably the most secure, isolated, and safest. The merge to the canonical repo then needs to go through a human, or at least separately controlled, process via a GitHub pull request.

Post by kstenerud » Wed, Apr 08, 2026, 5:38 AM UTC

creata wrote: post #24

kstenerud wrote: post #22

Earlier quoted context omitted.

Absolutely. That's why overlay is not the default.

That's... uh, an interesting approach to security.

Post by tietjens » Wed, Apr 08, 2026, 5:54 AM UTC