All pages

Docs · Right-sidebar surfaces

Prompts

Availability: macOS · cloud workspace (list_prompts / save_prompt).

The Prompts tab (right sidebar) is a library of saved prompts — short named recipes you can paste into the terminal, run immediately, queue, or send to the agent.

Use it for the prompts you reach for repeatedly: "review the diff," "summarize this log," "deploy preview to staging," "write a commit message from the staged changes."

Anatomy of a saved prompt

Field What it does
Name Display label, matched by the sidebar's search field
Body The prompt text. May reference {{variables}} (see below)
Trigger Optional keyword — type it in any terminal and it expands in place
Tags Free-form labels; become filter chips at the top of the list
Project Optional scope — a scoped prompt only shows while that project is active

Ways to run one

  • Click a row — pastes the body into the focused pane without pressing Return, so you can edit before running.
  • Play button — pastes and presses Return immediately.
  • ⌘P prompt menu — pops your saved prompts as a menu at the terminal cursor; picking one pastes and presses Return in that pane. Hold ⌥ for paste-only.
  • Queue button — appends the body to the focused pane's command queue (honors the Queue tab's auto-run setting; see Queue).
  • Send to Agent (right-click) — sends the body as a new user turn in the agent sidebar.
  • Trigger keyword — type the trigger followed by a space (or other boundary) in a terminal and the keyword is replaced by the expanded body, text-expander style. A brief HUD shows what was inserted.
  • Pinned preset — the pin above the agent input drops one prompt into the composer for you to review and send.
  • Slash palette — typing / in the agent composer surfaces your saved prompts alongside the built-in slash commands.
  • Assign Shortcut… (right-click) — bind a keyboard chord that sends the prompt straight to the agent.

Prompts can be reordered by drag, stuck to the top of the list, or pinned as a one-click preset above the agent input. A "Most used" section tracks what you actually run.

Variables

Bodies may reference {{variables}} that resolve at invocation time: {{cwd}} (alias {{pwd}}), {{branch}}, {{selection}}, {{visible}} (visible terminal contents), {{title}}, {{clipboard}}, {{date}}, {{time}}, {{datetime}}, {{home}}, {{user}}.

Any other {{name}} is a custom variable — the name alone defines it; there are no defaults or descriptions to declare. Firing such a prompt from any entry point above (click, play, queue, ⌘P, a typed trigger, a custom shortcut, the pinned preset, the slash palette) opens the run sheet first: it previews the resolved text, gives you a field per custom variable, and offers every verb (paste, run, queue, send to the agent, or — from the agent tab — insert into the draft), with the verb you started from as the Return-key default. Fields start empty; values you have used before appear as chips under the field. An Auto-fill button asks your current agent model to propose values from the terminal context and only fills fields you have left blank.

Built-ins that have no value in the focused pane (nothing selected, no git branch, blank clipboard) stay as literal {{…}} so you notice; the sheet lists which ones and why, since there is no field for them — select something or switch panes, then reopen. Names are case-insensitive and may contain letters, digits, _ and -; anything else between braces, such as {{key:NAME}}, is left alone.

Watched folder

Point the gear menu's Watched folder at any folder on disk and every .md / .txt / .prompt file in it appears as a read-only prompt — the filename becomes the name, and an optional #trigger: foo first line becomes the trigger. TRMNLY watches the folder and reloads on change, so prompts stay version-controllable and shareable.

Packs and libraries

The gear menu has Import pack… / Export pack… for .trmnlypack files — a JSON bundle of your local prompts for backup or sharing between Macs. Browse packs… opens the library browser, where subscribing to a bundled prompt pack adds its prompts read-only under a collapsible folder heading.

The TRMNLY pack holds 100 prompts that each put TRMNLY's own tools to work: the terminal and its panes, the in-app browser, worktrees, the Tasks board, chat, the fleet, ports, Docker, saved connections, schedules, runbooks and tab monitors. Each prompt names the tools it expects, so it runs the same in the agent sidebar and in a Claude Code session connected over MCP. It needs a hosted model: a local model is offered only about fifteen tools (see Local models), so most of the pack can't run on one. Filter it by tag, or, once subscribed, type a trigger such as t:orient, t:fix, t:preview or t:next in any pane. Prompts that need a value from you (a port, a PR number, a card) have no trigger and open the run sheet instead.

Agent tool surface

The agent has two read-only, no-approval tools: list_prompts (enumerate names, triggers, and tags, with an optional filter) and run_prompt (fetch a prompt's body by id, name, or trigger — despite the name it fires nothing, and the body comes back with {{variables}} unexpanded; the agent decides what to do with the text).

list_prompts also takes format: "json", which answers with each prompt's id, body, one-line preview, tags, pack, use count and last-used time — what the iOS app's Prompts tab shows — and record_use: "<id>", which counts a use the way the sidebar's ▶ does. The iOS app sends that after it sends or queues a prompt, so Most used and Recent today agree between the phone and the Mac.

save_prompt (no approval, add-only) appends a new local prompt from name and text (the cloud box's title / body also work), with optional tags and project_id; it never edits or replaces one. The iOS app's Duplicate uses it to make a variant of a prompt. In the app, the bookmark button in the agent input row saves the current draft as a prompt.