Safer local Git autonomy for sandboxed Codex without broad .git write access #24370
K1-R1
started this conversation in
Show and tell
Replies: 1 comment
-
|
This is fantastic work! It appears to be incredibly helpful. I truly appreciate your efforts in assisting others. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I’ve been working around a local Codex workflow issue: I want to keep Codex in a safer sandbox/approval posture, but local Git operations often need writes under .git. That can push you toward manual Git, repeated approvals, or broader permissions than you actually want.
I built a small local MCP server called codex-safe-git to explore a middle ground.
The idea is not to make .git broadly writable and not to expose arbitrary shell/Git access. Instead, Codex gets a narrow, auditable Git tool surface for local workflows: status, bounded diff summaries, branch prep, and exact-file commits. Remote operations are intentionally out of scope.
You can find it at: https://github.com/K1-R1/codex-safe-git.
Install is via Go:
go install github.com/K1-R1/codex-safe-git/cmd/codex-safe-git-mcp@v0.4.3
Not claiming this replaces any upstream permission work, but it may help people who want Codex to stay sandboxed while still being able to handle local Git more autonomously.
Beta Was this translation helpful? Give feedback.
All reactions