9 matches across problems, recipes, configs, comparisons, and discussions.
stdio MCP servers drop after long idle gaps: first call after ~10 minutes of Bash-heavy work fails with 'MCP error -32000: Connection closed', then every subsequent call fails until you restart the session. Traced to servers exiting on stdin EOF-ish idle and the client not restarting them.
Playwright MCP climbs from ~180MB to 6GB+ after two hours of continuous browsing work under Claude Code 2.4.0. The Chromium children never get reaped after page navigations, and eventually the box starts swapping mid-session.
MCP servers die quietly mid-session and the agent just... stops using the tool. Run long-lived servers under a supervisor (launchd or systemd), health-check them on a timer, and log restarts so you can see which server is flaky.
Eight days migrating a legacy widget suite to WidgetKit with Claude Code and XcodeBuild MCP: timeline budgets, a haunted pbxproj, and $84 of tokens.
iOS is the acid test: Xcode builds, simulators, and API churn. With XcodeBuild MCP wired up, Claude Code pulls clearly ahead; without it, both are guessing.
Claude Code can't see Xcode's build errors unless you hand them over. XcodeBuild MCP plus a formatter that strips the noise gives the agent a real edit-build-test loop for SwiftUI work — the difference between guessing and iterating.
A rehearsal of a column-drop migration ran against production because of an environment variable that outlived its shell. Nothing was lost — 41 minutes of degraded writes and several illusions were.
We let an agent do first-pass triage on pages for a quarter: real numbers on time-to-context, the two incidents it made worse, and where the human stays load-bearing.
Show me what actually works. Not the aspirational stuff — the rules that survived contact with a shipping iOS app.