Before submitting
Area
apps/server
Steps to reproduce
- Open a thread on a repository that has no git remote (
git remote prints nothing) — e.g. a local-only brainstorming repo, thread running in a linked worktree.
- Let the agent edit files so the working tree has uncommitted changes (
git status lists them).
- Open the changes/diff view.
Expected behavior
The view lists the changed files and renders diffs. The data exists: per-turn checkpoint refs (refs/t3/checkpoints/<thread>/turn/N) are created, projection_turns.checkpoint_files_json records the correct per-file additions/deletions, and the latest checkpoint tree matches the working tree.
Actual behavior
The view shows "0 changes" and no diffs can be opened. checkpoint_diff_blobs stays empty. The server trace shows every refresh failing while resolving the diff base: resolvePrimaryRemoteName throws GitCommandError: No git remote is configured for this repository (inside resolveRemoteRepositoryContext → resolveDefaultBranchName → resolveCurrentUpstream), which kills the whole diff computation even though checkpoints and the local branch are sufficient to render it. A fallback to the local default branch / checkpoint refs when no remote exists would fix it.
Impact
Major degradation or frequent failure
Version or commit
0.0.34-nightly.20260815.1102 (desktop AppImage)
Environment
NixOS (Linux 6.18), local backend, git linked worktree, agent edits made via shell tools
Logs or stack traces
{"type":"effect-span","name":"resolvePrimaryRemoteName", ... "exit":{"_tag":"Failure","cause":"GitCommandError: Git command failed in GitVcsDriver.resolvePrimaryRemoteName (~/.t3/worktrees/<project>/<thread>): No git remote is configured for this repository.\n at .../resources/app.asar/apps/server/dist/bin.mjs:73997:17"}}Workaround
git remote add origin <url> on the repo — any configured remote (it does not need to exist upstream) makes diff-base resolution succeed and the view populate. Possibly related symptom-wise: #5616.
Before submitting
Area
apps/server
Steps to reproduce
git remoteprints nothing) — e.g. a local-only brainstorming repo, thread running in a linked worktree.git statuslists them).Expected behavior
The view lists the changed files and renders diffs. The data exists: per-turn checkpoint refs (
refs/t3/checkpoints/<thread>/turn/N) are created,projection_turns.checkpoint_files_jsonrecords the correct per-file additions/deletions, and the latest checkpoint tree matches the working tree.Actual behavior
The view shows "0 changes" and no diffs can be opened.
checkpoint_diff_blobsstays empty. The server trace shows every refresh failing while resolving the diff base:resolvePrimaryRemoteNamethrowsGitCommandError: No git remote is configured for this repository(insideresolveRemoteRepositoryContext→resolveDefaultBranchName→resolveCurrentUpstream), which kills the whole diff computation even though checkpoints and the local branch are sufficient to render it. A fallback to the local default branch / checkpoint refs when no remote exists would fix it.Impact
Major degradation or frequent failure
Version or commit
0.0.34-nightly.20260815.1102 (desktop AppImage)
Environment
NixOS (Linux 6.18), local backend, git linked worktree, agent edits made via shell tools
Logs or stack traces
{"type":"effect-span","name":"resolvePrimaryRemoteName", ... "exit":{"_tag":"Failure","cause":"GitCommandError: Git command failed in GitVcsDriver.resolvePrimaryRemoteName (~/.t3/worktrees/<project>/<thread>): No git remote is configured for this repository.\n at .../resources/app.asar/apps/server/dist/bin.mjs:73997:17"}}Workaround
git remote add origin <url>on the repo — any configured remote (it does not need to exist upstream) makes diff-base resolution succeed and the view populate. Possibly related symptom-wise: #5616.