feat(sensor): capture Codex token usage - #86
Draft
barisozbas wants to merge 1 commit into
Draft
Conversation
Summary: Intent: - Preserve token accounting emitted by Codex sessions. - Extend AgentEvent without breaking positional construction. Changes: - Aggregate current and legacy token-count event shapes. - Store token usage as an optional backward-compatible event field.
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
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.
What changed
Codex token accounting is now retained on
AgentEvent.Why
Token usage is useful for cost and activity analysis but was previously discarded during normalization. The schema addition remains optional so existing consumers continue to work unchanged.
Validation
pytest -q Sensor/testsruff check Sensor/adr_sensor/parsers/codex_parser.py Sensor/adr_sensor/schemas/agent_event_schema.py Sensor/tests/test_parsers.py Sensor/tests/test_schemas.py