[BUG] Checkpointing disabled when workspace root is not a Git repository

[jfcantu]

Problem (one or two sentences)

RooCode is incorrectly telling me that checkpointing is disabled because of nested Git repositories.

Context (who is affected and when)

Any time I try and run a task.

Reproduction steps

1. Create a new workspace folder.
2. Clone a Git repository into that folder, so that the Git repository appears as a child folder (i.e., /workspace-root/cloned-repository/)
3. Open the workspace folder in VSCode, and then try and run any RooCode tasks.

Expected result

The task should start and run normally.

Actual result

The task runs, but warns that checkpointing is disabled due to nested Git repositories.

Variations tried (optional)

Tried running RooCode directly in a cloned repository - error did not occur.

App Version

3.28.3

API Provider (optional)

AWS Bedrock

Model Used (optional)

N/A

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

I suspect that, since my workspace root is not a Git repository, RooCode is actually initializing shadow-git there and therefore creating nested repositories on its own.


[Task#getCheckpointService] initializing shadow git
[t#getNestedGitRepository] found 3 nested git repositories, first at: vela
[Task#getCheckpointService] initShadowGit -> Checkpoints are disabled because a nested git repository was detected at: vela. Please remove or relocate nested git repositories to use the checkpoints feature.

[roomote]

I'm exploring a potential fix for this issue where checkpointing is incorrectly disabled when the workspace root is not a Git repository. I'll investigate the shadow-git initialization logic and work on a solution.

[roomote]

I've opened PR #8166 with a fix for this issue: #8166

The fix modifies the nested Git repository detection logic to only check for nested repos when the workspace itself is a Git repository. This allows legitimate Git repositories in non-Git workspaces (like your use case) while still preventing actual nested repositories.

The solution includes:

• Updated logic in ShadowCheckpointService.ts to check if workspace is a Git repo first
• Comprehensive test coverage for this specific scenario
• All existing tests continue to pass

CI checks are currently running on the PR. Once they pass and the PR is reviewed, this should resolve the false positive warning you were experiencing.

[jfcantu]

I'm not sure if roomote monitors these comments, but if so - I'd like to emphasize for it that it's just my theory that shadow-checkpointing is the root cause here, I'm not 100% sure.

[hannesrudolph]

You said that you cloned it so it is in a child folder. That is nested.