Omniscio

Team Chat reminders — be reminded about a message later

Open a message's action menu — right-click it, or use the ⋯ button that appears when you hover it — and choose Remind me. Pick In 20 minutes, In 1 hour, In 3 hours, Tomorrow at 9:00 AM, Next week (Monday 9:00 AM), or Custom date and time. The reminder is yours alone. You will find it at the top of Saved with the time it is due, where you can change that time, mark it complete, or remove it. When the time comes you get a notification; opening it takes you straight to the message — even if Omniscio was closed when it fired.

On this page

How to do it

  • Right-click the message (or click the ⋯ beside it) and hover Remind me. The five quick times are one click each. Custom date and time opens a small window with a date-and-time field.
  • It works everywhere a message appears: in a channel, in a direct message, and in a thread.
  • The quick times are relative to the moment you click, with two exceptions that are pinned to your own local clock: Tomorrow at 9:00 AM and Next week (Monday 9:00 AM). "Next week" always means the next Monday, so on a Monday it gives you the Monday seven days out.
  • The window never accepts a time in the past — a time you type that has already gone by becomes one minute from now — and refuses a time more than a year ahead with a plain message, because a reminder further out than that cannot be scheduled.

It is private, and it also keeps the message

  • Only you can read or write your reminders. They live in your own document inside the workspace, and the security rules refuse every other person, including workspace owners.
  • Setting a reminder also saves the message to Saved, the way Slack treats "Later": the reminder and the message stay together, and you can unsave the message at any time without touching the reminder.
  • Your reminders sync across your computers and the web app, because they live on the server rather than on one machine.

Where you manage them

The top of Saved carries a Reminders section: every reminder with the time it is due, the conversation it came from, and the message text. Click a row to jump to the message. Each row has three buttons:

  • Pencil — change when the reminder fires (the same quick times and custom field).
  • Check — mark it complete. A completed reminder moves out of the active list and is cleaned up automatically a week later.
  • Trash — remove the reminder entirely. The saved message stays in Saved.

One reminder per message: setting a second one on the same message replaces the first rather than stacking two. A reminder that was set for a message in a channel you have left simply never fires; the server re-checks your access to the channel before it schedules anything.

What happens when it is due

The reminder is not run by your app. Writing the reminder hands it to a Cloud Task that fires at the due moment, so it works with Omniscio closed and with every computer off. At that moment the server checks once more that you can still read the conversation, marks the reminder as fired, and sends a notification to the devices you have signed in, carrying the message text you saw when you set it. If you have left the conversation by then, nothing is sent. Tapping the notification opens the conversation at that message. The reminder then shows as Due now in Saved until you mark it complete or remove it.

If the reminder is deleted or its time changes before it fires, the scheduled task is cancelled, so a changed reminder never fires twice.

Limits and data

  • Up to 100 reminders at a time. At the limit you are told to remove one rather than the write failing silently.
  • A reminder keeps its own copy of the message author, channel name and up to 500 characters of the text, captured when you set it, so the Saved list and the notification never need to read the original message. The stored user's data is removed with the rest of their Team Chat data when their account is erased or their membership ends.

For developers — the data model

{tenant}/reminders/{uid} is one document per person, the same shape as {tenant}/saved/{uid}:

{ items: TeamChatReminder[] }

Each TeamChatReminder (see src/shared/team-chat/reminders.ts) is: id, channelId, messageId, messageAt (the message's createdAt, used to scroll to it), channelName, authorName, text (snapshot, capped at 500), dueAt (ISO instant), createdAt, and optional firedAt / completedAt.

  • Client writes go through data/chat-reminders.ts, which reads the server copy inside a transaction, so two computers cannot both append the same new reminder.
  • Server side is firebase/functions/src/team-chat/reminders.ts: the write triggers onRemindersWritten / onWorkspaceRemindersWritten diff the before/after items arrays and enqueue (or cancel) one Cloud Task per reminder, deliverChatReminderTask marks the reminder fired in a transaction and sends the push.
  • Any surface that wants to offer "remind me" calls openRemindMe(target, existing?) from remind-me-open.tsx; preset clicks use createMessageReminder(target, dueAtIso) from remind-me-actions.ts. A slash command (/remind …) should build the same TeamChatReminder and call saveReminder through the same data layer.

Last verified 2026-11-20