Before submitting
Area
apps/web
Problem or use case
Right now, T3 code defaults all worktrees to have the format t3code/<sha>. While this is fine within T3 code, I use an external Git client to manage worktrees and have difficulty linking threads to their worktrees.
Proposed solution
Provide an option to name the worktree manually or with AI, before creating it.
Why this matters
This will make worktrees more identifiable for other clients.
Smallest useful scope
Provide an option to name the worktree manually, before creating it.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/web
Problem or use case
Right now, T3 code defaults all worktrees to have the format
t3code/<sha>. While this is fine within T3 code, I use an external Git client to manage worktrees and have difficulty linking threads to their worktrees.Proposed solution
Provide an option to name the worktree manually or with AI, before creating it.
Why this matters
This will make worktrees more identifiable for other clients.
Smallest useful scope
Provide an option to name the worktree manually, before creating it.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution