Feat/message timestamp #259
Open
Conversation
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
- Add optional timestamp field to UserMessage, AssistantMessage, SystemMessage, ResultMessage, StreamEvent - Update message parser to pass timestamp from CLI data - Fix parser bug in user message handling - Add changelog entry for v0.1.4
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.
This addresses issue #258
The timestamp field supports timeline displays and message ordering
All message types now have optional
timestamp: int | str | NonefieldThe parser automatically populates timestamps from CLI transcript data
Other changes are done by ruff linter