When a Cloud Agent Project coordinator edits the Project’s notes.md, the change reaches cloud storage within about a second (confirmed in the agent-store sync log), but the Project panel / Context tab only shows it 1–2 minutes later. Running-agent spinners on linked agents lag too.
Steps to Reproduce
Have a Project coordinator edit notes.md (e.g. rename a heading).
Watch the Project panel.
Actual: it updates 1–2 minutes later. Closing and reopening the Context tab forces an immediate reload.
Expected Behavior
The panel updates within a few seconds.
Operating System
MacOS
Version Information
Version: 3.21.18
VS Code Extension API: 1.128.0
Commit: c4730f7d93d787d9ab120af715999f0345ee5bc0
Date: 2026-09-22T02:04:34.641Z
Electron: 42.10.0
OS: Darwin arm64 25.6.0
Additional Information
Why it matters: the panel is the main status board when a coordinator runs many agents, so stale lines look like work that’s stuck or finished.
Suggestion: a refresh button on the panel, or push file-change events to it.
This came back on Sep 23 at about 9:47 PM ET. Items that were removed from notes.md in the cloud kept showing in the Project panel for several minutes.
Measured on the Mac: the local copy got the new version about 90–150 seconds after the cloud edit. The sync log shows the new version downloaded 52 seconds before it was written to disk. The download was flagged as an etag mismatch because the cloud file changed while the sync pass was running.
This time .sync/sync.lock was not stuck. The Agents Window extension host held it for about 1h47m, but it rewrote the lock every 2 seconds and synced normally with nothing waiting.
Last night the same symptom came from a stale sync.lock held by the Agents Window extension host, and restarting the local agent worker cleared it.
Today the delay comes from two things. The file is edited often, so edits keep landing during a sync pass and wait for a later one. And every pass rechecks the whole store (about 2,900 files, 1.6 GB), with passes coming from 8 to 80 seconds apart. If the panel stays stale after the file on disk has updated, the panel’s own refresh adds more delay on top.
Hey @Imtiaz_Hossain - This is on our side, not anything you’ve misconfigured. Closing and reopening the Context tab (as you found) is the quickest way to force an immediate refresh in the meantime, and a leaner / less-churned Project store also syncs faster if that’s practical.
This is an issue we’re tracking around sync performance on larger Project stores, and your refresh-button / push idea is exactly the kind of feedback we’re passing along. I’ll follow up here when there’s an update.
Following up on the Project panel lag you reported. We tracked it down to the two things you spotted on large Project stores: each sync pass listed the store’s folders one at a time, and a notes.md that changed while a pass was running got thrown away and picked up only on a later pass. Both are fixed, and the fix is coming in Cursor 3.23.
On a store about the size of yours, a heading rename that used to take close to a minute to show up in the Context tab now shows up in roughly 10 to 15 seconds.
Please give it another try once you’re on 3.23 and let me know how it looks. Until then, closing and reopening the Context tab is still the quickest way to force a refresh.