fix: add timestamp field to message types - #1183
Open
SushantTusharJoshi wants to merge 1 commit into
Open
Conversation
The JSONL transcript file includes a `timestamp` field on each message, but the SDK message types (UserMessage, AssistantMessage, SystemMessage) were not exposing it. This adds an optional `timestamp: str | None` field to all three base message types and wires it through the message parser. Closes anthropics#258 Developed with Claude Code as a coding partner
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
1 participant
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
timestampfield toUserMessage,AssistantMessage, andSystemMessagedataclassesmessage_parser.pyto populate timestamps from JSONL data for all message typeskw_only=TrueonSystemMessage.timestampto avoid dataclass inheritance issues with subclassesTest plan
Closes #258
Developed with Claude Code as a coding partner