Reported by @potent sonnet
- Open ChatGPT Atlas on macOS.
- Use the native Atlas ChatGPT/new-tab experience, not chatgpt.com opened as a normal website.
- Ask ChatGPT to inspect or reference another open tab/page.
- Observe that ChatGPT suggests opening or using a side chat/sidebar to inspect the page.
- Look for the Ask Chat / side-chat control in the native Atlas ChatGPT tab.
- Compare this with opening chatgpt.com as a normal website inside Atlas, where the Ask Chat / side-chat style control is visible.
Atlas should clearly distinguish between native ChatGPT/new-tab mode, chatgpt.com web-app mode, Ask Chat / side-chat mode, and Agent mode.
If native Atlas ChatGPT cannot inspect another tab or page directly, it should not suggest an unavailable side-chat control. It should instead clearly tell the user which action is required: use Ask Chat from the target page, attach/paste the content, open chatgpt.com in a normal tab, or use Agent mode.
In native Atlas ChatGPT/new-tab mode, ChatGPT suggested using a side chat/sidebar to inspect another tab or page, but that side-chat control was not available from the native ChatGPT tab.
This created confusion because Atlas has multiple ChatGPT surfaces that look related but behave differently. A normal webpage in Atlas can show the Ask Chat / side-chat control, while the native Atlas ChatGPT tab does not expose the same control.
The user had to open chatgpt.com as a normal website inside Atl
ChatGPT Atlas on macOS; ChatGPT Pro; native Atlas ChatGPT/new-tab mode; chatgpt.com opened inside Atlas; Ask Chat / side-chat UI; normal webpage tab testing.