Codex last_assistant_message is parsed then discarded on Stop/SubagentStop
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 475
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 178
Description
Summary
stopRaw and subagentStopRaw declare LastAssistantMessage, and fixtures pass it, but parseTurnEnd / parseSubagentStop never copy it onto agent.Event (e.g. TaskDescription).
Impact
End-of-turn / subagent summaries Codex already sends are unused; other agents (Cursor, Droid) wire analogous fields into TaskDescription.
Expected
Map last_assistant_message into Event.TaskDescription (or equivalent) when non-empty.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the stopRaw and subagentStopRaw definitions, then trace parseTurnEnd and parseSubagentStop to see how they populate agent.Event. Compare the existing fixtures and analogous Cursor or Droid handling; done means a non-empty last_assistant_message appears in Event.TaskDescription for both stop paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100