Codex desktop: update_plan unavailable and no replacement exposed
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.901.51231
What subscription do you have?
Pro
What platform is your computer?
macOS 26.6.2 (25G83), Apple Silicon Darwin 25.6.0 arm64 arm
What issue are you seeing?
The assistant cannot update the native task-progress plan because update_plan is unavailable in its exposed tool set.
Searching the available tool registry found neither update_plan nor an equivalent planning/progress API. Checking typeof tools.update_plan returned "undefined".
The assistant falls back to textual progress updates. No failed update_plan invocation or UI error was observed.
What steps can reproduce the bug?
Fresh-session reproduction has not been verified. To check the behavior observed in the affected desktop task:
- In a local task using Default mode, ask: "Show a native task-progress plan with two steps."
- If the assistant reports that update_plan is unavailable, ask it to inspect the exposed tools for alternative planning/progress APIs.
- Observe whether the assistant finds an applicable API or falls back to textual progress updates.
The absence was observed in the original task and checked again in a side conversation.
Feedback ID: 01a07dea-f90e-7ed1-9bab-627a7a23fb8f
Token limit usage: Not recorded.
Context window usage: Not recorded.
What is the expected behavior?
The assistant can create and update the native task-progress plan through update_plan or a documented replacement. If this surface intentionally does not support it, that limitation should be explicit.
Additional information
Observed on September 7, 2026.
A locally installed show-task-progress skill still instructs the assistant to call update_plan. This does not establish whether the tool is currently supported.
Restart behavior and reproduction in an unrelated fresh task have not been tested. A regression or API rename has not been established.
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 by reproducing the behavior in a fresh Codex desktop Default-mode task and inspect the exposed tool registry for update_plan or a replacement. The issue is done when native task-progress updates work through an available API, or the unsupported surface is explicitly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100