Question about work trees?

[allpurposepunk]

How would I catch file edits and/or watch file edits in a git work tree which is a completely different directory then the main repo?

[KingEmma7]

Point codebase-index at the worktree directory itself. The watcher watches its configured root recursively; starting it in the main checkout does not automatically watch other linked worktrees.

# Install the optional watcher dependency in your codebase-index environment.
python -m pip install "codebase-index[watch]"

codebase-index --root /absolute/path/to/worktree index
codebase-index --root /absolute/path/to/worktree watch --debounce 500

--root is a global option, so put it before index or watch. The first command builds the index; the second keeps running and updates it after edits. Query that same root:

codebase-index --root /absolute/path/to/worktree search "your query"

Each checkout gets its own .claude/cache/codebase-index/index.sqlite. Run a separate watcher for each worktree you want to monitor. You can also cd into the worktree and omit --root: root discovery recognizes the linked worktree's .git file.

I checked this with 2.1.2 on macOS using a real linked worktree outside the main repository directory. Editing a Markdown file triggered an incremental update, and a search returned the new contents from the worktree's index. The check covered filesystem events and text indexing.

Sources: watch installation, watcher root, root discovery.

[allpurposepunk]

Thanks I'll check it out