-
Notifications
You must be signed in to change notification settings - Fork 0
Add cursor pagination to chat sessions and messages #54
Copy link
Copy link
Open
Labels
area: agentsAgent runtime, agent APIs, tools, prompts, or UI.Agent runtime, agent APIs, tools, prompts, or UI.component: apiHTTP API, OpenAPI contract, or API client concern.HTTP API, OpenAPI contract, or API client concern.priority: P3Low; backlog, cleanup, or opportunistic work.Low; backlog, cleanup, or opportunistic work.type: featureNew user-facing or operator-facing capability.New user-facing or operator-facing capability.
Description
Activity
Metadata
Metadata
Assignees
Labels
area: agentsAgent runtime, agent APIs, tools, prompts, or UI.Agent runtime, agent APIs, tools, prompts, or UI.component: apiHTTP API, OpenAPI contract, or API client concern.HTTP API, OpenAPI contract, or API client concern.priority: P3Low; backlog, cleanup, or opportunistic work.Low; backlog, cleanup, or opportunistic work.type: featureNew user-facing or operator-facing capability.New user-facing or operator-facing capability.
What to build
Chat sessions and chat messages paginate using the estate cursor convention: an opaque cursor and a limit going in, an items array and a next cursor coming back.
These are the collections in this service that genuinely grow without bound. Bounded collections — workspaces, repositories, projects, credentials — are deliberately left alone, because turning every list into an envelope is a breaking change across the estate for collections that hold single digits.
The cursor shape is chosen over page and size because it stays stable under concurrent inserts, which is what an infinitely scrolling message list needs.
Acceptance criteria
Blocked by