Terminal Session Profiles

Save a terminal as a reusable session profile (which shell to open, where, and what to run once it is ready), then bring it back with one click after a restart. Also repositions the Explorer, terminal and chat panes as collapsible columns.

Watch the two minute demo on YouTube.

Install from the Visual Studio Marketplace, or from Quick Open inside VS Code (Ctrl+P):

ext install GBTI.gbti-terminal-sessions

Built on VS Code's native terminal support

VS Code already supports persistent terminal sessions, but its native features are spread across terminal profiles, tasks, settings, and workspace permissions.

Terminal Session Profiles brings those pieces into one UI and adds reusable workspace or global profiles, ordered startup commands, automatic reprovisioning, and optional Claude session resume commands.

VS Code remembers what was open. This extension remembers what should be opened.

Session profiles

A profile is a saved terminal setup: which shell to open, where, and what to run once it is ready. Create one from the sidebar's ＋, or right-click any terminal and choose Save as Instance Profile to start from a terminal you already have open.

• Sidebar. Every profile, with an inline ▶ to launch and ✎ to edit. Clicking a profile edits it rather than launching, because spawning processes is too consequential for a single click.
• Editor. All fields at once: name, shell, directory, and an ordered command list you can reorder and delete inline.
• Terminal + dropdown. Tick Show in the terminal + dropdown and the profile is mirrored into terminal.integrated.profiles, appearing there by name. Commands still run, because the extension replays them whenever a terminal opens with a matching name.

Saved profiles come back on their own after a restart, in the right shell with their commands replayed.

Each profile says when it does that, under Open on startup in the editor:

A profile with no answer of its own follows terminalSessions.autoLaunch, which you can set globally or per project. The same three values apply at every level and the most specific one wins, so a project setting overrides your user setting and a profile overrides both.

Workspace and global profiles

Profiles are saved to the current workspace by default, inside .vscode/settings.json. You can instead save a profile globally so it follows you between projects.

Use the Saved in control to move a profile between scopes. The sidebar shows both workspace and global profiles, with global profiles clearly marked.

• A workspace profile overrides a global profile with the same name.
• Profiles added to the terminal + menu retain their original scope.
• To move several profiles at once, run Move Global Profiles into This Workspace.
• terminalSessions.profileScope only controls where new profiles begin.

How commands run

Commands run in order after shell integration is ready. Each command must finish before the next begins, while the final command may remain active.

For example, place claude --resume ClaudeCodeWorker1 last to reopen a specific Claude Code session, or use claude --continue to resume the most recent session in that directory.

Column layout

Show or hide the Explorer, editor, terminal, and chat from status-bar controls. The layout is remembered per workspace and uses VS Code's native panes, preserving terminal lists and Claude or Codex chat.

One column always remains visible so the workspace cannot be left empty.

Commands

Open the palette with Ctrl+Shift+P and type Terminal Sessions to see all of them.

Settings

License

MIT, copyright Gethsemane LLC. See LICENSE.