agents: support bounded replay and backward history paging on /stream - #706
Merged
Conversation
harness-api now caps a cursorless /stream attach to its replay budget instead of replaying a session's entire event history, and exposes older history through the same endpoint via before/limit (cthulhu #169570). Without this, clients can only ever see the newest slice of a long-lived session, with no way to reach the rest. Adds before/limit to sessions.stream() on both the sync and async clients, forcing replay_only when before is set because the server rejects the combination otherwise, and a history_page() helper that drains one page and returns the events, has_more, and the cursor for the next page back. has_more arrives as a trailing SSE comment, which SSEStream/AsyncSSEStream previously dropped along with every other comment frame, so they now record it while continuing to ignore banners like ": connected to <session_id>". Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
LGTM |
SSharma-10
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
harness-api now caps a cursorless /stream attach to its replay budget instead of replaying a session's entire event history, and exposes older history through the same endpoint via before/limit (cthulhu #169570). Without this, clients can only ever see the newest slice of a long-lived session, with no way to reach the rest.
Adds before/limit to sessions.stream() on both the sync and async clients, forcing replay_only when before is set because the server rejects the combination otherwise, and a history_page() helper that drains one page and returns the events, has_more, and the cursor for the next page back.
has_more arrives as a trailing SSE comment, which SSEStream/AsyncSSEStream previously dropped along with every other comment frame, so they now record it while continuing to ignore banners like ": connected to <session_id>".