COMMAND REFERENCE

TESTED AGAINST THE ACTUAL PARSER

command reference.

Copy the examples as written, then replace the highlighted parts with your own words. Every command affects only the conversation where you send it.

00 / START HERE

how to talk to the snorse

In a group, either mention @snorse-bot using Signal’s real mention picker or begin the message with 🐴 or 🐌. In a direct message, use either emoji or type @snorse-bot. Ordinary conversation and unprefixed DMs are ignored.

group
🐴 help
group
@snorse-bot reminders
direct message
🐴 calendar

Wherever this page shows 🐴, 🐌 or a real Signal mention works too. The prefix is not part of the command syntax below.

01 / CREATE

create a reminder

One time: today or tomorrow

remind [thing] today|tomorrow at [time]

🐴 remind call Sam tomorrow at 9am
🐴 remind take the bins out today at 19:30
🐴 remind deploy the site tomorrow at 7:30pm pt

Put the reminder text first, then the day and time. The optional word me and optional to may appear directly after remind: remind me to call Sam tomorrow at 9am.

One time: exact date

remind [thing] on [date] at [time]

🐴 remind renew the domain on 2027-07-15 at 10am
🐴 remind submit the form on 07/15/2027 at 10am

Repeat every day

remind [thing] every day at [time]

🐴 remind water the seedlings every day at 8am

daily also works in place of every day.

Repeat every week

remind [thing] every [weekday] at [time]

🐴 remind tidy the kitchen every friday at 5pm

02 / READ + CHANGE + DELETE

manage reminders

List

reminders or list

🐴 reminders

The reply includes each reminder’s local ID. IDs do not include a required #; both 12 and #12 are accepted when editing or canceling.

Edit one field

edit [id] text|time|date|id [new value]

🐴 edit 12 text bring snacks
🐴 edit 12 time 6:30pm
🐴 edit 12 date 2027-07-15
🐴 edit 12 id snacks

Edit exactly one field at a time. Custom IDs use lowercase letters, numbers, and hyphens and are local to this conversation.

Cancel

cancel [id]

🐴 cancel 12

03 / GOOGLE CALENDAR

read a calendar

Calendar support is read-only and must be configured by the host. Start with setup help; it provides the Google service-account email that needs See all event details permission.

Link a calendar to this conversation

calendar link help

🐴 calendar link help
🐴 calendar link household@example.com

link calendar [calendar id] is an equivalent form.

Show events

🐴 calendar
🐴 calendar next 10 days
🐴 next 3 weeks
🐴 calendar this month

calendar shows the next seven days. A range must be at least one day and no more than 93 days. The word calendar is optional for next… and this month queries.

04 / SCHEDULE A COMMAND

scheduled calendar digests

[calendar query] -> remind [label] [schedule]

🐴 calendar next 7 days -> remind weekly agenda every monday at 8am
🐴 calendar this month -> remind month check every day at 6pm

Scheduled calendar digests work only in groups. At delivery time, the snorse runs the calendar query and posts its current results. The first example above is verified; calendar ranges themselves must match the forms documented in the calendar section.

05 / RULES

dates, timezones, and scope

DatesYYYY-MM-DD or MM/DD/YYYY
Times7pm, 7:30pm, or 24-hour 19:30
Timezoneset, ct, mt, pt, or utc; otherwise the host default applies
Reminder text1–500 characters
ScopeEvery reminder and linked calendar belongs to one group or personal conversation

In a DM, listing reminders or calendars may also include active groups whose current Signal member list contains you. A DM cannot expose groups you are not currently in.

06 / TROUBLESHOOTING

when nothing happens

The snorse ignored the message.
Put 🐴 or 🐌 at the very beginning, or use Signal’s real mention picker. A typed @snorse-bot triggers DMs, but group chats require a real mention.
The reminder syntax looked natural, but failed.
The grammar is intentionally small. Put the thing first and the schedule last; copy one of the create examples above.
Calendar integration is not configured.
The host has no Google credentials. Reminder commands still work normally.
A new group receives only a capacity link.
The shared host is full or unhealthy. Existing groups stay online and new groups enter a first-in, first-out waitlist.