Terminal
A full-featured terminal with split panes, smart word selection, Cmd+click navigation, and keyboard shortcuts tuned for agent workflows.
Every Scape session runs in a full-featured terminal built on a custom SwiftTerm fork. It's designed for agent-driven coding workflows — with split panes, smart text selection, and keyboard shortcuts that keep you productive alongside your AI agents.
Split panes
Press Cmd+D to split the terminal into two side-by-side shells (max 2). The split panes run plain shells — not the coding harness — so you can run tests, check git status, or monitor logs alongside your agent.
- Closing the last pane collapses the split.
- Collapse/expand preserves running processes.
Smart selection
Double-click a word to select it — the selection automatically expands to include full URLs and file paths, treating ., /, :, ~, @, and other path characters as part of the word. Option+click enables rectangular (block) selection.
Cmd+click navigation
- URLs — opens in Scape's browser companion.
- File paths — opens in Scape's code editor (line numbers supported, e.g.
src/app.ts:42).
Keyboard shortcuts
| Shortcut | Action |
|---|---|
| Shift+Enter | Newline in the harness prompt |
| Ctrl+X Ctrl+E (or Ctrl+G) | Edit your prompt in an editor (Claude sessions) |
| Cmd+Delete | Kill from cursor to start of line |
| Cmd+D | Split into a second pane |
| Cmd+1–9 | Jump to session by index |
| Cmd+] / Cmd+[ | Next / previous session |
| Cmd+= / Cmd+- / Cmd+0 | Zoom in / out / reset |
Prompt editor (Ctrl+X Ctrl+E)
Drafting a long prompt in the one-line composer gets painful. In a Claude session pane, press Ctrl+X Ctrl+E (or Ctrl+G) to open your current prompt draft in a real editor.
By default the prompt opens as a tab in Scape's file editor (the code editor):
- Edit the prompt with everything the editor gives you — multiple lines, Vim mode, word wrap.
- Close the tab to send the text back to Claude. A banner above the editor reminds you, with an explicit Send to Claude button that does the same thing.
- ⌘S just saves — it does not send.
- Your text is sent back exactly as typed.
Using an external editor instead
Open Settings → General → Prompt editor (Ctrl+X Ctrl+E) and switch the picker from File editor to External editor, then enter an Editor command:
- Terminal editors (
vim,nano, …) run inside the session pane itself. - GUI editors need a flag that makes them block until the file is closed — e.g.
code --wait. - The command is split on spaces, so an editor path containing spaces can't be expressed.
- Leave the command empty to fall back to your shell's
$VISUAL/$EDITOR.
Appearance
The terminal automatically follows macOS light/dark mode. Font is configurable via Settings (IBM Plex Mono by default). Font zoom scales from 13pt base in steps from 0.75× to 1.5×. Scrollback is 10,000 lines.
Session states
Each session tab has a lifecycle:
| State | Meaning |
|---|---|
| Preparing | Setting up the session (creating worktree, etc.) |
| Ready | Harness is running and accepting input |
| Failed | Setup failed (shown as error state in the tab) |
| Exited | The harness process has exited |
| Harness unavailable | The configured harness CLI isn't installed |