Skip to content

fix(codex): follow subagent status under the app-server's new notification name - #703

Merged
moreih29 merged 1 commit into
developfrom
fix/codex-thread-status
Nov 19, 2026
Merged

moreih29 merged 1 commit into
developfrom
fix/codex-thread-status

Conversation

@moreih29

Copy link
Copy Markdown
Owner

Summary

Codex's app-server renamed the thread/statusChanged notification to thread/status/changed (the official 0.166.0 schema and the installed 0.170.0 both use the new name, with the same params). The app only matched the old name, so a Codex subagent going idle or hitting a system error was missed: its row did not settle from that notification and the tab did not reread its subagents. bun run check:agent-commands failed on develop for the same reason.

  • One check, isThreadStatusChanged, takes both names (older Codex and older logs keep working), used by the model and the controller.
  • check-agent-commands registers the current name. No other notification the app reads was renamed.

Tests

  • Codex model table: the new name updates a subagent's status.
  • bun run typecheck, bun run check:ci, bun run check:agent-commands, related tests (146).

🤖 Generated with Claude Code

@moreih29
moreih29 merged commit b9793de into develop Nov 19, 2026
7 checks passed
@moreih29
moreih29 deleted the fix/codex-thread-status branch November 19, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant