Disappearing messages after the ai prints a table

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

i can’t share much info as it’s on private data

but first i thought it didn’t print the message but going back my prompt history the message i sent was there and re-sending the prompt showed the response

but later after it printed a table it couldn’t print new messages (they disappeared quickly)

leaving cursor cli and re-opening the conversation showed the messages

Steps to Reproduce

not sure, maybe have a discussion with tables and send messages

Expected Behavior

prints the answers

Operating System

MacOS

Version Information

About Cursor CLI

CLI Version 2026.07.23-e383d2b
Model Auto Balance
Subscription Tier Team
OS darwin (arm64)
Terminal apple-terminal
Shell fish
User Email [email protected]

For AI issues: which model did you use?

auto

For AI issues: add Request ID with privacy disabled

i can’t share

Additional Information

tried to debug with cursor but it told me it’s a rendering bug

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey there!
Nothing is lost, for what it’s worth: the conversation is stored separately from what’s drawn on screen, which is why reopening brings it all back.

Two things that should help:

  1. Ctrl+L redraws the screen and should bring the missing messages back without quitting. It only works when the agent isn’t mid-run, and it clears your terminal’s scrollback, so scroll up first if there’s anything above you want to keep.
  2. A taller terminal window makes this much less likely. The redraw goes wrong when the section the CLI is actively updating grows taller than the window, and a big table is usually what tips it over.

This isn’t something you misconfigured. Our team is looking into this rendering behavior, and the table detail is a useful lead. No timeline to share yet, but I’ll post here when there’s an update.

If you get a chance: roughly how many rows tall was your Terminal window, and did the table have emoji or non-Latin characters in it? Those point at two different causes, so it’d tell us which one you hit.