feat: add offset parameter for message pagination #10198
+72
−7
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
offsetquery parameter toGET /session/:id/messageendpoint for efficient paginationloadMoreto use offset-based loading instead of re-fetching all messagesProblem
Previously, loading more messages in long sessions required re-fetching all messages from the start with an increased limit. For example, to load 100 more messages when you already have 400, the client would fetch all 500 messages again.
Solution
With the new
offsetparameter, clients can skip already-loaded messages:GET /session/:id/message?limit=400(400 messages)GET /session/:id/message?limit=100&offset=400(only 100 new messages)This reduces bandwidth and improves performance for long sessions.
Test plan
completeflag is set when no more messages exist🤖 Generated with Claude Code