{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieyuxx62muiwscm6qhvn2yhzawf3vhh6bv74a5rxxw3ydieuoikfa",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mfwi3glulbw2"
  },
  "path": "/t/prevent-auto-scroll-to-bottom-after-text-only-tool-output-when-exiting-full-screen-widget/1375357#post_1",
  "publishedAt": "2026-02-28T13:06:37.000Z",
  "site": "https://community.openai.com",
  "textContent": "We’re running into a UX issue related to tool calls and full-screen widgets.\n\nIn our app, we display a map in a full-screen widget. While the map is open, the user can continue prompting. When they do, we handle the intent with a tool that updates GPS coordinates (e.g., to change the map location). This tool returns text-only output and is meant purely to update the widget state.\n\nThe issue occurs when the user exits full-screen mode. Instead of returning to the widget in context, ChatGPT scrolls to the bottom of the conversation. This happens because the tool call triggers a standard assistant response, which gets appended to the thread.\n\nFrom a UX perspective, we’d prefer one of the following:\n\n  1. A way to prevent ChatGPT from auto-scrolling to the bottom after a tool call in this scenario.\n\n  2. A way for a tool to indicate that no assistant message should be generated in response.\n\n  3. Some mechanism to mark a tool invocation as “UI-only” or “state update only,” so it doesn’t produce a visible conversational turn.\n\n\n\n\nIs there currently a supported pattern for this? If not, is there a recommended workaround to avoid the scroll behavior when the tool is being used strictly to update widget state?\n\nAny guidance would be appreciated.",
  "title": "Prevent auto-scroll to bottom after text-only tool output when exiting full-screen widget"
}