D-1301Terminals
Terminals overview
What the integrated terminal is, where it lives, and what it can do.
- Topic
- Terminals
- Available on
- Available onDesktopWeb PortalMobile
- Reviewed
- May 15, 2026
On this page
Every session has a built-in terminal so you can run commands alongside the agent without leaving the app. It is a real PTY — the same shell you would get from your OS terminal — attached to the session’s working directory.
Where it lives
On desktop and the portal, the terminal is a resizable bottom-docked panel inside the session view. A toggle bar at the bottom of the transcript opens it; drag the top edge to set the height. When closed, the bar shows how many terminals are currently pinned to the session.
On mobile, the terminal opens as a full-height bottom sheet from the session view’s tab bar.
What it can do
- Run any shell that exists on the host (your default
$SHELL, or whichever the host falls back to). - Open multiple tabs per session, with drag-to-reorder.
- Replay output after a reload or reconnect from a circular buffer kept on the host — you don’t lose scrollback when you close and reopen the panel, and replayed output is re-wrapped to the window you reconnect on.
- Find within scrollback with case, regex, and whole-word options.
- Pin a terminal to one session and reuse it from another via the Pin existing menu, so you don’t have to recreate scratch shells.
What it does not do
- It does not give the agent a terminal. The agent runs commands through its own tool calls, which appear in the transcript with their own approval flow. The integrated terminal is for you.
- It does not run on a remote machine you haven’t activated. Each terminal lives on a Glueprint host — the desktop app or a CLI daemon — and a portal/mobile session is a remote view of that host’s terminal, not a separate shell.