Repository navigation
Open
Labels
editor/integrationEditor compatibility and CLI integrationEditor compatibility and CLI integrationwindowsWindows-specific issuesWindows-specific issues
Description
Summary
A generated client hook spawns codebase-memory-mcp hook-augment on every tool result, even when the current directory is not covered by any indexed project. In that state the call cannot produce anything useful: it walks up ancestors, falls back to scanning the whole cache and opening every project DB, and then returns the same generic hint every time:
[codebase-memory] Session context: no indexed graph project matched this working directory.
Run index_repository before structural exploration. ...
A no-op should cost nothing. Today it costs a process spawn, a cache scan, an on-access AV scan, and — on Windows — a console window.
Environment
- codebase-memory-mcp 0.12.1, Windows 11
- OpenCode 2 (V2
setup(ctx)surface,execute.aftertool hook); the plugin calls the standalone CLI with stdin JSON:SessionStart,PreToolUse(Grep/Glob),PostToolUse(Read) - Cache state during measurement:
list_projects→projects: 0, i.e. nothing indexed on the machine
Observed
- One
hook-augmentprocess per tool result (measured 10–20 spawns per minute in an active session). - On Windows the client runs as a detached service process without a console, so each spawn allocates a fresh console window (
conhost/OpenConsole -Embedding) that appears and closes; the user sees a terminal flicker per tool call. - Every launch of the executable is also picked up by on-access AV scanning.
- The answer does not depend on the tool or the payload: for a directory with no index the outcome is always the same hint, and nothing in the payload can change that until the project is indexed.
Proposal (any one is enough for a client-side gate)
- Exit before the ancestor walk and the cache scan when the cache contains no project DBs at all — in that state neither step can succeed.
- A machine-readable gate: e.g.
hook-augment --if-indexed(or a documented exit code) that answers "iscwdcovered by an indexed project?" without emitting augmentation text, so a client can skip the call entirely. - A documented, stable offline check. The cache layout is already effectively a contract —
<cache>/<project>.db, tableprojects, single row withroot_path(src/store/store.c, incl. the "no ghost .db for unknown/unindexed projects" invariant) — but it is not documented as public API. If it were, a client could verify with the host runtime's built-in SQLite and spawn nothing. - Generated plugins: register the hook only when the project is indexed, and/or cache the answer. Workaround used today: read
root_pathfrom the project DBs in the cache via the runtime's built-in SQLite (bun:sqlite/node:sqlite), fail open when verification is impossible, re-check every 5 minutes.
Independently of the gating, generated plugins should spawn with windowsHide: true: a console window per tool call is user-visible noise (same class of problem as #1427).
Related
- hook-augment restarts full daemon on every invocation, causing ~3s latency per call and hook timeouts #2058 —
hook-augmentrestarts the daemon on every invocation (~3 s per call) - Windows v0.9.1-rc.1: detached daemon spawns focus-stealing cmd.exe / Windows Terminal windows #1427 — detached daemon spawns focus-stealing console windows (closed)
Metadata
Metadata
Assignees
Labels
editor/integrationEditor compatibility and CLI integrationEditor compatibility and CLI integrationwindowsWindows-specific issuesWindows-specific issues
Activity