Sessions & terminal
Open a local terminal
The Terminal surface opens a real shell on your own machine as a tab
beside your SSH and console sessions — handy for a quick ping, a git
command, or an SSH you’d rather run by hand. It’s human input: the AI is
structurally blind to it.
Steps
- Click the Terminal tab in the left rail (the third rail tab, beside your SSH and API sessions).
- The launcher lists the shells installed on your machine, each with its
version —
zsh,bash,fish, PowerShell,cmd, any WSL distros, and Python / Node REPLs that are on yourPATH. - Click the shell you want, or take the default. A new terminal tab opens with that shell running.
What you can do
It’s a full terminal, the same as the SSH panes:
- Type and run anything — it’s your machine, so there’s no permit list and no approval prompt (those are agent-only).
- Split and tile it alongside SSH, console, and other local shells.
- Clear the scrollback, and log it to a file or export it, the same as any session.
- Open as many as you want; each is its own tab.
Restart in place
When the shell exits — you type exit, or a REPL quits — the tab stays put
with its final output on screen and a banner prompting you to press
Enter to restart. Enter spawns a fresh shell in the same tab, scrollback
preserved.
No Terminal tab?
If there’s no Terminal tab in the rail, an administrator has disabled
the surface with [terminal] enabled = false in Transit’s config.toml.
It’s on by default. See Local terminal for the
full surface, including where the config file lives.