Ad-hoc project attach: project="<absolute dir>" indexes a foreign directory once, read-only, no state written into it (zero-fallback)

buildagent commented

2026-11-09 12:29:11 +01:00

Member

Part of the zero-fallback epic (#555). Cause 2: code outside the configured projects is unreachable.

Observed

Checking a corpus copy (~/.cache/cosi-corpus/cs-dapper, a bind-diff staging dir) meant code-index query --root <dir> in the shell: cold 5–60 s, JSON on stdout, no reuse across calls. sed -n 225,235p won. Workers verifying binds in foreign checkouts did the same.

Proposal

project: "<absolute directory>" on any tool attaches that directory as an ad-hoc read-only project for the session:

indexed once by its own daemon (the existing per-root daemon, reused across calls and sessions);
never fanned out;
disclosed as relationship: ad_hoc with its root;
writes no state into the directory unless it is already a code-index project (see the #546 observation: state dirs appeared in corpus checkouts nobody indexed). Its index lives under the user cache, not in the foreign tree.

Optionally an explicit attach_project(path) for clients that want to pre-warm. The first call answers warming_up with a retry hint rather than blocking.

Acceptance

e2e: from a session rooted elsewhere, search_symbols(project="/tmp/x") warms then answers. A second call reuses the daemon. No .code-index/ is created inside /tmp/x.
The benchmark task "check a bind against source in a foreign checkout" needs zero shell calls.

Part of the zero-fallback epic (#555). Cause 2: **code outside the configured projects is unreachable.** ## Observed Checking a corpus copy (`~/.cache/cosi-corpus/cs-dapper`, a bind-diff staging dir) meant `code-index query --root <dir>` in the shell: cold 5–60 s, JSON on stdout, no reuse across calls. `sed -n 225,235p` won. Workers verifying binds in foreign checkouts did the same. ## Proposal `project: "<absolute directory>"` on any tool attaches that directory as an **ad-hoc read-only project** for the session: - indexed once by its own daemon (the existing per-root daemon, reused across calls and sessions); - never fanned out; - disclosed as `relationship: ad_hoc` with its root; - writes no state into the directory unless it is already a code-index project (see the #546 observation: state dirs appeared in corpus checkouts nobody indexed). Its index lives under the user cache, not in the foreign tree. Optionally an explicit `attach_project(path)` for clients that want to pre-warm. The first call answers `warming_up` with a retry hint rather than blocking. ## Acceptance - e2e: from a session rooted elsewhere, `search_symbols(project="/tmp/x")` warms then answers. A second call reuses the daemon. No `.code-index/` is created inside `/tmp/x`. - The benchmark task "check a bind against source in a foreign checkout" needs zero shell calls.

buildagent added the

Kind/Feature

Priority

Medium

labels

2026-11-09 12:29:11 +01:00

buildagent added a new dependency

2026-11-09 12:29:12 +01:00

#555 Agents still need shell fallbacks to finish code investigation and review

Rows
Columns

Ad-hoc project attach: project="<absolute dir>" indexes a foreign directory once, read-only, no state written into it (zero-fallback) #559

Observed

Proposal

Acceptance