When starting a new agent, the “Browse Files” sidebar automatically closes, forcing me to reopen it and re-navigate to my file each time. This breaks my workflow, especially when I’m actively referencing a file tree while working across multiple agent sessions.
Request: Add a setting (or persist the current state) so the “Browse Files” sidebar stays open across new agent sessions, preserving file tree context instead of resetting on every new agent start.
Impact: Frequent context-switching cost — losing file focus interrupts concentration and adds repetitive manual steps to an otherwise smooth workflow.
Hey, thanks for the feature request. Right now, when you start a new agent, the panel state is only saved for the Browser and Terminal tabs. The Files tab doesn’t keep it, so what you’re seeing is the current behavior, not something in your setup.
I shared the request with the team. It fits the same topic as other tracked requests about keeping side panel state in the Agents Window when switching agents, which currently applies to the Browser tab. Extending this to the Files tab makes sense, so I’ll add your case to that effort.
I can’t share an ETA yet, but I’ll post here if there’s an update.
The browser and terminal do not stay open when you switch to a new agent. They remain active in the original chat, but there is no indication of them in the new chat and requires manually reopening browser, files, etc.
Hey, thanks for clarifying. There are two separate things here, and you’re right on both.
About the Files tab, this is expected behavior right now. When you start a new agent, the panel state is only kept for Browser and Terminal, and the Files tab doesn’t carry over. I’ve already passed this to the team as a request to extend this to Files, I mentioned that above.
About Browser and Terminal not showing up in the new agent, there’s a nuance. The panel can stay open, but the tabs themselves are tied to a specific agent, so the browser and terminal from the original chat won’t appear in the new one and you need to open them again. That’s a separate issue we’re already tracking. I can’t share an ETA yet, but I’ll post here if there’s an update.
If you want, you can start a separate thread just about Browser and Terminal behavior when switching agents. It’s easier to track that case separately from the Files request. Let me know if anything behaves differently on your side.