You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3ffcbc9
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -153,6 +153,8 @@ When enabled, new projects are indexed automatically on first connection. Previo
153
153
154
154
Watcher registration is controlled separately by `auto_watch` (default `true`). Set `config set auto_watch false` to keep a session from registering its project with the background watcher — useful when working across many projects and you want each session contained to explicit indexing.
155
155
156
+
To turn the watcher off entirely, set `config set watcher_enabled false` (default `true`): the background poll thread never starts and no project is registered, while `auto_index` and manual `index_repository` keep working. Unlike `auto_watch` — which is consulted per session — `watcher_enabled` is read once when the background daemon starts, so run `codebase-memory-mcp daemon stop` after changing it; reconnecting your MCP client alone will not restart the daemon. See [docs/CONFIGURATION.md](docs/CONFIGURATION.md#2-cli-managed-runtime-settings).
157
+
156
158
### Keeping Up to Date
157
159
158
160
**Updates run from the install script on every platform, not from inside the running binary.**`codebase-memory-mcp update` validates your flags and then prints the exact command to run:
@@ -673,6 +675,7 @@ codebase-memory-mcp config list # show all settings
673
675
codebase-memory-mcp config set auto_index true# auto-index on session start
674
676
codebase-memory-mcp config set auto_index_limit 50000 # max files for auto-index
Copy file name to clipboardExpand all lines: docs/CONFIGURATION.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,7 @@ codebase-memory-mcp config list
77
77
codebase-memory-mcp config get auto_index
78
78
codebase-memory-mcp config set auto_index true
79
79
codebase-memory-mcp config set auto_index_limit 50000
80
+
codebase-memory-mcp config set watcher_enabled false
80
81
codebase-memory-mcp config reset auto_index
81
82
```
82
83
@@ -86,6 +87,34 @@ Current keys:
86
87
|---|---|---|
87
88
|`auto_index`|`false`| Automatically index new projects when an MCP session starts. |
88
89
|`auto_index_limit`|`50000`| Maximum file count allowed for automatic indexing of a new project. |
90
+
|`auto_watch`|`true`| Register the session's project with the background git watcher on connect. Set `false` to keep a session from registering its project (the watcher still runs for other projects). |
91
+
|`watcher_enabled`|`true`| Master switch for the background watcher subsystem. Set `false` to stop the watcher from starting at all — no poll thread and no project registration. Reindex manually with `index_repository` when disabled. |
92
+
93
+
> **`watcher_enabled` vs `auto_watch`.**`watcher_enabled` controls whether the
94
+
> watcher *subsystem* starts at all (the background poll thread). `auto_watch` is
95
+
> narrower: it only controls whether a connecting session registers *its own*
96
+
> project with an already-running watcher. When `watcher_enabled=false`,
97
+
> `auto_watch` has no effect — there is no watcher to register with.
98
+
>
99
+
> They also differ in **when they are read**, which matters because the watcher
100
+
> lives in the background daemon, not in your MCP client:
101
+
>
102
+
> -`auto_watch` is consulted each time a session would register its project, so
103
+
> a change applies to sessions that connect afterwards.
104
+
> -`watcher_enabled` is read **once, when the daemon starts**, because it decides
105
+
> whether the watcher is built at all. The daemon is long-lived and outlives
106
+
> individual MCP sessions, so **reconnecting your client is not enough** — retire
107
+
> the daemon so the next one picks the new value up:
108
+
>
109
+
> ```bash
110
+
> codebase-memory-mcp config set watcher_enabled false
111
+
> codebase-memory-mcp daemon stop # next session starts a daemon without the watcher
112
+
> codebase-memory-mcp daemon status # confirm
113
+
>```
114
+
>
115
+
> Disabling the watcher does not disable anything else: the daemon still starts,
116
+
>`auto_index` still runs, and `index_repository` stays available for manual
0 commit comments