Quick Replies (manage your snippet library)
How to build and manage your library of saved quick replies: the sidebar virtual project that holds quick replies, dividers and folders, the Settings tab that owns the AI-suggestion toggles, what happens when a snippet fires in a session, and the three library-level actions — Export to a JSON file, Share as a public link, and Import — whose merge only ever adds.
On this page
What it is
Quick Replies is a dedicated virtual project in Omniscio that holds your library of saved, reusable quick replies — the ones you can drop into any session's composer via the Alt+S picker, wire to an Auto-reply rule, or cite from an Automation's auto_respond action. Each entry is one of three types: a quick reply (a label + body text + an optional auto-submit flag), a divider (a label-only row used to visually group items — purely visual, no group semantics), or a folder (a nameable container that can hold quick replies, dividers, and other folders — unlimited nesting depth). Folder names may repeat freely; quick-reply labels are globally unique across every folder.
Where to find it
Quick Replies appears in the sidebar alongside the other Integrations virtual projects (Automations, Recipes, Skills, etc.). Opening it shows a sub-sidebar with three tab rows and a main panel whose contents swap based on the active tab:
- Settings — the per-feature toggles: AI Suggestions on/off, the Suggestion Model dropdown, Quick Reply Button visibility, Quick Reply Message text, Quick Reply Hotkey. This tab is the single home for these settings as of 2026-05-20. (Prior to that, an equivalent panel also lived under main Settings → Quick Replies; the panel was removed and right-click "Edit in Settings" on a snippet now routes into this VP tab, switches to Quick replies, and opens the inline editor on the target row.)
- Quick replies — your quick-reply + divider + folder library: a sticky toolbar pinned at the top of the panel ("Quick replies" title + count, with + Folder, + Divider, and + Add reply buttons that prepend new items to the current level, plus the library-level Export, Share, and Import actions), a draggable tree with per-quick-reply usage counts, folder rows that show
Name (direct/total)counts (direct children vs. all descendants) and a chevron to collapse/expand (state persists across restarts via thecollapsedQuickReplyFolderssetting), an inline editor that expands when you click a row, and a single collapsible + Add quick reply button at the bottom that reveals an inline editor when clicked (saving from there appends a new quick reply to the bottom of the list). - Sessions — your AI edit sessions for this project. Click a session row and the SessionPanel takes over the entire right pane; close the session to return to the tab list.
The active tab persists across project switches and app restarts (stored in localStorage under the key amc.quickRepliesTab). This is the authoring surface; for the composer-side UX (Alt+S picker, Alt+1/2/3 AI chips, Alt+Z Zap button), see use-quick-responses.md.
How it behaves
How to use it
- Open it. Click Quick Replies in the left sidebar's Integrations group — it lives next to Automations.
- Switch tabs. Click Settings, Quick replies, or Sessions in the sub-sidebar. The active tab persists across project switches and app restarts.
- Settings tab. Flip AI Suggestions to enable/disable AI-generated reply pills (Alt+1/2/3) for sessions, SMS, email, and Telegram. When on, a Suggestion Model dropdown appears (Haiku is fastest/cheapest). Quick Reply Button controls the lightning-bolt Zap button next to Snippets; with it enabled you also get the Quick Reply Message text field and Quick Reply Hotkey binding (default Alt+Z). This tab is the only home for these toggles — the legacy duplicate panel under main Settings was removed on 2026-05-20.
- Quick replies tab — create a quick reply. Two entry points. From the top toolbar: click + Add reply to reveal an inline editor between the toolbar and the list — saving from here PREPENDS the new quick reply to the top of the list, with Cancel to dismiss. From the bottom of the list: click the dashed-border + Add quick reply button to reveal the same inline editor — saving from here APPENDS to the bottom. The editor leads with just the basics — the Label (shown in the picker and sidebar row — must be globally unique), the Body textarea (the text that gets sent), and the Auto-send when selected toggle (with it on, picking the quick reply sends immediately; with it off, the text lands in the textarea for you to edit before hitting send). Everything fancier is tucked under a collapsible Advanced options disclosure, collapsed by default when adding a new reply so a basic user isn't overwhelmed — and auto-expanded when you edit a reply that already uses any advanced option, so your existing config is never hidden. Advanced options groups into References (the Prepend other quick replies chip row, the Append other quick replies chip row, and a live What gets sent preview that only appears when at least one prepend/append is configured) and Behavior (a Number key pin, an engine & model pin, and the "per-snippet effects" toggles described in the next subsection). The Save / Cancel / Delete footer is pinned and always visible. Ctrl/Cmd+Enter saves from anywhere; plain Enter saves from any single-line field.
- Quick replies tab — edit, reorder, delete, add dividers + folders. Click any quick-reply row to expand it inline into the same editor pre-filled; change fields and Save, or hit the trash icon to remove — removal happens at once, and the toast it raises carries Undo with a Ctrl+Z hint, so press Ctrl+Z (or the toast's Undo) to restore the quick reply exactly — same list position, "used X times" count, folder, and tags (it is re-inserted verbatim, not re-created as a fresh copy). Click Cancel to collapse without saving. Drag rows by their grip handle to reorder — every row type (quick reply, divider, and folder) is both draggable and a drop target. While dragging, hover near the top or bottom edge of a target row to insert above or below it; the accent hairline indents to the depth where the item will actually land, so a drop inside a folder shows an indented line while a drop outside at the parent level sits flush at the left margin — the fix for the old ambiguity at a folder's bottom edge where in-folder and out-of-folder drops painted an identical full-width line. On a folder row, hover the middle band to drop inside that folder (the whole row gets an accent-tinted fill). Dropping below an expanded folder inserts as that folder's first child (the gap visually belongs inside); dropping below a collapsed folder behaves like any other sibling-after insertion. A drop zone at the very bottom of the list — shown only while you're dragging — always drops at the top level (at the end), so you can pull an item out from under a folder that's the last row. Cycles are prevented automatically: dropping a folder onto itself or any of its descendants surfaces a toast and skips the move. The list keeps scrolling while you drag — spin the mouse wheel, or drag near the top/bottom edge to auto-scroll — so reordering across a long list never means dropping the row just to scroll. With a mouse or trackpad, just press a row and drag. On touch, press and HOLD a row for about half a second to pick it up, then drag — the same press-and-hold gesture that reorders projects, tasks, bookmarks and docs; a plain swipe (a finger that moves before the hold lands) still scrolls the list as normal. The up/down arrows on each row stay a one-tap alternative on any device. Use the right-click context menu's Move to folder… option for a click-driven alternative to drag-into. Insert a divider via + Divider, or a folder via + Folder — both prepend to the top of the current level. Delete folder opens a two-button dialog: Delete folder AND contents (cascades — removes every quick reply, divider, and subfolder inside) or Move contents up one level (promotes children to the folder's parent; auto-rename collisions like
"PR description (2)"). - Sessions tab — open or spawn an AI edit session. Click any existing session row to take over the right pane with the full SessionPanel; close the session (X button) to return to the list. To spawn a new session, use the + button in the sidebar's session rail (same as any other project). Omniscio starts a Claude session pre-seeded with: (a) this page, (b) your current snippet inventory as JSON, (c) a REST cheatsheet for
/quick-replies(list),POST /quick-replies(create),/quick-replies/:id, and/quick-replies/reorder, and (d) a short-lived in-app token that the Claude-Code process uses to write straight into the library — writes authorized with that token skip the CLI approval inbox and land as approved immediately. Ask it to "add a snippet that thanks the sender and confirms I'll reply tomorrow" and watch the Quick replies tab update. - Use what you built. Inside any session composer, press Alt+S to open the quick-reply picker. The picker opens at the root level; click a folder row to drill in with a horizontal slide animation. A top bar shows a back arrow and a clickable breadcrumb (
Root › Email › Replies) — click any segment to jump back to that level. Typing in the search box auto-flattens results across every folder, prefixing each row with its folder breadcrumb so you can see where the match lives. Arrow keys move between visible rows and Enter inserts the highlighted item. AI suggestion chips (Alt+1/2/3) and the Zap button (Alt+Z) stay flat — they never drill into a folder. See use-quick-responses.md for the full composer-side UX including the AI-suggestion chips and the Zap button. Attachments (screenshots, PDFs, text docs) attached to the composer ride along on auto-submit quick replies and Zap sends — see use-quick-responses.md "Attachments ride along" for the contract and chat-attachments.md for the underlying delivery pipeline.
Per-snippet effects (Advanced options → Behavior)
The Behavior group inside Advanced options holds three opt-in effect toggles plus an auto-apply tags row (the Auto-send toggle moved out to the always-visible basics). Each one persists on the snippet itself, so updating the override text is a single edit and any subsequent snippet send picks it up:
- Set session title from this quick reply — when this snippet is the first user message in a fresh session, Omniscio sets the session's title to the configured text (or the snippet's label if the field is left blank). This applies wherever you fire the saved reply as the first message — a session's Alt+S picker, Quick Launch, or the mobile new-session composer; it does not apply when you type the reply's text by hand (that's just a typed prompt with no reply identity). The AI title-generator may still rename later — this is a starting title, not a lock. Two nested checkboxes appear when this toggle is on: Append usage count adds the running number of times this quick reply has fired — including the current send — as
#150, and Append timestamp adds the local date and time as· 2026-05-30 14:32. With both on, the title readsFull Local Git #150 · 2026-05-30 14:32(count first, then timestamp). These suffixes apply only to titles set by this quick reply; AI-generated titles and manual renames are never touched. - Override Plain Speak "Latest" with this quick reply — when you send this snippet, Omniscio waits for the agent's reply to that turn and stamps the configured override text (or the snippet's label if blank) onto the final non-aside agent message of that turn. From then on, that one historical message renders its
## Latestline as the override text instead of the model's recap; the other four sections of the rewrite (TLDR / Recommended Action / Response / Questions) are unchanged. The stamp is sticky and per-message — it stays on that message permanently, even after you scroll back days later. Subsequent agent messages (the next turn, or any later turn) render the normal Plain Speak rewrite with no override. If Plain Speak didn't run for that turn (paused, capped, master-off, per-session off, short message), no override is shown — you see the original agent message. - Allow Inbox Pilot to auto-send this reply — gates whether the AI classifier can pick this snippet as an auto-respond reply. When on, you can also fill an optional Hint for the classifier (e.g. "acknowledge thanks", "ask for more details") so the classifier knows when this snippet is the right pick.
- Auto-apply tags — pick up to 5 library tags inside the snippet editor's "Auto-apply tags" section. Each time the snippet fires (Alt+S picker, Alt+Z Zap button, or an Auto-reply / Automation
auto_respondaction), Omniscio attaches those tags to the receiving session. The picker shows every tag in your library — global and project-scoped alike — because tag application happens unscoped at send time, so a tag scoped to one project still binds to a session in another project. Tags appear as chips on the snippet's row in the list (up to 2 visible, with "+N" overflow). Sessions cap at 10 tags total — once a session is at that cap, additional tags silently fail to attach (the message still delivers normally). Soft-deleted tags also silently no-op so a stale snippet→tag binding doesn't break sends; the binding gets cleared the next time the snippet is saved.
Reusing other quick replies via prepend/append (Advanced options → References)
The References group inside Advanced options includes two chip rows — Prepend other quick replies and Append other quick replies — for citing existing quick replies as shared headers/footers. The picker for each row excludes (a) the snippet currently being edited (no self-reference), (b) any quick reply already selected on the same row, and (c) dividers and folders (they have no sendable body). Each row caps at 5 entries; the + Add button visibly disables once you hit the cap. Removing a chip is a single-click × on the chip. The two rows are independent, so you can prepend up to 5 and append up to 5 on the same snippet.
When the snippet fires, Omniscio sends the final text by concatenating, in order: each resolved prepend body, the snippet's own body, then each resolved append body — joined by single newlines. So prepend = [greeting], body = "Thanks for the heads-up.", append = [signoff] produces:
Hi there!
Thanks for the heads-up.
— Bot
A live What gets sent preview renders just below the chip rows whenever at least one prepend or append is configured, so you can see the exact expanded text before saving. The preview only appears when there's something to preview — for a bare body with no refs, the body IS the final text and a duplicate preview would just be noise.
Expansion is fail-open and shallow on purpose:
- A reference whose target snippet was deleted is silently skipped at send time — no error, no blank line in the output. Deleting a referenced snippet never breaks the editor of others that referenced it. This matches the same reader-time skip pattern used by
snippet_tags. - A reference whose target body is empty is also skipped — no stray blank line between prepend and body.
- One level only. If snippet A prepends B and B prepends C, sending A emits
B-body\nA-body— notC-body\nB-body\nA-body. Recursion is out of scope on purpose; one level is the simple "no runaway expansion at fire time" rule. - No self-reference. Even if a stale id somehow points the snippet at itself, the helper skips it instead of infinite-looping or emitting the body twice. The picker also blocks self-selection at the UI layer.
This makes expansion safe to use from every fire path — the manual Alt+S picker, the Alt+Z Zap button, Auto-reply rules, Automation auto_respond actions, and the Inbox Pilot classifier all route through the same expandQuickReplyText helper. When the Inbox Pilot fires a snippet with refs, the decision row records the fully expanded text in frozen_quick_reply_text so replay is byte-equivalent to what the CLI received.
Export, share, and import the library
The Quick replies tab's toolbar carries three library-level actions — Export, Share, and Import — for moving a whole library between machines or between people. They deliberately have NO keyboard shortcuts, so a stray chord can never write a file or publish the library.
- Export writes the entire library to ONE small JSON file you pick in a native save dialog (default name
omniscio-quick-replies-<date>.json). Every quick reply, divider and folder goes in, and the folder structure is preserved via each row'sparentId. Per-machine usage statistics — how often a reply was used and when it was last used — are deliberately absent from the file. A toast confirms how many replies were written; dismissing the dialog writes nothing. - Share publishes the same library as a readable page at a public Omniscio Shares link and copies that link to your clipboard. It warns FIRST that the link is public — anyone with it can open the page — and publishes only once you confirm; the link is also listed in Shares, where it can be revoked later. The page is built from the same fresh read as the exported file, so the link and the file can never describe different libraries. Re-sharing an unchanged library returns the same link.
- Import takes either an exported file (Choose a file…) or the block pasted from a shared page (Or paste a shared library). It writes NOTHING until you confirm: it first previews exactly what it will do — how many replies, folders and dividers the source holds, how many will be added, how many are already here and will be skipped, any that will arrive under a numbered name, any tags it will create, and any pinned shortcut digits it will drop — and only Add to my quick replies applies it.
The merge is add-only and repeatable:
- It only ever ADDS. Nothing already on the machine is deleted, replaced or edited.
- A reply whose label AND text already match an existing reply of the same type is skipped, so importing the same file twice adds nothing.
- A name clash keeps both: a snippet whose label is already taken by DIFFERENT text arrives renamed
(2),(3), … after the existing one. - A pinned shortcut digit is never stolen — an arriving digit (1–9) survives only where that digit is free on this machine and no other row in the same file claimed it.
- The whole import is ONE database transaction, so a failure cannot leave half a library behind.
Both halves are also reachable from the command line: GET /quick-replies/export returns the same bundle as JSON, and POST /quick-replies/import performs the same merge. See cli-quick-replies.md.
Localization (built-in defaults)
The built-in quick replies (Red Team, Run the app, Plain English Rephrase, Interview Me, …) are language-aware. A fresh install creates only the starter set listed in FRESH_INSTALL_SEED_LABELS, and a one-time startup pass completes the library from the same catalogue — restoring whatever is missing on an install that holds none of the other built-ins (the state a reinstall leaves), and never re-adding a reply you have deleted. Each seeded default carries a hidden default_key column tying it to an i18n catalog entry at quickReplies.defaults.<key>.{label,text}; while that key is set, the picker, the settings list, the editor, AND the send path (composer + Inbox Pilot) render the reply's label and text from the catalog in the user's uiLanguage instead of the stored English. So a user running Omniscio in Spanish sees Spanish buttons and — because the whole prompt is sent in Spanish — the agent answers in Spanish. English users see no change, and nothing is visible until a non-English language is enabled (the pilot languages are gated behind unreleased-feature flags today).
File a Bug or Feature Request (fileBugOrFeature) is the reporter: one click sends an agent a complete instruction to decide whether the conversation is a bug or a feature request, write a solid report (title, what happened, numbered repro steps naming the exact screen and control, frequency, and the cost to the person), send it through the app's own local POST /feedback route, read 200 / 202 / other answers correctly, and tell the person in one line what was filed and its correlationId. It asks the person nothing. It ships on every install — fresh installs seed it, and existing installs receive it once from a one-off ledger migration — and it is deliberately opted out of the Inbox Pilot auto-reply pool, because it emails a human.
Editing adopts it. The moment you change a built-in's label or text and Save, it becomes a personal copy: the default_key is cleared (the editor sends defaultKey: null — the IPC update field is clear-only, so a client can never SET a key), the row keeps exactly what you typed, and it never re-translates. An unchanged save, a settings-only edit (autoSubmit, tags, a pin), or merely opening the editor leaves it a localized default. A translated label longer than the 50-char cap falls back to the English canonical when unchanged (the key is kept, so the catalog still localizes it).
Identity + backfill. Fresh installs get default_key stamped by the seed; existing installs are backfilled by a one-time migration that keys ONLY pristine rows — a row is keyed just when its label AND its exact text both match the frozen canonical, so any reply you had already edited stays a personal copy. That canonical list is append-only and holds every superseded revision: rewording a default's text without appending its new sha256 in the same commit silently un-keys pristine rows, dropping them to personal copies that lose localization and every future catalog update. plainEnglishRephrase has been reworded twice, so it carries three hashes. The 17 pilot locales are filled by the team's translation step and enforced when a branch is published.
The two plainEnglishRephrase rewords. 2026-07-17 — the English source went from "plain, simple English" to "plain, simple language" so its translations target the user's own language rather than literally asking for English (the button is still named "Plain English Rephrase" in English; some locales like Cebuano keep that proper name while fully translating the prompt body). 2026-08-25 — the spacing bullet stopped naming <br>. It used to end "…never use HTML tags like <br> (they show up as literal text here…)", and that ban was itself the cause: it put a vivid <br> into context on every send while the same sentence asked for vertical white space, which Markdown has no device for — so the model reached for the spacer it had just been shown and the reply rendered a literal <br>. It now reads "For spacing, use real blank lines between sections, with a heading to open each one — pure Markdown throughout." The general rule for any prompt in this app: a prohibition that spells out the forbidden token summons it — state the rule positively, and always leave the model something to do instead of the thing you banned.
The whole path routes through the shared resolver quick-reply-i18n.ts (renderer via the useQuickReplyResolver hook, main via mainT); expandQuickReplyText takes an injected resolveText so the composer and the Inbox Pilot both send the localized wording. Locked by default-quick-reply-i18n-contract.md. Two known limitations: the picker's text SEARCH matches the raw (English) label/text, so searching a built-in by a translated term won't match (the buttons still render localized); and the CLI PATCH /quick-replies/:id route (label/text/autoSubmit) does not clear the key, so editing a built-in via the CLI leaves it catalog-served — to personalize a built-in from an agent, delete it and create a fresh reply.
Related
For the composer side of the same feature — the Alt+S snippet picker, the Alt+1/2/3 AI suggestion chips and the Alt+Z Zap button — see use-quick-responses.md. Saved replies also fire from outside the composer, so automations-and-auto-replies.md covers the Auto-replies rules and Automation auto_respond actions that can fire a snippet by label, and cli-control.md documents the /snippet/* HTTP endpoints for scripting the snippet library from AutoHotKey, curl, or an external AI.
Last verified 2026-10-06