How Agently Works

Routines

A routine is a standing instruction. You write it once, and it runs on a schedule. Every Monday, send me the churn report. Every weekday at nine, summarise new support tickets. First of the month, chase anything unpaid.

The Routines screen holds the instructions themselves. It does not hold their output. When a routine fires, that run appears in Work on the day it runs, alongside everything else in your queue.

Coming from an older version? Routines replaced the Calendar screen in August 2026. The old /calendar URL redirects here. Your meetings live in Google Calendar, which Jarvis reads and writes through the integration.

Creating one

Click New routine and write the instruction as a sentence, including when it should run:

Every weekday at 09:00, summarise new support tickets

Press enter and Jarvis reads the schedule out of the sentence. You do not fill in a cron expression or pick from a recurrence dropdown. You can also just ask in chat: "every Monday, send me the churn report." It lands here either way.

Routines run once, daily, weekly on chosen days, or monthly on a given day.

Reading the list

Each row is one routine, with three things on it.

Routine is the name plus its schedule in plain words: every weekday · 09:00, mondays · 07:30, monthly on day 1.

Autonomy is the important column. It says how far a run goes without you:

  • Asks before shipping. The run produces a task in Work with its output attached. Nothing leaves your workspace until you review it.
  • Runs unattended. The run completes on its own. Used for routines whose whole point is that you are not there, like a scheduled post going out.

The column is derived from what the routine actually does, not from a setting you toggle. A routine that drafts something will always ask. One that performs a single defined action will not.

Last run shows when it last fired and whether it succeeded, or when the next one is due if it has not run yet.

Switching one off

Every routine has a toggle. Turning it off pauses it without deleting it, so the instruction and its history stay put and you can turn it back on later. A paused routine greys out but stays in the list.

What routines are good for

The test is whether you would put it on a recurring calendar invite for a person.

  • A digest. Monday morning summary of what moved last week, pulled from your connected tools.
  • A sweep. Daily pass over new support tickets, sorted and assigned.
  • A chase. Weekly look at unpaid invoices with a drafted follow-up for each.
  • A watch. Competitor pages or a news query checked on a cadence, with anything new written into your Brain.
  • A post. Something published on a schedule to a connected account.

How it relates to everything else

A routine is the schedule. Work is where its runs show up. Approvals is where a run stops if it wants to take an action that needs your sign-off. A routine that asks before shipping never touches Approvals, because it hands you the whole task to review instead.

  • Work, where runs land and get reviewed
  • Approvals, sign-off for unattended actions
  • Integrations, the tools a routine reads and writes
  • Skills, teaching a routine to work your way
← WorkSkills →