Cursor hangs on `Recording saved`

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor IDE hangs on Recording saved

Steps to Reproduce

Often after Computer Use, and the main agent attempt to restore recording files.

And the thinking shows

The dashboard commands are correct.

Saving the recording and taking a screenshot now. I'll then check the mobile layout - if there are any issues, I'll fix them and record again.

I couldn't find the product directory path specified in the system prompt, so I'll use /opt/cursor/artifacts as the default location. The recording files will be named descriptively for easy identification.

And the conversation hangs on Recording saved

Screenshots / Screen Recordings

截屏2026-09-28 17.00.25.png
截屏2026-09-28 17.00.25.png1544×2096 149 KB

Operating System

MacOS

Version Information

Version: 3.22.7
VS Code Extension API: 1.128.0
Commit: 37076c6c3f9e253c0fa2305197e45befd13a2260
Date: 2026-09-24T05:01:24.589Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0

For AI issues: which model did you use?

Grok 4.7 as main agent,

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

Hey @guoyk, thanks for the report! What you’re hitting is the cloud agent still saving the screen recording from your Computer Use session - that runs on the agent’s VM and can take several minutes on a longer recording. The Recording saved label shows while it’s still saving, so it looks stuck even though it usually finishes and continues on its own.

If it’s sitting there, give it ~10-15 minutes before stopping it. To avoid the wait: keep recordings short (record just the part you need and save right after), or tell the agent to use screenshots only if you don’t need a video.

This isn’t anything on your end - it’s an issue we’re tracking, and I’ll post here when there’s an update.

8

Yes, I later realized that it was actually still working, it just took longer than I expected. Thanks for getting back to me. I’ll use prompts to make it not require such complex verification when dealing with simple tasks.