os-backlog tracker resolution fails inside git worktrees #73

Open
opened 2026-07-16 19:15:37 +00:00 by jared · 0 comments
Owner

Discovered 2026-07-16 while capturing issues from the os-sdlc worktree (.claude/worktrees/os-sdlc). .cc-os/config is untracked/gitignored, so worktrees don't inherit the tracker key and issue-create fails with 'no valid tracker configured'. Workaround applied: manually copied .cc-os/config into the worktree. Fix options: os-backlog CLI should walk up past .claude/worktrees/ to the owning repo root when resolving .cc-os/config (git worktree detection via 'git rev-parse --git-common-dir'), or EnterWorktree-time provisioning. Matters for os-sdlc: the planned factory runs each spec in its own worktree, so capture/issue ops must work there natively.

Discovered 2026-07-16 while capturing issues from the os-sdlc worktree (.claude/worktrees/os-sdlc). .cc-os/config is untracked/gitignored, so worktrees don't inherit the tracker key and issue-create fails with 'no valid tracker configured'. Workaround applied: manually copied .cc-os/config into the worktree. Fix options: os-backlog CLI should walk up past .claude/worktrees/<name> to the owning repo root when resolving .cc-os/config (git worktree detection via 'git rev-parse --git-common-dir'), or EnterWorktree-time provisioning. Matters for os-sdlc: the planned factory runs each spec in its own worktree, so capture/issue ops must work there natively.
Sign in to join this conversation.
No description provided.