Replace DuckDB with SQLite storage - #216
Merged
Merged
Conversation
gadenbuie
marked this pull request as ready for review
September 9, 2026 14:49
gadenbuie
added this pull request to stack #217
September 9, 2026 14:49
gadenbuie
force-pushed
the
feat/sqlite
branch
from
September 9, 2026 14:51
798ae75 to
6b12877
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacks on #215.
Summary
Replace DuckDB with a shared RSQLite database for persistent conversation history and project code search. Add per-project FTS5 trigram indexes, incremental refresh, retention, busy handling, and server-side conversation resume pointers.
Verification
btw pkg test --path .