anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #10198] feat: add offset parameter for message pagination #13364

New Issue
Open
opened 2026-02-16 18:18:13 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:18:13 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/10198

State: open
Merged: No

Summary

  • Add offset query parameter to GET /session/:id/message endpoint for efficient pagination
  • Update desktop app's loadMore to use offset-based loading instead of re-fetching all messages
  • Only fetches additional messages needed, then merges them into existing state

Problem

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 offset parameter, clients can skip already-loaded messages:

  • Initial load: GET /session/:id/message?limit=400 (400 messages)
  • Load more: GET /session/:id/message?limit=100&offset=400 (only 100 new messages)

This reduces bandwidth and improves performance for long sessions.

Test plan

  • Verify initial message loading still works
  • Verify loading more messages appends correctly
  • Verify complete flag is set when no more messages exist
  • Test with sessions of varying lengths

🤖 Generated with Claude Code

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/10198 **State:** open **Merged:** No --- ## Summary - Add `offset` query parameter to `GET /session/:id/message` endpoint for efficient pagination - Update desktop app's `loadMore` to use offset-based loading instead of re-fetching all messages - Only fetches additional messages needed, then merges them into existing state ## Problem 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 `offset` parameter, clients can skip already-loaded messages: - Initial load: `GET /session/:id/message?limit=400` (400 messages) - Load more: `GET /session/:id/message?limit=100&offset=400` (only 100 new messages) This reduces bandwidth and improves performance for long sessions. ## Test plan - [ ] Verify initial message loading still works - [ ] Verify loading more messages appends correctly - [ ] Verify `complete` flag is set when no more messages exist - [ ] Test with sessions of varying lengths 🤖 Generated with [Claude Code](https://claude.ai/code)
yindo added the pull-request label 2026-02-16 18:18:13 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#13364
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?