[ChatGPT Web][Sep 2026 UI] Conversation workflow regressions: native links/new-tab behavior removed and direct Delete action lost

Summary

The recent ChatGPT web UI update introduced several related conversation-navigation and lifecycle regressions on chatgpt.com.

These are not requests for new advanced features. They are previously available browser/UI workflows that disappeared with the new interface.

The regressions I can reproduce are:

1. “New chat” no longer behaves like a normal browser link.
2. Existing conversation entries no longer behave like normal browser links.
3. As a consequence, standard browser actions are lost:
   • Right-click → Open link in new tab
   • Ctrl+Click
   • Middle-click
   • Copy link address
4. Delete has been removed from the menu of the currently open conversation, forcing the user to find the same conversation again in the sidebar/search before it can be deleted.

These changes all move conversation management away from direct/native browser interaction and toward extra sidebar/search navigation.

Environment

• Surface: chatgpt.com
• OS: Windows 11
• Browser: Microsoft Edge
• First observed: immediately after the September 25, 2026 ChatGPT web UI update
• Reproduced again on September 27, 2026

Regression 1 — New chat can no longer be opened directly in a new tab

Previously, “New chat” behaved like a link.

Expected browser workflows included:

• Right-click → Open link in new tab
• Ctrl+Click
• Middle-click

With the current UI, right-clicking “New chat” produces the generic page context menu rather than a link context menu.

This means a user who wants to preserve the current conversation and start another one in parallel now has to:

open another browser tab
→ navigate to ChatGPT
→ start a new chat there

instead of simply opening “New chat” in another tab.

Regression 2 — Existing conversations no longer preserve native link behavior

The same problem affects conversation entries.

When conversation entries are not real links, standard browser navigation is lost:

• no native Open in new tab
• no Ctrl+Click
• no middle-click
• no Copy link address

This is especially disruptive for workflows where several conversations are used in parallel and compared against each other.

Regression 3 — Browser-native context-menu functionality has been removed

The practical issue is not only the absence of an explicit “Open in new tab” button.

The new UI removes normal browser link semantics entirely.

That means the browser can no longer provide functionality it already knows how to provide for free.

This is a regression from normal web behavior and makes ChatGPT navigation less interoperable with the browser.

Regression 4 — Delete is no longer available from the currently open conversation

Before the UI update, the menu of the currently open conversation included Delete.

The previous workflow was:

open chat
→ use chat
→ decide whether it is worth keeping
→ delete it immediately from the currently open conversation

The current workflow is:

open chat
→ use chat
→ decide it is not worth keeping
→ leave the current context
→ find the same chat again in the sidebar or search
→ open another menu
→ delete it there

During the rollout I also observed inconsistent behavior inside the same account: an older existing chat still exposed the direct Delete action while a chat using the current UI did not.

Temporary Chat is not an equivalent workaround because the user often does not know at the beginning of a conversation whether the conversation will be worth keeping.

Why these regressions matter together

These changes all increase navigation and context-switching overhead.

For intensive technical/development use, parallel ChatGPT tabs are not cosmetic. They are used to:

• preserve one conversation while starting another task;
• compare outputs between conversations;
• inspect previous project context;
• supervise coding/agent work in parallel;
• keep long-running technical threads available without repeatedly searching for them.

The removal of native link behavior forces additional navigation every time a parallel conversation is needed.

The removal of direct Delete forces the user to search for a conversation that is already open in front of them.

This also discourages cleanup: chats remain in history not because the user wants to keep them, but because deleting them now requires extra search/navigation work.

Cost / supervision impact

For coding-heavy use, model and agent usage is metered and valuable enough that users cannot simply ignore efficiency, leave everything running indefinitely, and rerun work whenever something goes wrong.

Active human supervision, context preservation, and comparison between threads are part of the real cost of using the product.

A UI change that repeatedly adds navigation, searching, and context switching therefore increases the human supervision cost of the product even if each individual interaction only adds a few seconds.

Repeated across a development day, that becomes significant.

Steps to reproduce

Native-link / new-tab regression

1. Open https://chatgpt.com/ in Microsoft Edge on Windows 11.
2. Right-click New chat in the sidebar.
3. Observe that the browser shows the generic page context menu rather than a link context menu.
4. Try Ctrl+Click or middle-click on New chat.
5. Observe that it does not provide the previous native new-tab workflow.
6. Repeat with an existing conversation entry.

Direct Delete regression

1. Open a normal ChatGPT conversation.
2. Open the three-dot menu for the currently open conversation.
3. Observe that Delete is not available there in the current UI.
4. To delete the conversation, go to the sidebar/search.
5. Find the same conversation again.
6. Open its sidebar menu.
7. Delete it there.

Expected behavior

ChatGPT should preserve standard browser navigation semantics.

Preferred behavior:

• “New chat” is a real link/deep link where technically possible.
• Conversation entries are real links/deep links.
• Right-click, Ctrl+Click, and middle-click work normally.
• Copy link address is available.
• The currently open conversation includes a direct Delete action with the existing confirmation dialog.

If ChatGPT requires custom JavaScript navigation internally, an equivalent explicit Open in new tab action should be provided without removing native browser behavior where possible.

Actual behavior

The current UI replaces direct/native workflows with additional in-app navigation:

• New chat cannot be opened in another tab using normal browser link behavior.
• Existing conversation entries lose native link actions.
• Standard right-click/Ctrl+Click/middle-click workflows are removed.
• Deleting the currently open conversation requires finding the conversation again in the sidebar/search.

Scope

I am grouping these together because they appeared with the same recent web UI change and they have the same user-facing effect: conversation navigation and lifecycle management now require more in-app searching and context switching.

If these are owned by different internal components, please split them internally as needed, but they represent one coherent workflow regression from the user side.

Related community reports

Similar regressions are already being discussed in the OpenAI Developer Community, including reports about:

• conversations no longer being normal links;
• middle-click / Ctrl+Click no longer opening chats in new tabs;
• “New chat” losing new-tab behavior;
• recent ChatGPT web UI regressions affecting established workflows.

The important point here is that this is not a request to invent a new workflow. It is a request to restore standard browser and conversation-management behavior that previously existed.