What version of the Codex App are you using?
- Codex Desktop on Windows
- App package:
OpenAI.Codex 26.715.8383.0
- Bundled runtime:
codex-cli 0.145.0-alpha.27
What subscription do you have?
ChatGPT paid account.
What platform is your computer?
Windows x64.
What issue are you seeing?
The Subagents panel shows Active and Done child agents. I cannot open a child agent as an interactive chat or send it a direct follow-up.
This workflow worked in an earlier Codex Desktop build. I could open the subagent thread and continue talking with that agent while it retained its delegated context.
Current behavior:
- An active child remains shown as “thinking”.
- Completed children appear under Done.
- Selecting the child fails to provide a writable child conversation.
- Starting another child only produces another Active/Done entry with the same limitation.
- The parent can relay a message through collaboration tools, which adds an extra parent turn and removes the direct user-to-child workflow.
This affects long test reviews where a specialist subagent holds the complete review context and the user needs to question that same agent directly.
What steps can reproduce the issue?
- Open a task in Codex Desktop.
- Ask the parent agent to create a subagent for a long-running review.
- Open the Subagents panel.
- Select the active child entry and try to open its chat.
- Try to send the child a direct question.
- Repeat after the child completes and appears under Done.
What is the expected behavior?
Selecting an active or completed subagent should open its child thread.
- An active child should accept direct steering.
- An idle or completed child should accept a follow-up turn.
- The child transcript and delegated context should remain available.
- The parent task should remain the default task when the user returns to it.
Additional information
This appears related to the MultiAgentV2 direct-input policy:
Issue #33885 documents the app-server error direct app-server input is not allowed for multi-agent v2 sub-agents and the read-only child-thread policy. This report covers the Codex Desktop experience: the Subagents panel still presents child entries while the previous direct-chat workflow is unavailable.
Known-good legacy comparison
Local rollout metadata confirms the earlier writable workflow:
- A Codex Desktop task created on 2nd Jul 2026 used
codex-cli 0.142.5 with multi_agent_version: v1.
- Retained Desktop logs map Windows package
OpenAI.Codex 26.623.19656.0 directly to bundled codex-cli 0.142.5.
- A fresh user-owned root task created on 8th Jul 2026 under that package resolved to
multi_agent_version: v1; its spawned children also resolved to V1.
- Its children were stored as durable
thread_source: subagent / thread_spawn threads with parent IDs and agent roles.
- A child rollout contains a direct
user_message event and the child agent's reply, confirming direct user-to-child chat.
- A resumed legacy V1 parent still spawned V1 children under
codex-cli 0.145.0-alpha.18 on 20th Jul 2026.
- Newly created tasks in the current Desktop build use MultiAgentV2 and appear in the read-only Active/Done panel.
This identifies the V1-to-V2 workflow change as the compatibility boundary.
Verified release boundary
The locally observed Desktop package 26.715.7063.0 bundled 0.145.0-alpha.18. That build predates the later read-only UI layer and still contains the earlier MultiAgentV2 app-server rejection.
The current Desktop frontend accepts the CODEX_CLI_PATH environment override. Its packaged application code also declares 0.141.0 as the minimum supported app-server version and rejects older runtimes with codex-app-server-version-unsupported. This prevents current Desktop package 26.715.8383.0 from using the fully pre-rejection CLI target 0.139.0 as a simple override.
Public issues #28094 and #28348 map the About build 26.609.41114 to Windows package OpenAI.Codex 26.609.4994.0 with CLI 0.139.0. This is the strongest public mapping for a fully pre-#27173 Desktop stack. Public issue #27175 also reports Desktop 26.602.71036 with CLI 0.138.0 and stability problems in that package. An official historical MSIX download is currently unavailable through the published stable installer URL or Microsoft Store version listing.
The strongest locally verified Desktop rollback target for restoring the former writable-child workflow is therefore OpenAI.Codex 26.623.19656.0. A signed historical installer for this exact package remains required.
What version of the Codex App are you using?
OpenAI.Codex 26.715.8383.0codex-cli 0.145.0-alpha.27What subscription do you have?
ChatGPT paid account.
What platform is your computer?
Windows x64.
What issue are you seeing?
The Subagents panel shows Active and Done child agents. I cannot open a child agent as an interactive chat or send it a direct follow-up.
This workflow worked in an earlier Codex Desktop build. I could open the subagent thread and continue talking with that agent while it retained its delegated context.
Current behavior:
This affects long test reviews where a specialist subagent holds the complete review context and the user needs to question that same agent directly.
What steps can reproduce the issue?
What is the expected behavior?
Selecting an active or completed subagent should open its child thread.
Additional information
This appears related to the MultiAgentV2 direct-input policy:
Issue #33885 documents the app-server error
direct app-server input is not allowed for multi-agent v2 sub-agentsand the read-only child-thread policy. This report covers the Codex Desktop experience: the Subagents panel still presents child entries while the previous direct-chat workflow is unavailable.Known-good legacy comparison
Local rollout metadata confirms the earlier writable workflow:
codex-cli 0.142.5withmulti_agent_version: v1.OpenAI.Codex 26.623.19656.0directly to bundledcodex-cli 0.142.5.multi_agent_version: v1; its spawned children also resolved to V1.thread_source: subagent/thread_spawnthreads with parent IDs and agent roles.user_messageevent and the child agent's reply, confirming direct user-to-child chat.codex-cli 0.145.0-alpha.18on 20th Jul 2026.This identifies the V1-to-V2 workflow change as the compatibility boundary.
Verified release boundary
1026e9de1be292ebb01579dfcce5a34ab224917ais absent from stable0.139.0.0.140.0-alpha.2and is included in stable0.140.0.0.139.0is therefore the strongest verified CLI rollback target for removing the app-server rejection itself.0.145.0-alpha.22and is included in stable0.145.0.The locally observed Desktop package
26.715.7063.0bundled0.145.0-alpha.18. That build predates the later read-only UI layer and still contains the earlier MultiAgentV2 app-server rejection.The current Desktop frontend accepts the
CODEX_CLI_PATHenvironment override. Its packaged application code also declares0.141.0as the minimum supported app-server version and rejects older runtimes withcodex-app-server-version-unsupported. This prevents current Desktop package26.715.8383.0from using the fully pre-rejection CLI target0.139.0as a simple override.Public issues #28094 and #28348 map the About build
26.609.41114to Windows packageOpenAI.Codex 26.609.4994.0with CLI0.139.0. This is the strongest public mapping for a fully pre-#27173 Desktop stack. Public issue #27175 also reports Desktop26.602.71036with CLI0.138.0and stability problems in that package. An official historical MSIX download is currently unavailable through the published stable installer URL or Microsoft Store version listing.The strongest locally verified Desktop rollback target for restoring the former writable-child workflow is therefore
OpenAI.Codex 26.623.19656.0. A signed historical installer for this exact package remains required.