[Bug] Mini window: Permission request cards duplicated and no visual feedback after approval

Open 💬 1 comment Opened Apr 20, 2026 by lis-soft

What version of the Codex App are you using (From “About Codex” dialog)?

Latest (unknown exact version)

What subscription do you have?

ChatGPT Plus / Pro

What platform is your computer?

macOS

What issue are you seeing?

In the Codex mini window, when an agent requests a permission (e.g., tool use / MCP tool execution), the permission request card is duplicated and shown multiple times in the conversation. Additionally, after clicking "Allow" to approve the request, the card's appearance does not change — there is no visual feedback indicating whether the approval was successful. This makes it very confusing: users cannot tell if they actually approved the action or not.

What steps can reproduce the bug?

  1. Open Codex in mini window mode.
  2. 2. Start a task that involves tool usage or MCP tool execution requiring permission confirmation.
  3. 3. Observe the permission request card in the mini window — it appears duplicated (shown multiple times).
  4. 4. Click the "Allow" button on the permission request card.
  5. 5. Observe the card after clicking — it stays in the same visual state as before clicking.

What is the expected behavior?

  1. Each permission request card should appear only ONCE in the conversation — no duplicates.
  2. 2. After clicking "Allow", the card should visually update to reflect the approved state (e.g., change color, show a checkmark, display "Approved" text, or collapse/disappear). Users need clear confirmation that their action was registered.

Additional information

This issue was observed while using MCP tools within Codex. The mini window shows the permission/approval request card multiple times in a single session. Even after approving, the card UI does not update, leading to user confusion about whether the permission was granted. A screenshot has been attached showing the duplicated cards in the mini window.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗