Type

Bug

Problem / Value

In Dev Containers that set GIT_DIR, Roo’s checkpoint commits go to that location instead of the shadow repository. This causes unintended commits in the wrong repo and developer confusion.

Context

Affects developers using VS Code Dev Containers that define a global GIT_DIR (e.g., via remoteEnv). Occurs whenever Roo creates a checkpoint (reported on v3.19.7). The expected behavior is that checkpoint operations always target Roo’s shadow repo regardless of ambient git env.

Reproduction

1 Configure a Dev Container with remoteEnv setting GIT_DIR (e.g., GIT_DIR=/somewhere)
2) Start a Roo session and trigger a checkpoint
3) Observe the commit landing in GIT_DIR instead of the shadow repo

Expected

Checkpoint commits are isolated to Roo’s shadow repository and do not honor external GIT_DIR.

Actual

Commits are made to the path specified by GIT_DIR when present.

Acceptance Criteria

• Checkpoint/shadow-repo git operations are isolated from inherited environment variables (GIT_DIR, GIT_WORK_TREE, etc.)
• Behavior consistently targets the shadow repo across Dev Containers and local environments
• Change is scoped so other user workflows that rely on GIT_DIR outside checkpoints are unaffected

Notes

• Ensure checkpoint operations sanitize or override relevant git env for the duration of the operation only