Indexing speed, quantization, semantic chunking, and search-quality improvements #1
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
azer/ripsem-forge-archive!1
Loading…
Reference in a new issue
No description provided.
Delete branch "indexing-improvements"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Works through the project roadmap (now / next / later) while adding a test
suite, CI, and end-to-end verification with the real embedding model. The
default build stays lean (lexical backend, line chunking); the heavier
capabilities are opt-in cargo features.
Indexing — faster and smaller
vector, query stays f32 for accuracy). Index gains a
format_versionso astale index reports a clear "rebuild" message instead of decoding garbage.
and parallelise file read + change detection.
.git, apply the configuredexcludeglobs (previously a deadfield), and guard against reusing vectors after a model/dimension change.
Search — better results
treesitterfeature: chunk on function/type boundaries across 17 languages,with a tuned size cap for focused snippets; line-window fallback otherwise.
hnswfeature: optional approximate index that auto-activates above ~20kchunks; the exact flat scan stays the default for smaller repos.
searchto a subdirectory against the warm index.watchandthe server).
semantic ranking.
Product maturity
statuscommand (index size, chunk/file counts, model, staleness).install cursoralongsideinstall claude-code; install no longer clobbersexisting MCP servers.
repositorymetadata, cleaned-up path output.Tests, CI, and verification
quantization, and the full index/search/incremental flow (lexical backend, no
model download).
#[ignore]d so CI needs no download. On a multi-domain corpus they reportrecall@1 = 1.00 and MRR = 1.000.
--all-features, denying warnings), thedefault test suite, the pure-Rust feature tests, and an all-features build.
Verified end-to-end with the real model: semantic (by-meaning) retrieval, the
full MCP handshake, content-hash incremental indexing, and ~4 ms warm searches.