Repository navigation
Default worktree option breaks agent prompts in projects without a Git remote #17741
Description
Activity
Note
Grok responding on behalf of Julius.
Thanks for the report! This is already handled on
main:- Repos with no
originremote: fix(server): skip origin fetch when creating worktrees in repos without an origin remote #5556 (the fix for [Bug]: "Start from origin" is offered for repositories with no remote, failing every thread send #5408) skips the origin fetch and branches the worktree from the local base branch, and fix(server): allow local-only worktree bases #8751 (for [Bug]: "Start from origin" aborts thread bootstrap when the base branch has no remote-tracking ref #8191) allows local-only worktree bases when the remote branch is missing. The current thread launch path still checksremoteExistsbefore taking the origin route. - Folders that aren't Git repositories: fix(server): fall back when new worktrees are unavailable #6208 falls back to starting in the project directory instead of failing worktree creation.
Closing as already fixed. If you still hit this on the latest release, please comment with your T3 Code version and the exact error and we'll reopen.
- Repos with no
Description
In a local-only Git project with no remote, the default "start in a new worktree from origin/main" option breaks prompts sent to the agent. The project has no
origin/mainto use as a worktree base.The reporter manually verified this behavior.
Steps to reproduce
Actual behavior
The prompt fails to start the agent successfully when the worktree option targets the nonexistent
origin/main.Expected behavior
For local-only Git projects, the default should use the current checkout as the base for the new worktree rather than assume
origin/mainexists.For folders that are not Git repositories, the agent should start in the current project directory without attempting to create a Git worktree.