# Terminals and tabs > Use Workroom's terminals and tabs, open file paths in your editor, find text, run a project command and use the Quick Terminal. Every workroom opens with a real terminal in its directory. This page covers opening and managing terminals and tabs, the Run command, the Quick Terminal and what to know about shell integration. ## Terminals Terminals are drawn by [libghostty](https://ghostty.org), the engine behind the Ghostty terminal. Select a workroom, and its terminal is already in the right directory. A workroom keeps its terminals running while you work in another one, so a dev server, a build or a coding agent is as you left it when you come back. While a program in a terminal reports that it is working, such as a coding agent, its tab shows a moving underline and its sidebar row a spinner, so you can see what is busy without switching to it. ## Tabs A workroom can hold as many terminals as you like. They sit in a tab strip that you can reorder by dragging. A tab names itself after the running command. When the command ends it goes back to its own name, such as **Terminal 1**, unless your shell sets a title of its own, such as the working directory. For long titles, the pane's title bar provides more room than the tab. Hover over the pane title to read it in full. | To do this | Use | | --- | --- | | Open a new terminal | ⌘T, or the new-terminal button in the tab strip | | Focus tab 1 to 9, left to right | ⌘1 to ⌘9 | | Next or previous terminal tab | ⌥⌘→ and ⌥⌘← | | Flip to the pane you used last | ⌃Tab (**Go ▸ Last-Used Pane**) | | Close the tab | ⌘W (**File ▸ Close Tab**) | | Scroll to the top or bottom | ⌘↑ and ⌘↓ | **File ▸ Close Other Tabs** and **File ▸ Close All Tabs** close several at once. Closing a terminal ends its shell and anything running in it. When a process is still running, Workroom asks first. This is on by default. Turn it off with **Settings ▸ Terminal ▸ Confirm before closing a terminal**, **File ▸ Confirm Before Closing a Terminal**, or **Don't ask me again** in the prompt. Right-click a tab for **Split Right**, **Split Left**, **Split Down**, **Split Up**, **Move to New Window** and **Close**. See [Splits and windows](/workroom/docs/app/splits-and-windows.md). Right-click inside the terminal for **Paste** and the same split, window and close commands, plus **New Terminal**. ## Find text Press ⌘F to search the focused terminal's scrollback. ⌘G goes to the next match and ⇧⌘G to the previous one. Press Esc to close the find bar. The same keys search a file you have open in a pane. ## Copy and paste With **Copy on select** on, anything you select in a terminal is copied to the clipboard straight away. It is on by default. Switch it in **Settings ▸ Terminal ▸ Copy on select** or **Edit ▸ Copy on Select**. ## Open file paths in your editor ⌘-click a file path in a terminal to open that file in your editor. It works on paths that point at a real file, including relative paths, and on `file:line:column` forms. VS Code, Zed and Xcode open the file at that line. Choose the editor in **Settings ▸ Terminal ▸ Open file paths in**. It lists **Default App** and whichever of Visual Studio Code, Zed and Xcode you have installed. **Default App** opens the file as Finder would. A ⌘-click on anything else goes to the terminal as an ordinary click. To open the whole workroom, use **Room ▸ Open in** your editor, for example **Open in Zed** (⇧⌘O), or the editor button in the workroom's title bar. Its small arrow lets you pick a different editor. **Room ▸ Reveal in Finder** shows the workroom's folder in Finder. In Workroom 2.1.0 these are **Go ▸ Open in** and **File ▸ Reveal in Finder**. Click the folder path in a pane's footer to copy it or reveal it. In Nightly, the editor button may briefly show a generic app symbol while its icon loads. The button still opens your editor immediately. ## Shell integration Workroom turns on Ghostty's shell integration for zsh, bash, fish, elvish and Nushell. It lets Workroom know when a command starts and ends and where your shell is. Failed-command diagnosis, the tab title reset after a command and working-directory tracking depend on it, and so does the [command result mark](/workroom/docs/app/notifications.md#command-results). macOS's own `/bin/bash` is version 3.2, and it ignores the startup hook the integration uses. If that is your login shell, you get none of these. Homebrew bash 4.4 or newer works: ```sh brew install bash echo "$(brew --prefix)/bin/bash" | sudo tee -a /etc/shells chsh -s "$(brew --prefix)/bin/bash" ``` Log out and back in so apps you open from the Dock see the new shell, then open a new terminal in Workroom. `echo $BASH_VERSION` should print 5.x. ## Terminals that outlive their tabs A terminal's shell is held by a background helper, not by its tab. That is why terminals keep running when you quit Workroom, and reattach when you open it again. Closing a terminal ends it. In Nightly, run commands are kept too, unless you choose to stop them when you quit (see [Quitting with a run going](#quitting-with-a-run-going)). The Quick Terminal is never kept. > [!NOTE] > In Workroom 2.1.0 this was a setting named **Persist sessions**. Nightly removed the setting, and terminals always survive a quit. ### Restoring hidden terminals (Nightly only) When you reopen Workroom, visible panes reconnect immediately. Hidden terminal tabs reconnect gradually after the window appears, so restoring many panes leaves room for clicks and typing. Their shells and commands keep running in the background helper throughout. ### Detached sessions A session can be running in the background with no tab in the workroom showing it. When the current workroom has such sessions, a button with a stack icon and a count appears at the right of the pane footer, the strip along the bottom of a pane. Click it to see **Detached terminals**. Each row shows the terminal's title and its folder, and three buttons: - **Active tab** attaches the session to the tab you are in. It is off until that tab has a terminal. - **New tab** opens the session in a new tab. - **Stop** ends the session and anything running in it. ### Stop all detached terminals (Nightly only) **Settings ▸ Terminal ▸ Stop Detached Terminals…** counts the background terminals that no open tab is attached to, then asks before it stops them and anything running in them. ## Run a command Set a run command for a project, such as `npm run dev`, and start it in any of its workrooms with one key. See [Projects](/workroom/docs/app/projects.md#run-command) for setting it. | To do this | Use | | --- | --- | | Run, or jump to the run if it is already going | ⌘R (**Room ▸ Run**) | | Restart | ⌥⌘R (**Room ▸ Restart**) | | Stop | ⇧⌘R (**Room ▸ Stop**) | | Go to the run terminal | **Room ▸ Go to Run Terminal** | In Workroom 2.1.0 these are in a **Run** menu, and going to the run terminal is **Go ▸ Run Terminal**. The workroom's title bar shows **Run** when idle and **Restart** and **Stop** while a run is going. **Stop** sends the command Ctrl-C and waits for it to exit. If it has not exited after about six seconds, Workroom force-quits it. The command runs in its own terminal tab, in your login shell, at the workroom's directory. The pane footer of that tab shows the run's state. If a run ends or fails while you are looking at another tab or workroom, a toast tells you. In Workroom 2.1.0, run commands stop when you quit Workroom. ### Stop from the sidebar (Nightly only) Project-root and workroom rows show their run control only while the run command is running. Click it to stop the command. The run terminal's footer immediately shows **Stopping…**, and the run tab and sidebar control show spinners until the command stops. Then the sidebar control disappears even if its run terminal stays open, including for a workroom on a host. ### Run from a context menu (Nightly only) Right-click a project row in the sidebar, a workroom, or its Run terminal tab to choose **Run**, **Restart**, or **Stop**. Project-row actions control the project's root directory; workroom and terminal actions control that workroom. **Run** needs a configured command. **Restart** and **Stop** are enabled while the command is running. ### Quitting with a run going (Nightly only) A run command is held by the background helper, as a terminal is, so it can keep running after you quit. The first time you quit with a run going, Workroom asks whether to keep your dev servers running or stop them, and remembers your answer. Change it in **Settings ▸ General ▸ When quitting with dev servers running**: **Ask**, **Keep running** or **Stop**. An update always keeps them running, whatever you chose. With **Stop**, the tab of each run that quitting stops is closed and does not come back. When you open Workroom again, every other run's tab comes back where you left it: - A run that is still going reattaches, with no toast. - A run you stopped comes back stopped, with its output. Press Run to start it again. - A run that exited or failed while Workroom was closed comes back stopped, with the toast that says how it ended. - A run that ended because your Mac or its host restarted comes back stopped, and says so. Nothing starts by itself. If Workroom's background helper isn't running, the run tab says so and runs nothing. Press Run to try again. ### Idle stopped runs (Nightly only) Stopped Run tabs keep their output and remain ready for Run or Restart. If a stopped tab kept from an earlier Nightly does not restart, close it and open a new Run tab. Restart reuses the existing session, so closing and reopening the tab is how it picks up the fix. ### Run on a remote workroom (Nightly only) On a remote or container workroom, the run command runs on the workroom's host, in its directory there, in the host user's login shell. Run, Stop and Restart work as they do on your Mac. If a container is stopped, Run and Restart start it first; Stop never does. If a run ends while Workroom is reconnecting to its host, for example because the host restarted, the tab stops and says so: "This run ended while Workroom was reconnecting to its host. Press Run to start it again." A run started on one Mac shows on another that opens the same workroom: pressing Run there shows the run that's going rather than starting a second one. To reach a container's dev server from your Mac, forward its port. See [Port forwarding](/workroom/docs/remote/port-forwarding.md). ## Quick Terminal The Quick Terminal is a plain shell in your home folder, in a small window of its own. It is not part of any workroom. - Press ⌥§ from any app to show it, and press it again to hide it. Hiding keeps the shell and its scrollback. - You can also open it from **File ▸ Quick Terminal** or the Quick Terminal button in the title bar. - ⌘W or the red button closes it and ends its shell. The next time you open it, you get a new shell. The ⌥§ hotkey is on while **Settings ▸ General ▸ Global show/hide hotkey (⌘§)** is on. The same switch controls the ⌘§ show and hide hotkey. See [Settings](/workroom/docs/app/settings.md#general) and [Splits and windows](/workroom/docs/app/splits-and-windows.md#show-or-hide-workroom-from-anywhere).