Workspaces

The tab bar across the top keeps separate contexts. Each workspace remembers its own terminals, columns, tile heights and broadcast targeting, and switching keeps the other workspaces’ processes running in the background.

Broadcasting only ever hits the active workspace.

Naming

Opening a repo’s first terminal into an empty workspace auto-names that workspace after the repo. Hit ＋ for a fresh one and open a different repo there — now each repo has its own space. A workspace can also hold several repos if you keep opening into it.

• Double-click a tab to rename it.
• Right-click for the same, plus Reset name, Change root folder…, Startup command… and Close workspace.
• ✕ closes it.

A workspace that has never been named by hand keeps following its first terminal, so renaming that terminal moves the tab with it. Naming the tab yourself stops that.

Your workspaces — and the last-active one — are restored on the next launch.

Per-workspace roots

Each workspace scans its own root folder, so one workspace can be your Roblox games directory while the next is your JS/web directory.

Click the root button at the top-left of the sidebar to point the active workspace somewhere else. The menu lists every root you’ve used before, plus Browse for a folder….

The sidebar, the project filter and the ⌕ Jump palette all follow the active workspace’s root. Pins, hidden projects and recents are shared across all of them, because they’re stored by full path.

New workspaces start on the root you’re currently looking at, and each tab shows a small root chip once your workspaces disagree. Terminals stay tied to the folder they were opened in, so a workspace can keep running terminals from a directory its root no longer covers.

A workspace for one folder

Right-click a folder in the sidebar — a project row, or the group header above it — and pick New workspace for this folder. You get a tab named after that folder with its root already pointed at it: the sidebar narrows to what’s inside, and ＋ New terminal opens there without asking which project.

• Right-click a repo and the tab is scoped to that one repo.
• Right-click a group and it’s scoped to that shelf of repos, terminals landing in the group folder until you open one in a repo under it.

Nothing is opened for you — the tab is just already aimed, one click or Ctrl+Shift+N from a shell in the right place.

The same row is on a tile’s Project flyout, and a group header also offers Use as root folder for this workspace, which re-points the tab you’re on instead of making a new one.

Minimizing

The — button in a tile header minimizes the tile out of the grid and leaves a small card in a bar underneath, so a terminal you’re done with for now stops taking up room without being closed. The shell keeps running the whole time — click the card to put the tile back where it was.

The card keeps reporting while it waits:

• Gold and pulsing when that terminal rings the bell.
• Struck through when its process exits.
• Carrying the same accent border a targeted tile does, so the bar still answers “what is Enter about to hit”.

Right-click a card for the terminal’s full menu, and drag one along the bar to reorder it the way workspace tabs reorder — what moves underneath is the terminal itself, so a card put back lands where its card was.

Minimized terminals are saved with the workspace, so one you tidied away comes back tidied away, in the order you left them.

Session persistence

Open terminals, pins, hidden projects, collapsed groups, column count, broadcast history and window size are remembered and restored next launch.

Each workspace entry carries its own root, its own startup command, and a lastProject — the folder ＋ New terminal falls back to once that workspace has nothing focused. Each terminal inside it has a title (empty when it is still going by its project’s name) and a seed holding the command and prompt a planned terminal was opened for.

Delete the settings file to reset to defaults.