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

[PR #8996] feat(session): add ts_before and breakpoint params to Session.messages API #12943

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

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

State: open
Merged: No

Summary

Adds two optional parameters to Session.messages() API for loading messages older than the initial 100-message window:

  • ts_before: Unix timestamp - returns messages created before this point
  • breakpoint: Boolean - when true, stops at the first compaction summary

Problem

Multiple open issues request the ability to access message history beyond the initial 100-message limit:

  • Resolves #6137 - Cannot scroll to beginning of long conversations
  • Resolves #4918 - Feature request: pagination for messages & sessions
  • Resolves #7380 - Old messages disappear
  • Related #6548 - Pagination work

Current Session.messages() only supports a limit parameter, which returns the N most recent messages. There is no way to retrieve older messages.

Solution

This PR adds the foundational server-side API enhancement required by all proposed solutions. The implementation is minimal (8 lines of core logic) and non-breaking:

Core changes:

  • packages/opencode/src/session/index.ts - Add params to Session.messages() schema and iteration logic
  • packages/opencode/src/server/routes/session.ts - Expose params in HTTP API

Why this approach:

  • Timestamp-based anchoring uses immutable reference points, eliminating state management complexity and race conditions that offset-based pagination would introduce
  • Breakpoint support enables "load conversation history" (stop at compaction) vs "load full session" (ignore compactions) use cases
  • Zero breaking changes - all parameters optional, existing functionality unchanged
  • Prerequisite for all solutions - whether TUI, web client, or SDK consumers implement history loading, they all need this server capability

Usage

# Get messages before a timestamp
GET /session/{id}/message?ts_before=1768609939954

# Get messages before timestamp, stopping at first compaction
GET /session/{id}/message?ts_before=1768609939954&breakpoint=true

# Combine with limit
GET /session/{id}/message?ts_before=1768609939954&limit=50

Testing

Verified against sessions with 170+ messages and multiple compactions:

  • ts_before correctly filters to messages older than timestamp
  • breakpoint=true stops at first compaction part
  • Combined parameters work together
  • Existing behavior unchanged when params omitted
**Original Pull Request:** https://github.com/anomalyco/opencode/pull/8996 **State:** open **Merged:** No --- ## Summary Adds two optional parameters to `Session.messages()` API for loading messages older than the initial 100-message window: - **`ts_before`**: Unix timestamp - returns messages created before this point - **`breakpoint`**: Boolean - when true, stops at the first compaction summary ## Problem Multiple open issues request the ability to access message history beyond the initial 100-message limit: - Resolves #6137 - Cannot scroll to beginning of long conversations - Resolves #4918 - Feature request: pagination for messages & sessions - Resolves #7380 - Old messages disappear - Related #6548 - Pagination work Current `Session.messages()` only supports a `limit` parameter, which returns the N most recent messages. There is no way to retrieve older messages. ## Solution This PR adds the foundational server-side API enhancement required by all proposed solutions. The implementation is minimal (8 lines of core logic) and non-breaking: **Core changes:** - `packages/opencode/src/session/index.ts` - Add params to `Session.messages()` schema and iteration logic - `packages/opencode/src/server/routes/session.ts` - Expose params in HTTP API **Why this approach:** - **Timestamp-based anchoring** uses immutable reference points, eliminating state management complexity and race conditions that offset-based pagination would introduce - **Breakpoint support** enables "load conversation history" (stop at compaction) vs "load full session" (ignore compactions) use cases - **Zero breaking changes** - all parameters optional, existing functionality unchanged - **Prerequisite for all solutions** - whether TUI, web client, or SDK consumers implement history loading, they all need this server capability ## Usage ```bash # Get messages before a timestamp GET /session/{id}/message?ts_before=1768609939954 # Get messages before timestamp, stopping at first compaction GET /session/{id}/message?ts_before=1768609939954&breakpoint=true # Combine with limit GET /session/{id}/message?ts_before=1768609939954&limit=50 ``` ## Testing Verified against sessions with 170+ messages and multiple compactions: - `ts_before` correctly filters to messages older than timestamp - `breakpoint=true` stops at first compaction part - Combined parameters work together - Existing behavior unchanged when params omitted
yindo added the pull-request label 2026-02-16 18:17:49 -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#12943
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?