Skip to content

Daemon does not auto-respawn after Stop-Process — leaves project without incremental file-watcher #116

Description

@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 sync no longer auto-detects file edits.

Reproduction

  1. codegraph-vba daemons — pick a project daemon, note its PID
  2. Stop-Process -Id <pid> -Force (e.g. needed to release the DB lock for a forced reindex)
  3. codegraph-vba daemons — observe the project daemon is gone, no replacement
  4. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:vbaVBA/Access-specific work (parent codegraph product)enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions