jif-oaiandGitHub 554223ab80 feat: paginate memories MCP search results (#20996) ...

## Why

The memories MCP `search` tool previously stopped once it hit
`max_results`, so callers could tell there were more matches via
`truncated` but had no way to fetch the rest of the result set. That
made large searches awkward for clients that need to keep paging through
a stable, deterministic view of the matches.

## What changed

- add an optional `cursor` field to `SearchMemoriesRequest` / tool input
and return `next_cursor` in `SearchMemoriesResponse`
- update the MCP schemas and tool wiring so clients can request
subsequent pages explicitly
- change the local memories backend to collect and sort the full scoped
match list, then slice the requested page and reject invalid cursors
- add unit coverage for paginated search results and invalid cursor
handling in `memories/mcp/src/local_tests.rs`

## Testing

- Added targeted unit coverage in `memories/mcp/src/local_tests.rs`
- GitHub Actions are running for the branch

2026-05-04 15:23:10 +02:00

..

src

feat: paginate memories MCP search results (#20996)

2026-05-04 15:23:10 +02:00

BUILD.bazel

feat: memories mcp v1 (#20622)

2026-05-04 13:51:03 +02:00

Cargo.toml

feat: memories mcp v1 (#20622)

2026-05-04 13:51:03 +02:00