Working with Zed terminal

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

When working in Zed terminal, agent cli stops (or cli buffer glitch) many times.

Clicking terminal window or hitting arrow key refreshes the buffer, but the “Reconnecting…” appears.

Steps to Reproduce

  • Launch Zed 1.10.1 on windows
  • Open terminal and move it to editor pane
  • Run agent in WSL environment (agent sandbox enabled)

Expected Behavior

Working

Screenshots / Screen Recordings

ss 2026-07-12 101947.jpg

Operating System

Windows 10/11

Version Information

CLI Version         2026.07.09-a3815c0
OS                  linux (x64)
Terminal            unknown
Shell               bash

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report. I can see the screenshot with the banner Reconnecting to agentn.global.api5.cursor.sh.

There are two separate things here:

  1. The buffer glitch or freeze is known behavior of the agent TUI in embedded terminals that resize or re-layout. agent is a full-screen TUI, and on every resize it fully redraws the history. When you move the Zed terminal into an editor pane, that triggers a resize, and Zed’s embedded terminal emulator (especially on WSL) doesn’t always render the redraw cleanly. Also, Zed doesn’t always set a detectable TERM_PROGRAM (in the version info it shows Terminal: unknown), which can prevent the CLI from applying terminal-specific tuning.

  2. The Reconnecting... banner is a separate network retry banner. It’s not about redraw, it just becomes visible when you force a buffer redraw by clicking or pressing an arrow key.

Workarounds that usually help:

  • Run agent in a separate standalone terminal, not in a pane you move or resize.
  • Don’t move the pane mid-session.
  • Alternatively, use Zed’s ACP integration to work with Cursor via ACP instead of the raw TUI.

We’re tracking the redraw behavior in embedded terminals, but I can’t share an ETA for a fix yet. Let me know if the workarounds helped.

8

Thank you for sharing workaround. I hope to see this problem fixed.