Repository navigation
installing again via install script is dark pattern: "rebuild index" message followed by delete index action #607
Description
Version
codebase-memory-mcp 0.8.1
Platform
Linux (x64)
Install channel
GitHub release archive / install.sh / install.ps1
Binary variant
standard
What happened, and what did you expect?
the install suggested rebuilding indexes, then gives y/n prompt to nuke them.
Upon starting the web ui again, I am unable to create new indexes, either.
I expected the binary to update
cooked.
"Configuring coding agents...
codebase-memory-mcp install 0.8.1
Found 1 existing index(es) that must be rebuilt:
/home/***/.cache/codebase-memory-mcp/_config.db
Delete these indexes and continue with install? (y/n): y (auto)
Removed 1 index(es)."
Says indexes need to be rebuilt and next prompt gives y/n to delete them.
No instructions to rebuild.
No rebuild index command:
codebase-memory-mcp --help | grep rebuild
No rebuild index in the now empty ui:
Adding index now has no effect, only solution is to fully uninstall and start over.
at minimum it should remember which directories were indexed before unceremoniously nuking them and forcing the user through the terrible ergonomics of adding many new indexes. #608
Reproduction
- Install older version
- Run install script
- Experience dead end.
Logs
None.
Project scale (if relevant)
30 projects, 1/4 million nodes or so.
Confirmations
- I searched existing issues and this is not a duplicate.
- My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.
Back to grafify
Activity
[-]No clear upgrade path, installing again via install script nukes indexes[/-][+]installing again via install script cues "rebuild index" with not clear path forward[/+][-]installing again via install script cues "rebuild index" with not clear path forward[/-][+]installing again via install script is dark pattern: "rebuild index" message followed by delete index action[/+]test(repro): more install/UX + persistence reproductions for #607, #403…
fix: bulk parallel — Rust cross-crate, Python builtins, #607 reinstal…
DeusData commentedon Jun 28, 2026
This issue now has a first-class, durable reproduction in the cumulative bug-reproduction suite landing in #667 — a test that pins the exact failing behaviour, so it's tracked and guarded against silent regression. Where #667 also lands the root-cause fix, that's called out in the PR; otherwise the reproduction makes the eventual fix straightforward and verifiable.
The reproduction goes live once #667 merges. (Posted from the release branch's QA pass.)
fix: 17 reproduce-first issue + new-bug fixes (per-case verified)
DeusData commentedon Sep 26, 2026
Thank you, @dskvr, for calling this out so directly. You were right that "must be rebuilt" followed by a delete prompt was a dead end that lost your indexes.
Since v0.9.0,
installkeeps existing indexes by default. It only tells you to re-index to pick up extraction improvements, and deleting requires an explicitinstall --reset-indexes. The update hand-off never treats-yas consent to delete indexes, and a test now pins that. Remembering previously indexed folders is tracked separately in #608.Closing as fixed. Please reopen if anything on v0.11.0 still removes an index without you asking.
test(cli): pin that `update -y` never deletes project indexes (DeusDa…