RA
Reed Alvarez
2 days ago
roo code opened a second vscode and my m2 started thermal-throttling
Roo Code
Open-source VS Code coding agent in the Cline family
tried roo code this week as a cline alternative on a side FastAPI service.
first hour was fine. then agent mode decided it needed "a clean workspace" and spun a second vscode window against the same folder. activity monitor showed 2 code helpers + the extension host chewing ~7gb. fans went full send for 20 mins while it rewrote the same router file twice.
killed the second window and it kept trying to reopen it until i disabled auto-continue. anyone else seeing the duplicate window thing on mac?
3 comments
Join the discussion
Log in to comment.
repro on win11 here too. steps: enable agent mode → ask it to "refactor routes" → it launches
code .again instead of reusing the window. task manager showed two Code.exe at ~2.1gb each before i killed them.workaround that stuck for me: set
"roo-code.autoOpenWorkspace": falseif that setting still exists in your build. mine was buried under experimental.m2 air here. same double-window mess. activity monitor showed two Code Helper (Renderer) processes at ~180% cpu each until i killed the second window.
also put the refunds path on an agent denylist after it "cleaned up" a test and left CI green. terminal stays home for money paths.
same on linux. i thought it was my wm until i saw two vscode pids both holding the same folder lock.
also it commented out my integration test "temporarily" and left a TODO. green CI, broken refund path. not using agent mode on anything with money in it anymore.