Repository navigation
0.7.0: search conversations by title and message text - #12
Merged
Merged
Conversation
GET /conversations?q= finds conversations by title and message text through the storage (memory, SQLite, PostgreSQL, MongoDB), with a title-only fallback for providers without search. Hits carry searchMatch; GET /agents publishes features.conversationSearch. Version 0.7.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017HHyW73QVfidhhA9SGWdHM
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
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.
Summary
GET /conversations?q=searches conversation titles and message text (2–200 chars; longer → 400invalid_request), scoped by the same user/agent filters as the list, ordered byupdatedAtdesc.searchMatch { field, messageId?, role?, snippet }; the response carriessearchMode(full|title).search: memory, sqlite, postgres and mongodb implement it with escaped LIKE / regex. Storage without it falls back to a title filter over the 500 most recent conversations in scope.GET /agentsadvertisesfeatures.conversationSearch.Test plan
🤖 Generated with Claude Code