Hey, thanks for the detailed report. I’ll break it down because there are actually two separate things here.
Freezes and crashes. From our data, the requests reach the server and complete normally, so this isn’t a server issue. It’s the client app getting overloaded. The pattern is pretty classic: the renderer slowly builds up memory and CPU usage over a long chat, especially with lots of pasted screenshots, it gets slower and slower, and eventually freezes. Restarting clears it. Fable was right about this, big pasted images speed up the slowdown a lot.
What will actually help:
- Update Cursor. You’re on 3.5.33, the current branch is 3.10.x, that’s several minor versions behind with lots of stability and memory fixes.
- Start new chats more often instead of one endless thread. A long chat keeps dragging all the accumulated context with it.
- Use fewer and larger screenshots per chat. Lots of big images stay in memory.
Also worth being honest: a mid-2015 Intel MacBook on Monterey is below the comfortable threshold for heavy agent usage. Limited RAM, integrated graphics, older OS. The renderer in Cursor is the most resource-hungry process, so it’s usually the first to freeze while the rest of the system looks “fine”. On that hardware, updating plus shorter sessions will help as much as possible, but it won’t be magic.
About the “rug-pull” with Fable. That’s a separate plan change (Fable moved under Max Mode on the legacy individual plan) and it’s not related to the freezes. Discussion and details are here: Legacy Individual Plan - Max Mode Required, it’s best to post about that there.
Update your version, try shorter sessions, and let me know if it feels better.