Ahmed Ibrahim 13e1d0362d Delegate review to codex instance (#5572) ...

In this PR, I am exploring migrating task kind to an invocation of
Codex. The main reason would be getting rid off multiple
`ConversationHistory` state and streamlining our context/history
management.

This approach depends on opening a channel between the sub-codex and
codex. This channel is responsible for forwarding `interactive`
(`approvals`) and `non-interactive` events. The `task` is responsible
for handling those events.

This opens the door for implementing `codex as a tool`, replacing
`compact` and `review`, and potentially subagents.

One consideration is this code is very similar to `app-server` specially
in the approval part. If in the future we wanted an interactive
`sub-codex` we should consider using `codex-mcp`

13e1d0362d · 2025-10-29 21:04:25 +00:00

History

..

exit_interrupted.xml

Delegate review to codex instance (#5572)

2025-10-29 21:04:25 +00:00

exit_success.xml

Delegate review to codex instance (#5572)

2025-10-29 21:04:25 +00:00

history_message_completed.md

Delegate review to codex instance (#5572)

2025-10-29 21:04:25 +00:00

history_message_interrupted.md

Delegate review to codex instance (#5572)

2025-10-29 21:04:25 +00:00