Help test 0.24: opt-in semantic search and background daemon #111
luca-ctx
announced in
Announcements
Replies: 1 comment 6 replies
|
Hey @luca-ctx, thanks for a mention. What's the embedder model, is it multilingual? Tbh I've been prototyping for a few days -- ingesting human replies from ctx and classifying them with tags from the SDLC taxonomy. Gonna make SDLC watchdog of a kind |
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The ctx CLI 0.24 release introduces two important opt-in features: semantic search and a background daemon.
Prior to 0.24, ctx search was lexical only, and incremental refresh generally happened in-process, usually right before
ctx search, so results would be fresh.Semantic indexing is much heavier than lexical indexing. Initial ingestion and incremental refresh take more CPU, memory, and wall clock time, so we do not want ordinary
ctx searchcalls to be delayed by updating semantic indexes.To make this feasible locally, 0.24 introduces a background daemon. When enabled,
ctx setupandctx importcan start daemon-owned maintenance in the background. The daemon refreshes discovered local history sources, keeps lexical indexes fresh, and, when semantic search is also enabled, builds the local semantic sidecar.When semantic search is enabled, the default search backend becomes hybrid: lexical + semantic evidence. You can still force the old path with
ctx search --backend lexical.Because this introduces new local-process and resource-use risk, it is currently behind explicit config opt-in.
ctxdoes not write these defaults into your config file automatically.Enable background daemon only:
Enable background daemon + semantic search:
After changing config, run:
In 0.24, local semantic search is supported on Linux GNU and macOS arm64 builds. Other platforms should continue to work as lexical-safe builds. We will be following up to add support on the other platform builds in 0.25 or another upcoming release.
If you are interested in improving your search results and helping us harden this feature, please enable it and let me know how it goes: setup time, memory/CPU, indexing progress, incremental refresh behavior, search speed, and whether the results are actually better than lexical search for your real agent history.
CC'ing our contributors, thank you so much for your PRs so far. @atharva-patill @daisuke8000 @j2h4u @jongko54 @kj-9 @kuwa2005 @msokh @mtgibbs @nikrich @rNoz @robbe1912 @shinhyo @sin5ddd @yarikoptic @ZhiXiao-Lin
All reactions