> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/developer-features/terminal-window.md).

# Terminal Window

Run a Ghostty-powered terminal inside Nimbalyst. Create multiple terminal sessions in your workspace directory that survive app restarts.

Nimbalyst includes a Ghostty-powered terminal, so you can run commands in your workspace without leaving the app. You can open multiple terminal sessions, each running independently, and their output persists across app restarts. The terminal sits alongside the visual editors rather than replacing them; see the [developer tools page](https://nimbalyst.com/features/developer-tools/). The terminal requires [Developer Mode](/developer-features/turn-on-off-developer-mode.md).

<figure><img src="https://562749618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVUeHZHlFlZrZt02syRC%2Fuploads%2FWrUDs581brz2Zot1q077%2FTeminals.png?alt=media&amp;token=bda408ef-32f2-4d09-b7b8-6b2b0ba0233f" alt="Nimbalyst in Agent mode with the terminal panel open along the bottom, showing a shell prompt in the workspace directory"><figcaption><p>The terminal panel opens along the bottom of the workspace, with a shell running in your project directory.</p></figcaption></figure>

### Opening and Closing the Terminal

Open and close the terminal panel from the terminal icon in the left nav, or press **Ctrl+\`**.

Add more terminals by clicking **+** to create a new terminal tab.

<figure><img src="https://562749618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiVUeHZHlFlZrZt02syRC%2Fuploads%2FEJWRzBAuLBf2xytN96AR%2FMultiple%20Terminals.png?alt=media&amp;token=83767d38-9280-44f3-9c84-1d6cea089a68" alt="Three terminal tabs across the top of the terminal panel, with a plus button to add another"><figcaption><p>Each terminal tab is an independent shell session; click + to add another.</p></figcaption></figure>

### Using the Terminal

Type commands and press Enter to run them. The terminal works like any standard shell:

* Run commands: `ls`, `git status`, `npm install`, and so on
* Navigate directories: `cd folder`
* Use tab completion (depends on your shell)
* Access command history with the up and down arrow keys

#### Shell Detection

Nimbalyst automatically detects and uses your system shell:

| Platform | Default Shell       |
| -------- | ------------------- |
| macOS    | zsh (or bash)       |
| Linux    | bash (or zsh, fish) |
| Windows  | PowerShell (or cmd) |

#### Scrollback and History

Terminal output is preserved, up to 500KB per terminal. When you reopen a terminal session, previous output is restored, you can scroll back through it, and a new shell process starts in the same directory.

Your shell's own command history (up and down arrows) also persists across sessions. Fish shell and Windows cmd have limited history persistence.

#### Process Management

* **Running processes**: commands run until they complete or you stop them with Ctrl+C
* **Shell exit**: if the shell exits, press Enter to restart it
* **App quit**: when you close Nimbalyst, all terminal processes are stopped and scrollback is saved

### Terminals in Worktrees

Each [worktree](/developer-features/worktrees.md) has a dedicated terminal button, so you get a terminal scoped to that worktree's directory, with its own persisted scrollback.

### Tips

* Each terminal starts in your workspace folder
* Copy and paste with your normal system shortcuts (Cmd+C/Cmd+V on Mac, Ctrl+C/Ctrl+V on Windows/Linux)
* Clear the screen with `clear` or Ctrl+L
* Environment variables set during a session do not persist to new sessions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nimbalyst.com/developer-features/terminal-window.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.