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 72edfce
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,6 +224,8 @@ The install script placed beside the binary is **reported, not deleted** — uni
224
224
-**`CROSS_*` edges** link nodes across multiple repos indexed under the same store
225
225
-**Multi-galaxy 3D UI layout** for cross-repo architecture visualization
226
226
-**Cross-repo architecture summary** combining services, routes, and dependencies across the indexed fleet
227
+
-**Run status**: `index_status` (and the UI layout next to `linked_projects`) carries a `cross_repo` object, `{"status":"never_run"}` until `index_repository(mode="cross-repo-intelligence")` has run with that project as the source, then `"ran"` with `last_run_at`, `outcome`, `targets`, `projects_scanned`, `total_cross_edges` and `skipped_projects`. That is how you tell "never linked" apart from "linked, nothing matched". The status is stored in the project's own index next to its `CROSS_*` edges, so a reindex that rebuilds the index drops both at once and the status goes back to `never_run`.
228
+
-**Skipped stores**: `target_projects: ["*"]` skips an index built before the #768 schema change rather than failing the whole run. The response lists each one as `skipped_projects: [{"name", "reason": "pre_768_schema", "hint": "reindex this project"}]`.
227
229
228
230
### Edge types (selected)
229
231
-`CALLS` — a callable is invoked at the source site
Copy file name to clipboardExpand all lines: docs/CONFIGURATION.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,6 +242,33 @@ be indexed and later returned. And the credential list is a denylist, so it
242
242
raises the cost of a mistake rather than closing the class — a directory it does
243
243
not name is permitted.
244
244
245
+
### Shared / HPC filesystems
246
+
247
+
On clusters and other shared machines, home directories often live on a network
248
+
filesystem (NFS, Lustre, GPFS, SMB/CIFS), and `~/.cache` is sometimes a symlink
249
+
into a shared tree. Three rules keep CBM working there:
250
+
251
+
-**Put the cache and the rendezvous on local storage.** Set `CBM_CACHE_DIR` (indexes,
252
+
`_config.db`) and, if needed, `CBM_RUNTIME_DIR` (the daemon rendezvous) to a
253
+
local disk you own, for example `/local/scratch/$USER/cbm` or `/tmp/$USER-cbm`.
254
+
Set the same values in your MCP client's environment and your shell.
255
+
-**Do not route the cache into another account's tree.** A symlinked `~/.cache` is
256
+
resolved and allowed, but every directory on the *resolved* path must be owned
257
+
by you or by root. If a parent such as `/shared/fs` belongs to another account,
258
+
that account can rename or replace anything below it, so CBM refuses the path
259
+
and names the directory and its owner:
260
+
261
+
```text
262
+
... (cache-private) - '/shared/fs' is owned by uid 1234 (alice), not by you (uid 1000) or root; ...
263
+
```
264
+
265
+
This check has no override. Choose a location with a safe ancestry instead.
266
+
-**Avoid network filesystems for the cache.** The indexes are SQLite databases in
267
+
WAL mode, which needs shared-memory locking that network filesystems do not
268
+
provide reliably. On Linux, CBM logs one `daemon.cache_root_network_fs` warning
269
+
at startup when the cache root is on NFS, Lustre, GPFS, CIFS or SMB2. The cache
270
+
still works there, but it can be slow, and a database can be corrupted.
271
+
245
272
## 5. Agent and Editor Integration Files
246
273
247
274
The `install` command can also write MCP entries and instruction blocks into agent/editor config files such as Claude Code, Codex, Gemini, VS Code, Cursor, Zed, and others.
0 commit comments