Symptom
After killing the codegraph-vba daemon for a project (e.g. Stop-Process -Id <pid> to release the DB lock for a reindex), no new daemon is spawned for that project. The MCP server keeps answering queries (it reads the DB directly), but the incremental file-watcher is gone — codegraph-vba sync no longer auto-detects file edits.
Reproduction
codegraph-vba daemons — pick a project daemon, note its PID
Stop-Process -Id <pid> -Force (e.g. needed to release the DB lock for a forced reindex)
codegraph-vba daemons — observe the project daemon is gone, no replacement
- Edit any file in the project —
codegraph-vba sync <project> must be run manually; nothing else picks up the change
Expected
A new daemon spawns for the project (e.g. on the next MCP tick, or immediately on detection that the project has a .codegraph-vba/ but no daemon).
Actual
Daemon is gone until the user manually runs codegraph-vba sync or restarts the MCP server. The error message in codegraph-vba index correctly says "Stop any running CodeGraph MCP server/daemon for this project and retry" — but does not suggest the reverse (respawn).
Workaround
codegraph-vba sync <project> spawns a fresh daemon and immediately syncs.
Context
/cc @ardelperal
Symptom
After killing the codegraph-vba daemon for a project (e.g.
Stop-Process -Id <pid>to release the DB lock for a reindex), no new daemon is spawned for that project. The MCP server keeps answering queries (it reads the DB directly), but the incremental file-watcher is gone —codegraph-vba syncno longer auto-detects file edits.Reproduction
codegraph-vba daemons— pick a project daemon, note its PIDStop-Process -Id <pid> -Force(e.g. needed to release the DB lock for a forced reindex)codegraph-vba daemons— observe the project daemon is gone, no replacementcodegraph-vba sync <project>must be run manually; nothing else picks up the changeExpected
A new daemon spawns for the project (e.g. on the next MCP tick, or immediately on detection that the project has a
.codegraph-vba/but no daemon).Actual
Daemon is gone until the user manually runs
codegraph-vba syncor restarts the MCP server. The error message incodegraph-vba indexcorrectly says "Stop any running CodeGraph MCP server/daemon for this project and retry" — but does not suggest the reverse (respawn).Workaround
codegraph-vba sync <project>spawns a fresh daemon and immediately syncs.Context
gestion_riesgoscodegraph-vba upgrade --checkconfirms v1.7.0c52c067in consumer workflow repo for the full session context/cc @ardelperal