Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Summary
In Agent/Chat, the input composer sometimes leaves its anchored home at the bottom of the panel, floats upward over the conversation, then abruptly snaps back down. When it snaps, the conversation behind it jumps to a new scroll position. During the drift, scrolling feels stuck/jittery and the underlying text is hard to read because the composer (and sometimes message action icons) overlay mid-thread content.
Steps to Reproduce
I encountered this on agentic surface, not in a repo, empty Home cha screen full width and After I had gotten it to draw a couple mermaid type flowchart diagrams, but I’ve seen this composer box float before too.
Steps to reproduce
Open a long Agent/Chat thread (enough content that the panel scrolls).
Scroll up through older messages while the composer is visible.
Continue scrolling / interacting until the composer leaves the bottom and sits mid-panel over message content.
Keep scrolling or wait until it “corrects.”
Observe the snap back to the bottom and the sudden jump of the conversation behind it.
Expected Behavior
Expected
Composer stays pinned to the bottom of the chat panel (or moves only with intentional layout changes).
Conversation scroll is independent and smooth.
Composer never covers mid-thread content.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
Version: 3.11.19 (user setup)
VS Code Extension API: 1.125.0
Commit: bf249e6efb5b097f23d7e21d7283429f0760b740
Date: 2026-07-12T21:39:24.175Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200
Additional Information
Actual
Composer visually detaches and translates upward over the transcript.
Near the top of its travel (or after some scroll/update), it hard-snaps back to the bottom anchor.
That snap reflows / resyncs the conversation scroll, so the page “slams” to a new position.
While detached, scroll feels poor and reading is blocked by overlay.
Sometimes detached UI chrome (e.g. “1m ago”, thumbs, copy) also floats over content, suggesting a layout / sticky-position / scroll-container sync failure rather than just “scroll is slow.”
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor


