Terminal Session Profiles

Manage and auto provision terminal sessions in VS Code.

Text Editors

Software Engineering

Developer Tools

GitHub

Visit WebsiteSee on Product HuntGithub ⧉Twitter ⧉Visual Studio Marketplace ⧉

Multiple terminals are now a staple of ongoing development work. Instead of rebuilding named Claude sessions, servers, PowerShell tabs, and WSL environments each time VS Code restarts, Terminal Session Profiles saves the complete setup and brings it back ready to use. The rise of coding agent tools has made terminal management a much more central part of the day-to-day workbench. Terminals are no longer temporary scratch space. They often represent distinct, long-running parts of a project, each with its own name, working directory, and purpose. Our own configuration commonly runs several named Claude Code sessions alongside one PowerShell terminal and one WSL terminal, so three to five tabs in a single project is normal. VS Code already includes native terminal persistence, but restoring a terminal tab is not the same as restoring the session that previously occupied it. A restored tab may keep its old name and scrollback while reopening as a new default shell with none of its previous processes running. The tab looks familiar, but the environment it represented is no longer there. A profile records which shell to open, which directory to open it in, and an ordered list of commands to run once the shell is ready. Commands are replayed literally and in order, so "claude --resume ClaudeCodeSessionName" reopens that particular named session rather than whatever ran last in that folder. Each command except the final one is awaited before the next begins, which lets a profile prepare an environment before starting a long-running process. Before replacing a restored terminal, the extension compares the process recorded when the profile was launched against the process that returned. If the original genuinely survived, the terminal is left alone rather than being terminated and recreated. There is a second, optional half. The Explorer, editor, terminal, and chat areas can be arranged as collapsible columns with status-bar controls, and each workspace remembers its own arrangement. It controls VS Code's real interface containers rather than replacing them, so the terminal keeps its normal list and Claude Code or Codex continue to operate inside their existing panels. It can be disabled without affecting profiles, command replay, or restoration. Free, open source, MIT licensed. The two minute video is silent with on-screen captions. Happy to answer any questions here.