Context-Aware Reminders

Normal reminder apps give you a time and a text string. Moltbot gives you a time, a text string, and everything you need to know to act on it — pulled from memory automatically.

You: Remind me about the meeting with Alice next Wednesday at 2pm,
and include a recap of what we discussed last time

When Wednesday arrives, Moltbot does not just send "Meeting with Alice." It searches memory for your previous interactions with Alice, compiles a summary, and delivers the full context alongside the reminder.

Prerequisites

• Moltbot running and connected to Telegram
• Scheduled tasks / reminder support — See Scheduled Tasks
• Memory system enabled — The "context-aware" part depends on memory. Without it, reminders still work but are just plain text. See Memory System

How It Differs from Standard Reminders

Feature	Standard Reminder App	Moltbot Context-Aware Reminder
Time trigger	Yes	Yes
Custom text	Yes	Yes
Pulls related context from past conversations	No	Yes
Includes meeting history with a person	No	Yes
Adapts content based on what happened since	No	Yes
Can call tools (check GitHub, fetch data)	No	Yes

The key difference is that Moltbot reminders are not static. Between when you set the reminder and when it fires, the world changes. Moltbot can incorporate those changes into the reminder.

Setup

Step 1: Set a Basic Context-Aware Reminder

Just ask naturally:

You: Remind me about the meeting with Alice next Wednesday at 2pm,
and include a recap of what we discussed last time

Moltbot will:

1. Schedule the reminder for Wednesday at 2:00 PM
2. When the time arrives, search memory for all interactions with Alice
3. Compile a summary of your most recent discussion
4. Send both the reminder and the context together

Step 2: Add Follow-Up Reminders After Meetings

Build a habit of logging and scheduling in one step:

You: Just finished meeting with Bob. We discussed the API migration
timeline — he needs the spec by end of month. His team is blocked
on the auth module.

Remind me in 2 weeks to check in with Bob about the auth module progress.

Moltbot saves the meeting notes and schedules the reminder. When the reminder fires in two weeks, it will include the context about the auth module and the spec deadline.

Step 3: Recurring Context Reminders

Some reminders benefit from repetition with evolving context:

You: Every Monday at 9am, remind me to review my open GitHub issues
and include a summary of what I worked on last week.

Each Monday, the content is different because Moltbot pulls fresh data from memory and (optionally) from GitHub.

Step 4: Conditional Reminders

Reminders that only fire if a condition is met:

You: Remind me on Friday at 5pm to submit the expense report,
but only if I haven't already told you it's done.

Moltbot checks memory when the time arrives. If you said "Submitted the expense report" earlier in the week, it skips the reminder.

More Examples

Project deadline reminder:

You: The v2.0 launch is on March 15.
Remind me 1 week before with a status check:
what's done, what's in progress, and what's at risk.

Social reminder:

You: It's Sarah's birthday on April 12.
Remind me the day before so I can get a gift.
Include what she mentioned she's interested in lately.

Learning reminder:

You: I started the Rust book last week.
Remind me every evening at 9pm to study for 30 minutes.
Include which chapter I was on last time.

Follow-up chain:

You: I sent a proposal to the client yesterday.
If I haven't heard back by Friday, remind me to follow up.
Include the key points from the proposal.

Edge Cases and Troubleshooting

• Timezone handling: Reminders fire based on your server's timezone. If you travel across timezones, be explicit: "Remind me at 2pm Tokyo time." Moltbot will interpret this if your SOUL.md includes timezone awareness.
• Vague timing: "Remind me later" or "Remind me soon" is ambiguous. Moltbot will make a reasonable guess (e.g., 1 hour for "later," next morning for "tomorrow") but may ask for clarification. Be specific when precision matters.
• Memory gaps: If you ask for context about someone you've never mentioned before, the reminder will fire but the context section will be sparse. Moltbot will note that it has no prior information.
• Long-term reminders: Reminders set weeks or months in the future depend on Moltbot running continuously. If your server restarts and the cron state is not persisted, reminders may be lost. Check your persistence configuration.
• Overlapping reminders: If you set multiple reminders for the same time, they will all fire. Moltbot does not batch them automatically, but you can ask: "Consolidate all my reminders for tomorrow into a single message."

Pro Tips

• Combine with the Personal CRM. Every reminder about a person automatically becomes richer when you have CRM-style notes in memory. The two recipes are natural partners. See Personal CRM.
• Use reminders as accountability. Set a reminder to check on a goal: "Remind me in 30 days how the new testing strategy is going. Include what I said my targets were." Your past self holds your future self accountable.
• Dictate reminders by voice. Telegram supports voice messages. Say your reminder naturally, and Moltbot handles the rest. This is especially convenient when driving or walking.
• Chain reminders to workflows. "Remind me Monday at 9am to generate my weekly report" effectively creates a manual trigger for the Weekly Report recipe.
• Set pre-meeting prep reminders. "Remind me 30 minutes before the board meeting to review the slide deck and check if the Q3 numbers are finalized." This gives you preparation time with relevant context.

Related Pages

• Memory System — How context is stored and retrieved for reminders
• Scheduled Tasks — Technical details on cron and scheduling
• Personal CRM — Rich context about people in your network
• Weekly Report — Pair with reminders for regular reporting
• Creative Use Cases — More automation ideas