The problem
I work across 100+ git repos using Claude Code worktrees, kept under VS Code's default worktree layout:
{repo}.worktrees/{branch}
agentsview already does path-based project resolution for Superset, Conductor, Middleman, and Codex layouts, but not the one I'm using and I'm not sure I should expect it to find all my repos, since they're located in my own ~/code directory and not some application-specific directory.
agentsview groups these under the right project while the worktree directory exists. But once I delete a worktree, there's nothing left on disk to tie the session's working directory back to the repo, and resolution falls back to the branch name instead of the project name I'd like it to be.
Worktree mappings address this, but it's not practical to manage 100+ through the GUI. As a workaround, I wrote a script to discover my worktrees and add mappings through the API.
The request
Add a feature to add custom path → project mapping layouts similar to the existing Superset/Conductor/Middleman/Codex ones:
{repo}.worktrees/{branch} ⇒ {repo}
Alternatively, consider adding support for the {repo}.worktrees/{branch} pattern.
The problem
I work across 100+ git repos using Claude Code worktrees, kept under VS Code's default worktree layout:
agentsview already does path-based project resolution for Superset, Conductor, Middleman, and Codex layouts, but not the one I'm using and I'm not sure I should expect it to find all my repos, since they're located in my own
~/codedirectory and not some application-specific directory.agentsview groups these under the right project while the worktree directory exists. But once I delete a worktree, there's nothing left on disk to tie the session's working directory back to the repo, and resolution falls back to the branch name instead of the project name I'd like it to be.
Worktree mappings address this, but it's not practical to manage 100+ through the GUI. As a workaround, I wrote a script to discover my worktrees and add mappings through the API.
The request
Add a feature to add custom path → project mapping layouts similar to the existing Superset/Conductor/Middleman/Codex ones:
Alternatively, consider adding support for the
{repo}.worktrees/{branch}pattern.