Skip to main content
ollim-bot doesn’t wait to be asked. Its scheduling system runs routines (recurring schedules) and reminders (one-shot or chainable nudges) that fire automatically. Each one becomes an agent prompt — the bot reads it, decides what to do, and optionally pings you with findings. Most routines and reminders run as background forks — disposable sessions where the agent works silently and only reaches out when something warrants attention, governed by a ping budget.

​
Key features

Routines

Recurring cron-based prompts that define the daily and weekly rhythm. Fire on schedule indefinitely.

Reminders

One-shot nudges that fire after a delay, then self-remove. Support follow-up chains via the agent.

Background forks

Disposable sessions for routines and reminders. Text output is discarded — the agent pings or reports findings.

Ping budget

Rate-limited ping budget that prevents background forks from over-pinging.

Forward schedule

Each background task sees upcoming tasks, budget status, and refill timing before deciding whether to ping.

Chain reminders

Multi-step follow-ups where the agent schedules the next check. Chains end when the agent stops calling follow_up_chain.
Routines and reminders are markdown files with YAML frontmatter, stored in ~/.ollim-bot/routines/ and ~/.ollim-bot/reminders/. The agent can create, edit, and remove these files directly — no CLI required. Changes are picked up within seconds, no restart needed.

​
Foreground vs background

Routines and reminders can run in two modes:
The default for routines when background is not set or false. For reminders, foreground requires foreground: true via the add_reminder tool or background: false in the YAML file. The bot sends you a DM with the agent’s response, just like a normal conversation.Foreground tasks pause interactive conversation while running. Use these for tasks that need your immediate attention or require back-and-forth.

​
Routines vs reminders

​
Find what you need

​
Next steps

Routines

Cron syntax, YAML frontmatter fields, and routine examples.

Reminders

One-shot reminders, delay scheduling, and follow-up chains.

Background forks

Isolated mode, model overrides, tool restrictions, and update modes.

Ping budget

Refill-on-read bucket, capacity, refill rate, and critical bypass.

Real-world examples

Annotated routines and reminders from an actual data directory, with patterns for pipelines, chains, and behavioral design.