macOS app: Voice message is posted to the wrong thread if user switches threads while transcription is processing
Resolved 💬 1 comment Opened Feb 20, 2026 by diasflack Closed Feb 20, 2026
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.217.1959 (669)
What subscription do you have?
Pro
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
In the Codex macOS app, when using voice input, after pressing "Send" on a voice message (while transcription/processing is still in progress), switching to another thread causes the final recognized message to be posted to the currently active thread instead of the original one.
This results in messages appearing in the wrong conversation.
What steps can reproduce the bug?
- Open Thread A
- Record a voice message
- Press "Send"
- While transcription/processing is still ongoing, switch to Thread B
- Wait for processing to complete
What is the expected behavior?
The message should remain attached to Thread A (where it was recorded and sent), regardless of UI navigation.
Additional information
This appears to be a context binding issue where the voice message processing result is not strictly associated with the originating thread.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗