Restore context#
Confirm that Codex is running and that the selected conversation exists in the expected environment. Open the original task rather than a similarly named one. Recheck CueSpec’s current status and conversation identity.
If the failure clearly occurred before submission, the draft can be reviewed for another deliberate attempt after recovery. If submission is uncertain, inspect the conversation for receipt first.
Keep version information#
The development history includes a host-availability failure and later compatibility work. A read-only connection succeeding does not itself prove that the reply path succeeds. Use a small non-sensitive reply to verify the actual route once the environment is ready.
Do not delete local history, reset account data or create duplicate tasks as the first response. A useful report includes CueSpec and Codex versions, the visible availability message and whether the original task could be opened. This is a conversation-delivery issue, separate from microphone capture.