Build your workflow

Scheduled loops

Schedule recurring prompts in Claude Code and combine them with Recall's persistent context.

In this guide

Scheduled Loops with Claude Code

Claude Code's /loop command schedules a prompt to fire at a regular interval while your session stays open. Recall integrates natively so you can get periodic memory digests without lifting a finger.

When a scheduled prompt fires, Claude wakes up and calls whatever MCP tools it needs — including Recall. This means you can set up a recurring check-in that surfaces recent memories and pending to-dos automatically in the background.

Fires while you work

Loop runs between your turns, never interrupting mid-response

Calls MCP tools

The scheduled prompt can invoke any Recall tool automatically

Session-scoped

Loops live for the current session. Use Desktop for persistent scheduling

The /recall-loop Command

The easiest way to schedule a memory check-in. One line sets up an hourly digest of recent memories and pending to-dos.

/loop 30m /recall-loop        # Every 30 minutes
/loop 1h /recall-loop         # Hourly digest
/loop 2h /recall-loop         # Every 2 hours

Each time the loop fires, Claude runs /recall-loop which calls the loop_digest tool and formats the result:

Example output when loop fires

Recall Digest — Last 60m [14:30:00]
==================================================
MEMORIES  3 new
  [decision] Chose Redis for session caching with 30-minute TTL
  [insight] Auth middleware reads tenant context from req.tenant
  [code_pattern] Always use generateUlid() for new IDs

TO-DOS
  [OVERDUE] Review security audit report (high)
  Write tests for billing service (medium)

--------------------------------------------------
Tip: /loop 60m /recall-loop

loop_digest MCP Tool

Call directly in a custom loop prompt for more control over the window and filters.

window_minutesHow far back to look (default: 60)

include_todosInclude pending/overdue to-dos (default: true)

min_importanceMinimum memory importance to show (1-10, default: 4)

/loop 30m call loop_digest with window_minutes=30 and tell me if there are overdue todos

Scheduling Ideas

/loop 5m check if the deployment finished and tell me the status

Babysit a Railway or Vercel deploy while continuing other work

/loop 30m /recall-loop

Periodic memory digest during a long coding session

/loop 1h check my recall todos and remind me of anything overdue

Hourly to-do reminder without leaving your session

/loop 15m check the CI status for the current PR and alert me if it fails

CI monitoring while you write code

/loop 2h summarize what decisions I've stored in recall today

End-of-day context review for future sessions

Interval Syntax

Intervals are optional — if omitted, the loop defaults to every 10 minutes.

Form	Example	Interval
/loop 30m ...	/loop 30m /recall-loop	every 30 minutes
/loop 2h ...	/loop 2h /recall-loop	every 2 hours
/loop 1d ...	/loop 1d summarize my day	every day
No interval	/loop /recall-loop	every 10 minutes (default)

Loops expire after 3 days automatically. Use Claude Desktop's scheduled tasks for persistent scheduling that survives session restarts.

Keep up with what's changing.

Read the changelog