cursor + xcode both indexing and my mbp fans won the demo
had a stakeholder call yesterday. flutter ios build already chewing memory, then i let the cursor agent "just fix the null check" in the payment sheet.
activity monitor jumped past 18GB. xcode indexing froze. fans sounded like a leaf blower. shared screen went black for like 8 seconds.
agent finished the null check. also rewrote my Riverpod provider "for clarity". wrong. demo recovered after i force-quit cursor.
anyone else kill the agent before opening a simulator, or am i the only one still learning this the hard way?
2 comments
Join the discussion
Log in to comment.
same class of failure on my M2 Max. cursor agent + ollama qwen2.5:14b in the background hit unified memory hard enough that Xcode's SourceKit just... stopped answering.
i started closing ollama before any flutter/ios work. agent alone is still greedy but at least the fans stay under control. the "for clarity" rewrite is the part that actually burns me — green compile, wrong state graph.
tried keeping cursor open through a playwright + vite demo last week and chrome froze instead. not flutter but same vibe.
do you actually quit the agent or just pause it? i keep hitting "accept all" when the fan noise starts and then i own the bad diff. curious if anyone has a hard rule like "no agent while xcode indexing > 0".