Yard Docs
Sign in
On this page

Terminals

Open a shell in a workspace or a project's container from a tab, and connect terminals straight to a runner.

Updated November 11, 2026 · 5 min read

Every workspace has a terminal: a shell inside the same container the agents use, on the workspace's runner. Nothing runs on your computer or on Yard's servers.

Open a terminal

Terminal in the bottom bar opens a panel under the work, which it pushes up rather than covers; drag its top edge to resize it. Agent terminals are sub-tabs of the panel. On a phone it is in the bar's … menu and fills the screen. It opens the terminal of what you have open:

  • in the workspace, the workspace's own container, in the workspace's files;
  • on a project's page, that project's container, in the project's directory with its worktrees. A project gets its terminal once it has been set up.

To get to another project's terminal, open that project.

A hosted app has a shell of its own too: Terminal in an app's menu on the Apps page opens a shell inside that app's container, in a window over the page. It is offered while the app runs, not for a database. Reopening it returns to the same shell. It has no GitHub access.

More than one terminal

Choose New terminal (the + next to the terminal's name) to open another shell in the same place. Each gets a tab, named after the place and numbered, such as workspace 2. Up to eight can be open in a workspace, and in each project.

The × on a tab closes that terminal and ends its shell. Asking for a terminal gives you one of your own. Others who can edit the workspace see your terminals and can open them to watch, but only you can type in a terminal you opened: what they type is ignored, and it never gets their GitHub access. Closing one closes it for them too. The last terminal has no ×; its shell keeps running when you close the tab.

Your shell runs as a user of your own in the container, with a home of your own: ~ holds your dotfiles and shell history, and ~/workspace leads to the workspace. Files of the workspace are shared with everyone who works in it, but another person's shell or agent cannot read your shell's environment, your agent's sign-in or what your yard command sends. Code the workspace runs (a git hook, a package script) runs as whoever runs it, so only work in workspaces with people you trust with that.

A chat's agent in a terminal

In your own Claude Code or Codex chat the agent runs as its own CLI in a terminal session: Open in terminal adds an Agent tab with the chat's title, showing the session the chat's messages go to. Closing that tab leaves the agent running; End session in the tab's … menu closes it. Terminals count character widths the way the agents' CLIs do, so their symbols and boxes line up. See the agent in a terminal.

During an agent sign-in, Open terminal in the sign-in dialog shows the sign-in's own CLI. Typing in it takes over from Yard's automatic answers; Yard still saves the account when the sign-in succeeds.

Who can use it

People who can edit the workspace can open terminals; viewers cannot (see sharing and roles). If the person who opened a terminal can no longer edit the workspace, the terminal ends. The prompt names you and the workspace, for example alex@asset-library, so it is clear whose shell it is.

A workspace on someone's own computer (a personal runner set up with Yard for desktop) may ask its owner first: at the Workspaces I approved and Ask me first levels, a terminal opened by anyone else waits until the owner allows it on that computer, and fails with "Waiting for the owner of this computer to approve" when they do not answer within 5 minutes. A paused computer opens no terminals. See Yard for desktop.

When the runner goes offline the panel says "Runner offline. The terminal comes back when it reconnects." A dropped connection is retried by itself; if the shell exits, choose Reconnect to start a new one.

Copy and paste

Keys What they do
Ctrl+Shift+C Copy the selection.
Ctrl+C or ⌘C Copy the selection; with nothing selected, interrupt the running command.
Ctrl+V, Ctrl+Shift+V or ⌘V Paste.

A right-click opens a menu with Copy, Paste, Select all and Clear. Where the browser does not let Yard read the clipboard, the paste keys fall back to the browser's own paste.

Tools in a project terminal

A project terminal has yard, yard-canvas, yard-shot and yard-display on its PATH. A terminal can read the workspace's repositories on GitHub with the Yard GitHub App's access, the same an agent gets: git fetch origin and gh pr view work, and nothing in it can push. Your own GitHub connection never enters the box, since everything in a workspace runs as one user and could read it. To push, run yard git push (Yard pushes the project's branches as you) or use Yard; open pull requests from Yard. Git only hands the App's access to GitHub itself, never to another host a repository is pointed at, and it is never written to a file. See repositories and git.

From your own computer

The yard command-line tool can open the same shell from a local terminal with yard workspace shell. See installing the CLI and the CLI reference.

Direct runner domains

Normally a terminal's traffic passes through Yard's API on its way to the runner. An organization admin can give a runner an address of its own, so browsers connect to it directly:

  1. On the runner machine, run yard runner direct set --listen <host:port> (with --cert and --key, or behind your own HTTPS proxy).
  2. In Yard, choose the runner in the Runners menu (or Settings on it on the Runners page) to open its settings, and enter its https address under Own address. Choose Save, then Check.

The settings say whether the address "answers as this runner". This works only for runners that are pinned to their machine. File downloads use the same address.

A terminal that connects directly shows "Direct". When the address cannot be reached, the terminal falls back to the usual route through the API by itself, so nothing breaks for people outside your network.

See installing a runner for setting up runners.

Was this page useful?
Edit this page