Thanks, that’s a helpful data point. The fact that the Editor window stays clean while the Agents window grows to 5 to 8 GB without parallel sessions matches a known group of bugs around the new Agents window surface, where listeners and composer state can accumulate during long sessions. We’re tracking the issue, but there’s no ETA for a fix yet.
If you decide to try the Agents window again and notice memory creeping up, please grab a screenshot of Process Explorer before restarting Cmd+Shift+P → Developer: Open Process Explorer. Which process is growing renderer, extensionHost, or ptyHost and roughly how long it’s been since the session started will really help narrow down which leak path is getting triggered for you.
For now, using the Editor window as a workaround is the right call if it covers your flow.