[ChatGPT Web][Windows/Chrome] Backspace on an @ plugin mention can make the chat/composer disappear
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
On ChatGPT Web (chatgpt.com), the conversation/composer can disappear or reset when Backspace is used while editing or removing an @ plugin/skill mention.
The strongest reproduction is after a plugin prompt has already completed: start the next prompt, invoke the @ picker again, select or begin editing a plugin/skill mention, then press Backspace. The chat/composer UI can disappear unexpectedly.
Normal typing by itself is not the main trigger. The issue appears tied to the @ mention/autocomplete/token state plus Backspace.
Steps to reproduce
- Open an existing conversation on ChatGPT Web.
- Click the message composer.
- Type
@and select a plugin/skill from the picker. - Submit the prompt and wait for the response/plugin execution to finish.
- Click the composer to start the next prompt.
- Type
@again and select or partially select a plugin/skill mention. - Press Backspace to edit/remove the mention or text around it.
- The composer/chat UI may disappear, reset, or collapse.
- Repeating the
@-> plugin selection -> Backspace sequence reproduces the problem.
Expected behavior
Backspace should delete text or remove the selected @ mention normally. The composer should stay mounted and focused, and the conversation should remain visible.
A completed prior plugin invocation should not leave stale composer/mention state that affects the next prompt.
Actual behavior
Pressing Backspace while editing/removing an @ plugin/skill mention can destabilize the composer and cause the chat/composer UI to disappear or reset, interrupting message composition.
Environment
- Product: ChatGPT Web (
chatgpt.com) - OS: Windows 10
- Browser: Google Chrome 152
- Device: Desktop
- Observed: 2026-09-10
Frequency
The issue is repeatedly reproducible around the @ plugin/skill mention flow, especially after a previous plugin prompt has completed.
Public reproduction/reference
I created a public issue with the same reproduction details here:
https://github.com/zrt219/chatbot/issues/1
A screen recording was also captured showing the failure being reproduced.
Notes for investigation
The failure may be around the rich composer mention lifecycle rather than normal text input. Useful areas to inspect would be mention-token deletion, autocomplete teardown, stale state after a completed plugin turn, keyboard/input event handling, focus restoration, or an unexpected composer unmount/remount.
This report is for ChatGPT Web, not the Codex CLI.
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
The report identifies ChatGPT Web rather than the Codex CLI and names no repository files, tests, or entry points. Confirm that the issue belongs in this repository before looking for an applicable frontend component; done would require a reproducible fix that keeps the composer and conversation visible during the described Backspace flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100