# Codex IDE plugin silently eats messages

**URL:** <https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586>\
**Category:** Bugs\
**Tags:** codex\
**Created:** [October 1, 2026, 2:47pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586 "2026-10-01T14:47:45Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marcio\_Galli](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/marcio_galli/32/726530_2.png) [@Marcio\_Galli](https://community.openai.com/u/Marcio_Galli)\
**Post date:** [October 1, 2026, 2:47pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/1 "2026-10-01T14:47:45Z")

</div>

This happens a lot, more or less, over time. Let me know if you need me to dig the specific Codex IDE plugin version, and how to do it. Anyway, the patter is:

After user types in the text field, at the bottom, this Codex chat plugin ‘eats’ the message, it does not move it as a real pending message to the queue.

---

<div class="post-metadata">

**Author:** ![Marcio\_Galli](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/marcio_galli/32/726530_2.png) [@Marcio\_Galli](https://community.openai.com/u/Marcio_Galli)\
**Post date:** [October 1, 2026, 2:58pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/2 "2026-10-01T14:58:39Z")

</div>

![image](https://us1.discourse-cdn.com/openai1/original/4X/b/2/5/b2553d70d27a9bdab1c844305d90cb3b29e00414.png)there are multiple outputs the user may see after the problem happens. Here is an example of one possible.

---

<div class="post-metadata">

**Author:** ![Marcio\_Galli](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/marcio_galli/32/726530_2.png) [@Marcio\_Galli](https://community.openai.com/u/Marcio_Galli)\
**Post date:** [October 1, 2026, 3:32pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/3 "2026-10-01T15:32:03Z")

</div>

A test: I tried to copy/paste a richer text from ChatGPT, into the Codex, and then saw the problem, ate/silence.

Then instead, I pasted in the browser urlbar, recopied, and pasted in the chat, and it went through. Could perhaps that be about some characters causing the bug?

---

<div class="post-metadata">

**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\
**Post date:** [October 1, 2026, 3:32pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/4 "2026-10-01T15:32:33Z")

</div>

Welcome to the forum!

You posted this in the appropriate place on the forum for discussing and documenting a Codex bug. The forum, however, is not the official issue tracker. If the problem needs to be formally reported and tracked by the Codex maintainers, the official place is the [OpenAI Codex GitHub issue tracker](https://github.com/openai/codex/issues).

Please follow the posting requirements for the **Codex Bugs** subcategory:

> [@Read this before you post in the Codex Bugs category](https://community.openai.com/t/read-this-before-you-post-in-the-codex-bugs-category/1396098):
>
> Report reproducible bugs in the Codex CLI, IDE extension, app, or web experience. Include your Codex version, environment, steps to reproduce, and expected versus actual behavior. Provide a [minimal reproducible example](https://en.wikipedia.org/wiki/Minimal_reproducible_example) where possible. Model hallucinations or differences in generated output alone are not considered bugs for this category. Keep each topic focused on one bug. Use the main Codex category for discussions and Feature Requests for proposed improvements. When a fix is available, con…

I asked ChatGPT to search for the closest related issue, and it identified:

> <https://github.com/openai/codex/issues/26683>
>
> \### What version of the IDE extension are you using?
> 
> 26.602.40724
> 
> \### What sub…scription do you have?
> 
> ChatGPT Pro
> 
> \### Which IDE are you using?
> 
> VS Code
> 
> \### What platform is your computer?
> 
> Microsoft Windows NT 10.0.26200.0 x64
> 
> \### What issue are you seeing?
> 
> \### 1. Queued messages disappear or are not acted on
> 
> When Codex is already working on a task and I send an additional message, the follow up is not handled reliably.
> 
> Observed behaviour:
> 
> \- Sometimes the message disappears after being sent.
> \- Sometimes the message appears in the queue/cube, but Codex does not automatically continue with it after the current task finishes.
> \- The queued message can remain visible in the UI but is not acted on.
> 
> \### 2. Codex shows a thinking state but never starts the task
> 
> Sometimes Codex only shows the thinking state and no task actually begins.
> 
> Observed behaviour:
> 
> \- I send a message.
> \- Codex displays that it is thinking.
> \- No task or mission starts.
> \- No useful response is returned.
> \- No clear error message is shown.
> \- The only reliable recovery is restarting Codex.
> 
> This is misleading because the UI suggests Codex is working, but in practice no progress is made.
> 
> \### What steps can reproduce the bug?
> 
> I cannot reproduce this with a single deterministic code snippet because it appears to be an extension and runtime issue. However, I have reproduced it repeatedly with this workflow:
> 
> 1. Open a repository in VS Code.
> 2. Start a Codex task.
> 3. While Codex is working, send an additional message as follow up guidance.
> 4. Observe that the message may disappear, remain stuck in the queue/cube, or not auto start after the current task finishes.
> 5. In some cases, send a new message and observe that Codex shows the thinking state but never actually starts a task.
> 6. Restart Codex to recover.
> 
> The issue has occurred across five different internet connections in five different physical locations, so it does not appear to be caused by local network instability.
> 
> \### What is the expected behavior?
> 
> \- Follow up messages sent while Codex is working should not disappear.
> \- Queued messages should remain visible and should be acted on after the current task finishes.
> \- If a queued message is intended as guidance for the active task, Codex should incorporate it as soon as possible.
> \- If Codex cannot start a task, it should show a clear error message.
> \- Codex should not remain indefinitely in a thinking state without starting a task or returning a response.
> \- Restarting the entire Codex extension should not be required to recover from this state.
> 
> \### Additional information
> 
> Approximate start of issue: 3rd June 2026

If that issue describes the same problem you are experiencing, consider adding a 👍 reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.

If it does not match your problem closely enough, search the [existing Codex issues](https://github.com/openai/codex/issues) for a better match. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.

---

<div class="post-metadata">

**Author:** ![Marcio\_Galli](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/marcio_galli/32/726530_2.png) [@Marcio\_Galli](https://community.openai.com/u/Marcio_Galli)\
**Post date:** [October 1, 2026, 3:53pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/5 "2026-10-01T15:53:10Z")

</div>

This bridge between here and there, it’s amazing, thanks. Exactly because all bugs in the world carry on a strong relationship with use cases. I do see, this thread, therefore, as somewhat valid.

---

<div class="post-metadata">

**Author:** ![Marcio\_Galli](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/marcio_galli/32/726530_2.png) [@Marcio\_Galli](https://community.openai.com/u/Marcio_Galli)\
**Post date:** [October 1, 2026, 3:54pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/6 "2026-10-01T15:54:25Z")

</div>

A note, though, it’s not stuck with thinking. I saw about 5 different things happening related to what I referred as “eating”.

---

<div class="post-metadata">

**Author:** ![ntx](https://avatars.discourse-cdn.com/v4/letter/n/77aa72/32.png) [@ntx](https://community.openai.com/u/ntx)\
**Post date:** [October 2, 2026, 1:28pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/7 "2026-10-02T13:28:03Z")

</div>

i have the same problem, it’s so frustrating and time wasting

---

<div class="post-metadata">

**Author:** ![Marcio\_Galli](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/marcio_galli/32/726530_2.png) [@Marcio\_Galli](https://community.openai.com/u/Marcio_Galli)\
**Post date:** [October 2, 2026, 2:41pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/8 "2026-10-02T14:41:02Z")

</div>

A few months ago, I tried to open the plugin code in the Codex to fix, and apparently I fixed but then i realized it didn’t . I will see now, what Sol 6.1 can do for us. Let us see, if I find something meaningful I ping here.

---

<div class="post-metadata">

**Author:** ![Marcio\_Galli](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/marcio_galli/32/726530_2.png) [@Marcio\_Galli](https://community.openai.com/u/Marcio_Galli)\
**Post date:** [October 8, 2026, 5:38pm UTC](https://community.openai.com/t/codex-ide-plugin-silently-eats-messages/1402586/9 "2026-10-08T17:38:04Z")

</div>

For me started to work a few days ago. Let us see.
