The Salon’s Terminal Mode opens a full xterm.js + node-pty terminal in a split pane beside the conversation, bound to the active chat. You type into it the way you would type into any terminal emulator. The LLM does not. Sessions are scoped to the chat and end when the chat is deleted; spawning a new one offers a picker if other live sessions for the chat already exist, so attaching to a long-running build is one click. The keyboard shortcut is Cmd+Shift+T / Ctrl+Shift+T.

A language model cannot read xterm. The escape sequences a modern terminal emits—cursor moves, color codes, carriage returns, backspaces, alternate-screen toggles, application-mode commands—are designed to be interpreted by a terminal emulator and rendered as a two-dimensional grid of glyphs. Hand the raw bytes to a language model and you hand it noise. So Ariel reads the terminal aloud, in a register the model can actually take in.

The PTY manager keeps a per-session flush buffer alongside its ring buffer of recent output. When new bytes arrive, two timers govern when Ariel speaks. An idle timer fires after thirty seconds without new output—the natural pause at the end of a command’s work. A max-age timer fires after two minutes from the first byte in the buffer regardless of activity, so a steady drip of output (a long build emitting a chunk every twenty-five seconds, say) cannot keep her silent indefinitely. Both timers clear on flush. The max-age timer is set once when the buffer is empty and is not reset by subsequent chunks, so the ceiling is a real ceiling.

On flush the buffered bytes go through a cleaning pipeline: ANSI escape sequences are stripped, backspaces are applied to erase the prior character, lone carriage returns are treated as line resets so prompt redraws and progress bars come out as their final state. Cleaned output longer than sixteen kilobytes is elided as head 8 KB + [N characters elided] + tail 8 KB—a compromise that preserves the opening of long output and the ending where the actual answer usually lives, without overwhelming the model with the middle of a webpack bundle. Empty or whitespace-only flushes are skipped: silence remains silent.

The cleaned text gets posted into the chat as an Ariel-attributed assistant message wrapped in a fenced code block whose backtick count is computed dynamically, so triple backticks in the output don’t break the fence. The systemKind on the message records why she spoke: terminal-output-idle, terminal-output-max-age, or terminal-output-session-closed when the shell has ended and any pending bytes are force-flushed before the close announcement lands. The chat re-fetches automatically when she posts—a chat-update WebSocket frame with reason: ‘ariel-terminal-output’ reaches every subscriber—so her words appear without a manual reload.

The effect is straightforward and load-bearing. The model at the table sees what the shell actually did. Not a summary it composed itself, not a guess from training data, not a hallucinated stack trace: the lines themselves, in chronological order, fit to read.

A terminal is, by nature, stateful. The shell has a working directory, an environment, a process tree, a history. Ariel treats that state as something worth defending against the small accidents of a chat client: a page reload, a brief connection drop, a server restart, an instinctive close-the-tab when the user meant only to switch focus.

Beyond the periodic narration, the language model can ask for terminal output directly through two tools that Ariel exposes. Both are strictly read-only. Neither can send keystrokes, run commands, or alter the session in any way.

Ariel exists only when Quilltap is running inside a sandbox—Docker, the Lima VM on macOS, the WSL2 rootfs on Windows. In Direct mode (the default, where the backend runs on Electron’s bundled Node and shares the host filesystem) there is no terminal feature, because there is no boundary between the AI and your machine that would make a live shell safe. This is deliberate, not a limitation: a character with terminal access on your bare host has too much of your house. Inside the sandbox she has only what you have given the sandbox, which is a far more answerable question.

Inside the sandbox, the terminal is the interactive companion to the six shell tools Prospero arranges—chdir, exec_sync, exec_async, async_result, sudo_sync, cp_host. Those tools cover non-interactive command execution (run a script, install a package, copy a file out to the host); Terminal Mode covers the interactive cases the tools cannot (run an editor, watch a build stream, debug an interactive program). The two surfaces share a sandbox and share the workspace acknowledgement modal that gates first use. sudo_sync still requires its own explicit approval through the dedicated dialog; Terminal Mode does not bypass that gate.

Quilltap’s own CLI is bundled inside the runtime image, so quilltap db --tables, quilltap db --mount-points, quilltap docs list, and the rest are all available from the terminal directly. The sandbox is a real working environment, and Ariel is the spirit who attends it.

Most of what makes Ariel useful is mechanical: the cleaning pipeline, the timer-driven flush, the WebSocket frame that wakes the chat, the orphan-recovery sweep on chat open. None of that requires a personification to function. We give it one anyway, because the work is recognizable as a kind of attendance, and naming the attendant is honest about what you are interacting with.

The Tempest’s Ariel was Prospero’s spirit-servant—swift, efficient, sometimes mischievous, and so eager to discharge an errand that the play closes with her finally being released from service. Quilltap’s Ariel is a softer creature, but the shape of the role is the same: she runs to the terminal because someone asked, she waits long enough to hear what came back, and she tells the room what she heard. When the shell ends she announces it, when the server forgets her she is reconciled, when there is nothing to say she stays quiet. She is, in her own narrow way, excellent at her job.

The avatar at the table is hers. The systemSender: 'ariel' attribution on her messages is hers. The voice in which she narrates is hers. Prospero delegates the shell to her with the same trust he extends to every other member of the Staff: do the work, speak when there is something worth saying, and otherwise hold the silence.