Skip to content
Automations

Put routine work
on a schedule.

Recurring tasks that start themselves, in your time zone — and never quietly spend while you're away.

“Every morning, brief me on what changed in my topic.”
Trigger
Every day 8:00
Action
Research the latest developments. Write a short briefing with primary sources, dates and open questions.
Model
Claude Opus 5.5

An automation is
an ordinary task that starts itself.

Same project, model, tools and approvals as anything you'd run by hand.

  1. 01

    Write the task

    Name it and describe the work, then pick the project, the model and the tools it may use.

  2. 02

    Choose when it starts

    On a schedule, when a project file changes, or when a piece of text appears on a public page.

  3. 03

    It runs as an ordinary task

    Same agent, same approvals. Results land in the same conversation or a separate one.

  4. 04

    Run it now, or let it stop

    Run now starts it on demand; an optional expiry date stops it on its own.

Set it once,
in your time zone.

Try it — the next run updates as you change the days.

NameWeekly project review
Task

Review this project, summarize progress and outstanding issues, check the available tests and recommend the three most useful next steps.

Repeat on
… Run now
A week of automationsExample
Mon08:00
Tue08:00
Wed08:00
Thu08:00
Fri08:0016:00
Sat
Sun

Daily research brief, weekdays 08:00 Weekly project review, Fridays 16:00. Any hour, minute and set of weekdays works.

Three ways
to start.

A schedule, a file that changes, or a page that starts saying something. File and page checks run from once a minute to once a day; the first check only records a baseline.

Schedule

At the hour and minute you set, on the weekdays you choose.

The time zone is stored with the automation.

Project activity

When a watched project file's content changes.

Project-relative path; compared by content digest, not timestamp.

Condition

When 1–200 characters of text appear on a public page.

Fires on false → true; the page is observed, never executed.

Missed
means missed.

Automations start paid work, so the scheduler is strict — anything it misses is reported, not run later. Every missed or skipped occurrence leaves a notice with the reason.

  • App closedOccurrences that passed are marked missed. There is no catch-up.
  • Computer asleepWaking more than 90 seconds late marks that run missed.
  • Project busyThe occurrence is skipped instead of queued.
  • No replaysThe run is claimed before work starts, so a crash never repeats it.

Three starting points
that ship with the app.

Daily research brief

Research the latest developments in my chosen topic. Write a concise briefing with primary sources, dates, key changes and open questions.

Weekly project review

Review this project, summarize progress and outstanding issues, check the available tests and recommend the three most useful next steps.

Weekly learning plan

Prepare a focused weekly learning plan for my chosen subject. Include reliable resources, practical exercises and a way to measure progress.

Questions.

Does it run when the app is closed?
No. Automations run while Recursive Intelligence is open. A schedule that passes while it's closed is marked missed and is not caught up later.
What happens if my Mac was asleep?
If the computer wakes more than 90 seconds after the scheduled time, that occurrence is marked missed with a notice, and the next one is scheduled normally.
Can a watched page make the agent do something?
No. The page is only observed for your text; its content is never executed and it can't install tools.
Can I run one right now?
Yes — Run now starts it on demand, and you can choose whether results go to the same conversation or a separate one.
Can an automation stop by itself?
Yes. Set an expiry date and it stops scheduling after that moment.

Let the routine
run itself.