Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 0
Read Agent SDK session records, and surface ones that cannot render#133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Changes from all commits
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The undisplayed count treats records the SDK reader is silent on by design as drops, so healthy sessions get the "this CLI may be out of date" footer; only
record_type === 'system'is excluded, buteventToItemsalso returns [] forkind: 'rate_limit'(part of the persisted claude_sdk@1 union) andcodexEventToItemsreturns [] for every codex frame except item.completed/error/turn.failed.Verified against the installed 0.15.0 by calling reshapeTranscript directly: a
rate_limitrecord yields {items: [], undisplayed: 1}, and a normal six-record codex turn (thread.started, turn.started, item.started, item.updated, item.completed, turn.completed) yields one rendered row and undisplayed: 5. Sinceagent session connectdoes not filter by harness and the platform persists every Codexexec --jsonThreadEvent verbatim (source=codex, codex_jsonl@1), connecting to a codex session shows e.g. "37 events could not be displayed, this CLI may be out of date" while rendering the transcript correctly — and because the warning takes the whole meta line and only clears on a send, a watch-only or closed session (canSend false, --no-input) loses status/spend/session id for the rest of the run.