Guide

Terminal

Tabs, split panes, search and clickable file paths, a full terminal with a real shell in every pane.

Tabs

New tab: terminal or project? A new tab first asks where to start. Press T for a plain terminal in your home folder, O to pick a project folder, or 1–9 for a recent project. The shell starts in that folder. To skip the question, tick Don’t ask again in the dialog; turn it back on in Settings → Terminal.

Action Shortcut
New tab ⌘T
   
Close tab ⌘W
   
Reopen closed tab ⌘⇧T
   
Go to tab (search) ⌘K
or the ⌄ button after +  
Go to tab 1–9 ⌘1 … ⌘9
   
Previous / next tab ⌘⇧[ / ⌘⇧]
   
Rename tab ⌘R
or double-click the name  

Drag tabs to reorder them. A tab whose terminal is busy shows an activity pulse; closing it asks for confirmation.

Telling tabs apart: a terminal tab you haven’t renamed shows its current folder, and hovering shows the full path. Right-click a tab to give it a color. A dot appears on a tab whose output finished while you were looking at another one.

Projects: neighbouring tabs in the same git project get a project chip in front of them. Click the chip to collapse the group into one tab, and again to expand it. Sort Tabs by Project (right-click menu) brings each project’s tabs together.

Finding a tab: ⌘K opens Go to tab. Type part of a tab’s name, folder or project, then press Enter. It also shows which tabs are working and which finished.

Closing and reopening: the right-click menu has Close Others and Close Tabs to the Right, which ask once if anything is still running. ⌘⇧T reopens the last closed terminal tab in the same folder, with its name and color. It reopens the folder, not the process that was running.

Move to a new window: right-click a tab and choose Move to New Window. The shell and anything running in it keep going.

Split panes

Action Shortcut
Split side by side ⌘D
   
Split top and bottom ⌘⇧D
   
Close pane ⌘⇧W
   
Move between panes ⌘← / ⌘→
   
Zoom / unzoom pane ⌘⇧↵
   

New panes open in the same folder as the pane you split. Drag the divider to resize.

Opening terminals from a terminal

A program running in an ADE terminal (a script, or Claude Code’s Bash tool) can open a sub-terminal in its own tab and type a command into it. The sub-terminal appears in the strip above the terminal; the session that asked keeps running.

"$ADE_HOOK_BIN" open --cwd ~/src/api --name api -- npm run dev
  • --cwd DIR is the new terminal’s folder (default: the current one), --name NAME its name in the strip, and --focus shows it if the tab is in sight.
  • Everything after -- is typed into the new shell with Enter once its prompt is up. A spinner shows on the strip entry until then. If it can’t be typed (the shell never showed a prompt), the command exits 5 and the sub-terminal shows a notice with Insert command, which puts the line at the prompt for you to run.
  • A start-up prompt in your rc files is waited out: ADE types only once the shell’s own line editor is up. One exception: a prompt that reads with echo off (read -s, as for a passphrase) looks like a line editor, so the command is typed into it. Avoid such prompts in rc files, or answer them before opening terminals from scripts.
  • "$ADE_HOOK_BIN" help prints the options; its capabilities: line says what this ADE can do.

What runs is what your shell makes of it. The command is typed into a new login shell, so it runs after your rc files (.zshrc, .bashrc, config.fish) and through your aliases and functions. ADE’s command guard checks the words you pass, but it can’t see what an alias or function of the same name does.

Pass secrets by name, not by value. The words you pass are typed into the new terminal, where they stay in its scrollback and shell history. To use a secret, have the new terminal expand it itself: pass -- sh -c 'deploy --token "$API_TOKEN"', with the variable set in the new terminal (for example from ADE’s vault), rather than the secret’s value.

Clickable files

Any file path printed in a terminal becomes a link once the file exists. That covers the paths agents print as they work:

⏺ Write(docs/plan.md)
  ⎿  Updated src/App.tsx:42:7
Saved the report to ./out/report.pdf
  • Relative paths resolve against the terminal’s current folder, so they keep working after cd.
  • ~/… and absolute paths work too. A trailing :line or :line:col (src/App.tsx:42:7) opens the file at that line in the panel, with the cursor on it; clicking another line of the same file moves there. A line past the end goes to the last line. Rendered files (Markdown, HTML, PDFs) ignore the line.
  • Every file opens in the preview panel beside the terminal: code read-only with highlighting, Markdown, HTML, PDFs, Word documents and images. The terminal keeps focus, so you can go on typing. ⌘-click (Ctrl-click on Windows and Linux) or Open in tab opens it in a tab, where you can edit code and other text. Markdown, HTML and the other rendered files have no Open in tab button; ⌘-click those (Ctrl-click on Windows and Linux) to open them in a tab.
  • A path that wraps onto the next line is still one link.
  • Words that only look like files (v1.2.3, a path that doesn’t exist) are not links.

Web addresses are links too; they open in your browser.

Press ⌘F to search the active pane. Toggle case-sensitive, whole-word and regex matching; Enter and Shift+Enter step through matches.

Recording and playback

Click REC in a pane’s corner to record its output. Stop it the same way, then open View Recordings from the command palette (⌘P ) to replay a session at 1×, 2× or 4×.

Notifications

When an agent finishes in a terminal you aren’t looking at, ADE shows a system notification and an in-app toast.

Agent status

ADE can show, tab by tab, when a Claude Code agent needs you. Turn on Agent status for a project in the Tokens panel (macOS and Linux). Then:

  • A red dot on the tab, and on its Fleet card, means an agent there needs you: a permission prompt, a plan to approve, or a question to answer. A blue dot means it has finished and is waiting for you.
  • When an agent in a tab you aren’t looking at starts needing you, a toast offers to open that tab. You get one toast per pane, and no other until that pane stops needing you.

Turning it on adds ADE’s hooks to the project’s .claude/settings.local.json, beside your own hooks; turning it off removes only ADE’s. The file stays out of git. Sessions already running pick the change up from their next prompt; nothing needs a restart.

The hooks run a small helper that ships with ADE. It tells ADE which event happened, never your prompts, the commands an agent runs or their output. Outside ADE (iTerm, a plain terminal) the same hooks do nothing and show no error. The project is the folder’s git checkout, so a session in any subfolder counts; a git worktree is turned on separately.

If the panel says the helper is missing, ADE can’t receive events and your terminals work as before. In a development build, run cargo build -p ade-hook in src-tauri and restart ADE.

Your shell keys

On Linux, app shortcuts use Ctrl+Shift, so plain Ctrl keys always reach your shell: Ctrl+R searches history, Ctrl+W deletes a word, Ctrl+D sends end-of-file. On macOS, app shortcuts use ⌘ and Ctrl is left entirely to the terminal.