Agent / Glass window: chat does not stay pinned to bottom while agent streams output

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE — Agent / Glass window

Describe the Bug

When an agent session is producing output, the view does not stick to the bottom — the latest (bottom-most) output scrolls out of view and I have to manually scroll down to keep following along. It seems to stop tracking the bottom once terminal/code-block widgets get appended to the conversation.

This matches the earlier report Agent stops scrolling chat buffer automatically after terminal or code boxes appear in chat (which was tagged Cursor CLI and has since been auto-closed). I am confirming the same behavior in the GUI Agent / Glass window, in case that helps scope the fix beyond the CLI.

Steps to Reproduce

  1. Start an agent task that produces a lot of streaming output (including terminal/code blocks).
  2. Keep the conversation scrolled to the bottom.
  3. Observe: as new output arrives (especially after a terminal/code widget), the view stops following the bottom and you must scroll down manually to see the latest output.

Expected Behavior

While the conversation is scrolled to the bottom, it should stay pinned to the bottom as new output streams in, so the latest output remains visible without manual scrolling.

Operating System

MacOS

Version Information

Cursor 3.6.31

Does this stop you from using Cursor?

No - Cursor works, but with this issue

7

This is a known one: while the agent is streaming, the chat can lose its “stick to bottom” lock when a terminal or code block expands and changes the layout mid-stream, so new output lands below the fold until you scroll down. Our team is actively working on this - a few fixes have already shipped and more are in progress - though it’s a stubborn one that’s had several causes, so it isn’t fully resolved yet.

There’s no clean workaround for now beyond using the scroll-to-bottom control (or scrolling manually) while it streams.

One thing that would help us route this to the right fix: are you seeing it with local agents, cloud agents, or both in that window? The streaming-tail behavior has a slightly different cause for cloud agents, so knowing which one you’re on helps us pin it down.

8

Thanks @mohitjain. I’m seeing it with local agents — that’s all I run in that window, so I can’t speak to cloud agents (I don’t use them).