Error creating chat MessaagePort connection
Nobody has claimed this yet.
- 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.9
What subscription do you have?
Pro
What platform is your computer?
uname -mprs
What issue are you seeing?
I’m experiencing a recurring “MessagePort connection” error in the Codex desktop app on macOS.
Recent messages in a long-running conversation fail to load or appear in the chat. The assistant seems to retain context from those exchanges, but I cannot reliably see the latest messages or responses.
I have already tried:
Closing and reopening the app.
Uninstalling and reinstalling the app.
The problem persists after both steps.
This conversation contains extensive project work, design approvals, and references to locally saved files. I’m concerned about losing access to the conversation history and would like to troubleshoot this without deleting local app data or project files.
Could you help identify the cause and restore reliable loading of the conversation? Please let me know which diagnostic logs or app version details you need.
What steps can reproduce the bug?
Feedback ID: 01a03f2b-f292-7f61-9964-6ec06ff01cc8
What is the expected behavior?
No response
Additional information
No response
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
No source files, tests, or entry points are named. Start by reviewing the issue details and Feedback ID 01a03f2b-f292-7f61-9964-6ec06ff01cc8, then inspect the available diagnostic logs for the MessagePort error. Done means identifying the cause and restoring reliable loading of recent conversation messages without deleting local app or project data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100