[Bug]: t3_worktree_handoff drops git's error message ("git worktree add failed")
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- git, typescript
Research direction
Start in the apps/server area by tracing the t3_worktree_handoff call to GitVcsDriver.createWorktree, where the reported failure comes from. Check how git command errors and stderr are handled, then reproduce a failing git worktree add and confirm the returned error includes git’s message, branch and path.
Written by the indexing model from the issue text.
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
- Fill the disk until it has a few hundred MB free (or any other condition that makes
git worktree addfail for a reason other than the ones T3 already names). - From a Claude thread on the project root, call
t3_worktree_handoffwith{"branch": "fix/example", "baseRef": "origin/main", "startFromOrigin": true, "continuationPrompt": "…"}.
Expected behavior
The error carries git's own message and the ref and path T3 used, e.g. git worktree add failed: fatal: … No space left on device (branch fix/example from origin/main), so the agent can act on it.
Actual behavior
{"_tag":"WorktreeMcpFailure","code":"operation_failed","message":"Unable to create the worktree: Git command failed in GitVcsDriver.createWorktree (<project root>): git worktree add failed"}
git's stderr is dropped. In the case above the agent only found the cause (disk 100% full, 356 MB free) by running git worktree add --dry-run and df itself; the identical handoff call succeeded later once space was freed.
In my usage over one week this generic error came up 3 times in 3 sessions, with different underlying causes. The cases T3 already recognises are clear (e.g. Branch '…' already exists and is checked out at '…'), so this is about the fallback path.
Impact
Minor bug or occasional failure
Version or commit
0.1.10 (desktop); also seen on the build before it
Environment
macOS 27.2 arm64, Claude Code 2.1.327 provider
Logs or stack traces
See "Actual behavior".
Workaround
Run git worktree add --dry-run by hand to see git's message.
Related: #38027, where a missing ref was reported as a different error and the error text didn't name the ref.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 4h 46m
- Merged PRs (30d)
- 488
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
[Bug]: Add provider can create a built-in driver's default instance, which has no delete actionPossibly taken @nateEc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#38462 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day
-
Progress indicated by console logs is off by onePossibly taken @marceliwac claimed this today. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/aws-cdk-examples#1336 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#4999 · 1 comment ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
db-ux-design-system/core-web#8856 ·
Maintainers usually reply within 1 day