Add REST equivalents for recall/forget plus API robustness fixes#131
Merged
rahilp merged 1 commit intoJun 7, 2026
Conversation
Adds GET /recall and POST /forget REST routes that mirror the existing
MCP tools, brings GET /list to filter parity with list_recent (tag,
after, before), and standardizes error responses to { ok: false, error }
across all routes. Extracts shared recallEntries/forgetEntry/
buildEntryFilterQuery/requireAuth helpers so the MCP tools and REST
routes share one implementation, mirroring the existing captureEntry
pattern. Includes integration test coverage for both new routes plus
extended list and auth tests.
Also updates the README endpoint list and links it to the corresponding
wiki documentation.
5 tasks
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
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 /recallandPOST /forgetREST routes that mirror the existingrecall/forgetMCP tools (semantic search with time-decay reranking, and delete-by-id with vector cleanup)GET /listto filter parity withlist_recent(tag,after,before){ ok: false, error }and de-duplicate the repeated auth check via a sharedrequireAuthhelperrecallEntries/forgetEntry/buildEntryFilterQueryhelpers so MCP tools and REST routes share one implementation (mirrors the existingcaptureEntrypattern)/recalland/forget, plus extended/listand auth testsTest plan
npm test— full suite passes (270/270)npx tsc --noEmit— no new type errorsGET /recallandPOST /forgetagainst a deployed worker with a realAUTH_TOKEN