openai / openai/codex

[Bug] Subagent task messages never delivered to spawned agents; agents idle or act on inherited context (Windows desktop app)

Open
#40,069 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug subagent windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.818.3698.0 (package: OpenAI.Codex_26.818.3698.0_x64__2p2nqsd0c76g0)【需你确认:请以 About Codex 对话框显示为准,如有差异替换】

What subscription do you have?

其他

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

Spawned subagents never receive the task text passed via spawn_agent or followup_task. They either complete an onboarding turn and reply "waiting for task", or act only on the context inherited from the parent thread (recursively spawning their own subagents and running unrelated demos). A verbatim quote-back test failed: the agent did not repeat the given message and instead spawned more subagents. Observed in two independent conversations; symptom in the other chat was "subagent invoked but just watching/idle". No error message is shown.

What steps can reproduce the bug?

Feedback ID: 01a025b0-87c5-72a0-ab34-d0e3e2858267

What is the expected behavior?

Per official docs (https://developers.openai.com/codex/subagents), a spawned agent should receive the task text in its own thread and execute it, and its result should return to the parent. Actual behavior: the task text never appears in the agent's visible conversation; agents idle or act on inherited context.

Additional information

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the subagent documentation and reproduce the issue using Feedback ID 01a025b0-87c5-72a0-ab34-d0e3e2858267. Trace the spawn_agent and followup_task message-delivery entry points in the Windows desktop app; done means spawned agents receive the task text and return their results to the parent instead of idling or using inherited context.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.