Omniscio

Quick Replies via CLI (read, create, move, delete, export and import the library from an AI agent)

Quick Replies via CLI exposes the personal Quick Replies library — snippets, dividers and folders — to an outside AI agent over Omniscio's local control server: eleven routes to read, create, edit, reparent, reorder, delete, restore, export the library as a bundle, import one back. Covers the gating model, the flat and tree read shapes, the add-only import merge, and what is deliberately out of scope.

On this page

What it is

Omniscio ships a Quick Replies library — the user's personal collection of pre-written messages they can paste into a running Claude session with a single click. Each row in the library is one of three shapes:

  • snippet — an actual reply with a label and a body text (e.g. label "Hi", text "Hello — thanks for the message."). An optional autoSubmit: true flag means clicking the snippet inserts AND sends the message in one step.
  • divider — a visual section break with a label only (no body). Renders as a horizontal rule with its label in the picker.
  • folder — a container that can hold snippets, dividers, or sub-folders. Has a label, no body, and can nest arbitrarily.

Every row has an optional parentId (the string id of its enclosing folder, or null for top-level rows) and a displayOrder integer used to sort siblings within the same parent. The full structure is therefore a tree — top-level rows have parentId: null, everything else points at a folder row's id. The in-app picker walks that tree depth-first sorted by displayOrder at every level. The in-app companion page is quick-replies.md; this page covers the eleven CLI routes that expose the same library over the 127.0.0.1:19519 localhost HTTP server so an external AI agent (Claude Code in another project, ChatGPT with the omniscio-control skill, a curl script) holding the Omniscio bearer token can read, create, edit, reparent, reorder, delete, export and import entries.

The gating model is uniform across all eleven routes — and deliberately permissive compared to the rest of the CLI surface:

  • Every mutation is apply-immediately. There is no inbox approval round-trip. POST /quick-replies, POST /quick-replies/move, PATCH /quick-replies/:id, DELETE /quick-replies/:id, POST /quick-replies/reorder, POST /quick-replies/:id/restore, and POST /quick-replies/import all execute inline and return 200/201 the moment the change has landed. Quick Replies are personal text templates — no session spawn, no cost, fully reversible by re-creating or moving — so the inbox round-trip every approval-gated surface uses (cron, automations, settings, tag-library, recipes, sessions) would just add latency without any new safety. Open Omniscio clients refresh via the QUICK_REPLIES_CHANGED push.
  • No idempotency dedup. Unlike the cli-tags / cli-cron / cli-automations surfaces, which honor X-Client-Request-Id to fold a network-hiccup retry into the same pending row, the Quick Replies create body accepts a clientRequestId field for backward compatibility but the routes do not consult it. A blind retry on POST /quick-replies will produce two rows. Treat each mutation as one-shot; if you need to know whether a row landed, call GET /quick-replies — that is the source of truth.
  • Reads are bearer-gated but NOT read-budgeted. GET /quick-replies (flat), GET /quick-replies/tree (nested), and GET /quick-replies/export (the whole library as a bundle) require the bearer token in Authorization: Bearer <token> and return 401 when it is missing or invalid. They do not share the 60-reads-per-minute-per-token-hash budget that gates the rest of the auth-gated GET routes on this server — GET /quick-replies predates that budget, and /tree and /export were deliberately given the same plain-bearer tier so that diverging gates between read shapes of the same data would not surprise.
  • Mutations share the global 10-mutations-per-minute bucket with every other write route on this server, and return 401 when the bearer is missing or invalid. Every route on this surface — reads and mutations alike — answers a missing/invalid bearer with 401 unauthorized; 403 is reserved server-wide for an authenticated-but-denied request, and this surface has no such case (L05-F10).

The route family was renamed from /snippet/* to /quick-replies/* in schema v228 — anything you may have seen referring to /snippet/list or /snippet/create belongs to a prior surface and no longer exists.

Where to find it

Day to day the library is used from inside the app — the Quick Replies picker, where snippets, dividers and folders appear as a tree you can click, drag and edit. This page is about the other end of the same library: an AI agent reads and changes those rows from outside Omniscio, so the picker and the agent always see one set of entries. There is no separate screen to open for the agent side — it reaches the library over the same local control server the rest of Omniscio's automation is driven from, and needs the same access token.

How it behaves

Quick Replies is one of the few surfaces an AI can change with no approval step: every change is applied the instant it is made, and every open window is told to refresh itself, because these rows are personal text with nothing expensive or hard to undo behind them. The trade is that each request stands alone — repeating one that already half-succeeded makes a second copy rather than folding into the first — so the dependable way to find out what actually happened is to read the library back. Everything the agent can reach is also visible to you in the picker, and anything it gets wrong can be undone there in a couple of clicks.

How the picker itself is arranged and used from inside the app — dragging a snippet into a folder, the inline editor, and the two ways of deleting a folder — is on the Quick Replies page. If what you want is the moment a snippet is the right reply, see Use quick responses, and Quick reply declutter nudge covers keeping a library that keeps growing under control.

  • quick-replies.md — the in-app companion: the virtual project's three-tab sidebar, the drag-into-folder behavior, the inline editor's Content + Behavior tabs, the two-button cascade-vs-promote delete dialog, and the Export / Share / Import actions that share a code path with the two routes above.
  • cli-control.md — the CLI server itself: token handling, the full route catalog, the 10-mutations-per-minute mutation bucket, the 60-reads-per-minute read budget that this surface is exempt from.
  • cli-tags.md — the closest sibling CLI surface (multi-route library management for tag library). The contrast is instructive: cli-tags has an inbox-approval round-trip on library mutations and honors X-Client-Request-Id for idempotency; cli-quick-replies has neither, because Quick Replies are personal text and tag library changes carry blast radius across sessions.
  • cli-pending-actions.md — the inbox-approval surface used by every approval-gated CLI mutation. Quick Replies do not land here — every Quick Replies mutation skips the queue and applies inline.
  • omniscio-control quick-replies skill — the external-AI side of the contract: how an agent decides which route to call when the user says "add a quick reply for X" or "make a Greetings folder".
  • cli-quick-replies-contract.md — the test-locked invariants I1–I8 with citations into the routes and schemas tests. Read this before changing the surface.

Last verified 2026-09-29