Voice requests to start or update work repeatedly fail to reach the task coordinator, while the same requests sent in written chat succeed.
Environment
- ChatGPT/Codex desktop app on Windows and ChatGPT Android app.
- Observed October 5–6, 2026.
- Exact app versions can be supplied if needed.
Steps observed
- Start a voice call with an existing dot.
- Request a new task, an update to ongoing work, or a read-only document check.
- The assistant attempts to hand off the request.
- The handoff returns the error below.
- A retry repeatedly returns the same error.
- Sending the request in written chat successfully reaches the coordinator.
Exact error
“Not sent. The spoken context could not be confirmed yet; you may retry this tool. If it remains pending, wait for a later turn. Do not use another route to main.”
Error code: voice_parent_context_pending
Tool status: UNAVAILABLE
Expected
Spoken task requests should reach the coordinator, or the app should show an actionable failure state and supported recovery steps.
Actual
Voice conversation continues and written messages can be delivered, but spoken work requests fail to reach the coordinator. The problem affects read-only requests as well as already-authorized actions.
Troubleshooting attempted
- Ended and restarted voice calls.
- Restarted both desktop and mobile apps.
- Retried failed handoffs once.
The failure persisted after these steps.
Impact
Requests and corrections must be repeated in text, and users must manually check whether work actually started. This prevents reliable coordination through voice.
A separate symptom is that some calls stop responding after the assistant says it is checking something. It is not established whether these failures share a cause.
Please investigate why spoken context remains unconfirmed and provide a supported recovery path. This report does not request bypassing approval checks.