Re:A way to exclude sensitive files issue still open for Ope...
by laweijfmvo on Sunday June 28, 2026 @03:59PM
(#48710982)
huh, but what if the AI trashes my git repo? maybe it just deletes the .git folder entirely. a deterministic undo wouldn’t be the silliest feature, for the current definition of “AI”.
[ Parent
| on HN ]
Re:A way to exclude sensitive files issue still open for Ope...
by mirashii on Sunday June 28, 2026 @04:05PM
(#48711049)
The default sandboxing for Codex does not allow the agent to access .git
Re:A way to exclude sensitive files issue still open for Ope...
by valleyer on Sunday June 28, 2026 @04:56PM
(#48711566)
I think this is what you meant, but just to clarify: it doesn't allow it to write to .git. Read access is allowed.
Re:A way to exclude sensitive files issue still open for Ope...
by pamcake on Sunday June 28, 2026 @06:43PM
(#48712514)
The answer is the same: You give it either read-only or its own copy separate from the one you care about.
The requested feature wouldn't be a robust solution here either for the same reasons.
Besides, have you noticed the amount of other amateur-hour bugs anf jank in Codex going for weeks or months without proper resolution? Given that, why would you want and trust their solution here over alternatives, specifically?