Omniscio

Scheduled Messages (a note to your future self)

Scheduled Messages lets you write a rich-markdown note to yourself, schedule it to arrive once or on a recurring cadence, and have Omniscio drop it silently into your unified inbox when it fires — a letter to your future self with no approvals and nothing to respond to.

On this page

What it is

Scheduled Messages lets you write a rich-markdown note to yourself — a subject line plus a Markdown body, with optional inline images — schedule it to arrive once at a future time or on a recurring cadence, and have Omniscio silently drop it into your unified inbox when it fires. Think "a letter to your future self": a reminder, a checklist, a standing weekly prompt, a bit of context you want resurfaced next Monday morning. When the message fires it lands as a persistent inbox item that survives an app restart; you read it and archive it (and Ctrl+Z brings it right back if you archive one by mistake), and that's the whole lifecycle — there are no approvals and nothing to respond to.

Scheduled Messages is on by default. The capability (flag scheduledMessagesEnabled) ships enabled for everyone — existing installs are flipped on once, respecting a later opt-out — so the background scanner runs and a fired note lands in your unified inbox whether or not you ever open the feature's UI. What is hidden by default is the standalone "Scheduled Messages" sidebar row and its compose surface, gated by a separate UI-only flag (scheduledMessagesSidebarEnabled, default off), exactly the way Alerts works. Reveal the row by installing Scheduled Messages from Marketplace → Inbuilt (or from the discovery nudge, which flips the same flag); hiding it never affects the scanner or the inbox delivery. Turning the capability itself off — the opt-out in Settings → Features — silences the scanner; messages and deliveries already in the inbox are preserved.

Not the same as "Send Later". Send Later (a.k.a. scheduled responses) defers a reply you are sending into a live Claude session — it queues your typed message and dispatches it to the agent at a chosen time. Scheduled Messages never touches a session and never talks to an agent: it delivers a note to you, into your inbox, full stop. If you want to nudge a running agent later, use Send Later; if you want to remind yourself of something later, use Scheduled Messages.

A scheduled message has two states: Active (enabled — the scanner fires it on its schedule and, for recurring messages, advances to the next fire time) and Paused (disabled — the schedule is suspended but the message is kept so you can resume it). Recurrence reuses Omniscio's shared recurrence vocabulary: once, daily, weekdays, weekends, or specific days of the week, each paired with a local time of day.

Where to find it

How to use it

  1. Reveal it in the sidebar. The feature is already on, but its sidebar row is hidden by default. Install Scheduled Messages from Marketplace → Inbuilt, then use its pin to add it to the side nav. (You can also jump straight in from the discovery nudge, which flips the same toggle.)
  2. Open the Scheduled Messages virtual project in the sidebar. The first launch shows an empty state with + New message.
  3. Compose a message. Give it a subject (up to 200 characters) and a Markdown body (rendered live in a preview pane via ProseBlock). Use Add image to embed an inline image — it is copied into the message's own attachment storage and referenced by an attachment:// URL, so the original file can move or be deleted later without breaking the message.
  4. Set the schedule. Pick a recurrence — Once, Daily, Weekdays, Weekends, or Custom days (choose which days of the week) — and a time of day (defaults to 08:00 local). Or, faster: type the timing in plain English into the Schedule (plain English) box above those controls — "every weekday at 8pm", "tomorrow at 2:30pm", "weekends at 9am" — and Omniscio fills the Time, Recurrence, and (for one-offs) Date for you, with a one-line preview of what it understood. The box only ever fills the schedule; your subject and body are never touched, and you can still adjust any field by hand. Save with the button or with Ctrl+Enter / Cmd+Enter.
  5. Receive it in your inbox. When the message fires, it appears in your unified inbox as a Scheduled Messages integration row. Clicking the row opens the delivery in the Scheduled message inbox viewer on the right: the subject as a heading, a "Delivered <timestamp>" line, and the Markdown body rendered as rich text. Archive it with the Archive button to clear it from the inbox — and if you archive one by mistake, press Ctrl+Z to bring it straight back (the archive is reversible).
  6. Act on it with one click. The card also carries a Start session button in its bottom bar (the same shared affordance drip and agent-alert cards have, keyboard shortcut N). Click it to open the shared Start session dialog: pick the repo, add your own message if you like, and the reminder's subject and body ride along in a collapsed, editable details box (there is no Base branch picker). The session receives your message first, then a short "About this item" note Omniscio adds itself (what a scheduled message is, when this one was delivered, whether it repeats and when it is next due, its ids, and how to list, archive or bring back the delivery), then the reminder — handy when the note is really a to-do. Starting a session leaves the reminder in your inbox (archive it yourself when you're done).
  7. Manage existing messages. The management pane (and the sidebar) split messages into Active and Paused sections with live search. Each row offers Pause / Resume and Delete (delete is confirmed via ConfirmDialog — it stops all future deliveries, but deliveries already in your inbox are kept).

How it behaves

  • Integration registry contracts — the wiring assertions this feature's registry entry has to honor.
  • Drip — the queue-and-trickle inbox feeder this feature is modeled on (Drip is the richer, multi-item cousin).
  • Send Later — defers a reply into a live agent session; the distinct feature people most often confuse this with.

drip.md is the queue-and-trickle inbox feeder this feature is modelled on, and send-later.md covers the distinct feature most often confused with it — deferring one of your replies into a live agent session rather than delivering a note to you.

Last verified 2026-09-28