DocsScreens

Terminal

The terminal your agents run in: one main terminal per tab for your agent, child terminals for everything else, and sessions that outlive the app. To start an agent, see Run an agent.

The terminal card

Press ⌃` (Toggle Terminal) in a repository tab to open the terminal as a card over the tab, in its worktree.

Press it again, or the yellow button (Hide Terminal), to hide the card; clicking the agent tile on the tab brings it back. Title bar buttons dock the card at the bottom or on the right, and the pin (Pin Terminal) makes the view shrink to make room for it.

Main and child terminals

The first terminal in a tab is its main terminal, the seat for your agent and the only one recorded. For a dev server or a quick check, open a child terminal with Open Terminal (⌃⇧`). It appears as a chip under the card, named after its command, such as pnpm dev.

  • Click a chip to expand it. Minimize folds it back, still running; Exit ends it.
  • If its command listens on a port, the chip shows it, like :3000↗. Click it to open it in your browser.

Status badges

Each terminal shows its most urgent badge in the title bar, on its chip, and on the agent tile. Hover over one to read it.

  • Bell, or a notification the program sent.
  • A check mark: the running command finished.
  • Exited: the shell ended on its own.
  • Session ended: something outside the shell ended it, such as another process.

The agent tile also shows New output as a dot, and an hourglass with ? when the program may be waiting for input, an estimate. Its tooltip says whether Claude Code is Working or Idle.

Warnings

When Claude Code finishes a turn, a warning line may appear under the title bar: a file your agent changed usually changes with another one it left untouched. Open opens that file in Files; × ignores it until you commit.

The agent tile also shows the main terminal's memory use. The number turns orange when it's well above usual for this worktree, or when macOS is short on memory and this terminal uses the most. Whaatcher never stops anything for you.

When you quit Whaatcher

Quitting doesn't stop your terminals, and neither does a crash. If something is running, Quit Whaatcher? asks first. When you reopen Whaatcher, each session reattaches in its tab with its screen and scrollback; if one ended unexpectedly meanwhile, its tab tells you why. Restarting your Mac or logging out ends every session.

End a session

  • The red button (Close Terminal) ends the main terminal and its child terminals, asking first if something is running.
  • Typing exit ends a shell. If the main terminal ends while child terminals remain, click Restart Terminal on its dimmed screen for a new one.
  • Closing the tab ends its terminals too.