fix(agent-manager): parse current Codex session messages - #149
Merged
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
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.
Summary
response_itemmessage records in agent detail conversations.AgentMessageevent records from current Codex JSONL logs as fallback.response_item/event_msgrecords inagent detail, preferring canonicalresponse_itemmessages.agent listsummaries and status classification.payload.messageparsing intact.Validation
npm run test -- CodexAdapter.test.tsfrompackages/agent-manager: 66 passed.npm run typecheckfrompackages/agent-manager: passed.npm run lintfrompackages/agent-manager: passed.npm run testfrompackages/agent-managerwith process access: 502 passed.nx run-many -t lintandnx run-many -t test: passed.Risks
response_item; mirrored records with a matching turn/role/content are skipped to avoid duplicate detail output.