I'm using Claude Code in VS Code with a workspace that is not a single git repo — it's a directory (/Users/me/github/org-workspace/) containing ~15 sibling git repos and their active git worktrees. The VS Code extension always launches Claude with cwd = org-workspace/, which I want to keep so I can jump between repos freely. I've registered 4 repos in ~/.code-review-graph/registry.json and each has a correctly built .code-review-graph/graph.db.
The problem: .mcp.json runs uvx code-review-graph serve with no --repo, so _resolve_repo_root() falls back to cwd (the non-git workspace root), the PostToolUse code-review-graph update --skip-flows hook does the same, and that builds a junk 12-file graph at the workspace root that all tool calls without an explicit repo_root hit by default. cross_repo_search_tool works across the registry, but the other 20+ tools still need repo_root on every call.
What's the recommended setup for this topology — outer git repo whose real purpose is to host many nested registered sibling repos + worktrees, IDE-fixed cwd on the outer — so that
(a) tool calls without explicit repo_root route sensibly (fan out over the registry, or infer from the edited/queried file path) instead of defaulting to the outer repo,
(b) the update hook writes to the correct nested graph,
(c) worktrees auto-resolve from their main repo instead of needing individual registration, and
(d) the outer repo can be excluded from serving entirely (is there a flag, or is the intended pattern to run one serve per registered repo)?
Running code-review-graph 2.3.2 on macOS with the Claude Code VS Code extension.
I'm using Claude Code in VS Code with a workspace that is not a single git repo — it's a directory (/Users/me/github/org-workspace/) containing ~15 sibling git repos and their active git worktrees. The VS Code extension always launches Claude with cwd = org-workspace/, which I want to keep so I can jump between repos freely. I've registered 4 repos in ~/.code-review-graph/registry.json and each has a correctly built .code-review-graph/graph.db.
The problem: .mcp.json runs uvx code-review-graph serve with no --repo, so _resolve_repo_root() falls back to cwd (the non-git workspace root), the PostToolUse code-review-graph update --skip-flows hook does the same, and that builds a junk 12-file graph at the workspace root that all tool calls without an explicit repo_root hit by default. cross_repo_search_tool works across the registry, but the other 20+ tools still need repo_root on every call.
What's the recommended setup for this topology — outer git repo whose real purpose is to host many nested registered sibling repos + worktrees, IDE-fixed cwd on the outer — so that
Running code-review-graph 2.3.2 on macOS with the Claude Code VS Code extension.