Skip to main content

Routines

Agent > Routines

Run the Agent on a schedule

A routine is a saved Agent prompt that runs on a cadence and produces a brief. Use routines for the reviews you already do by hand: morning planning, end-of-day cleanup, weekly team check-ins, and recurring client updates.

Start from a routine template or write your own prompt
Choose the schedule, scope, and delivery channels
Finished runs create briefs you can share
Routine runs are available through the MCP server and GraphQL API

Where routines live​

Routines live under Agent > Routines. The list has Routines and Runs tabs and All, Just Me, Team, and Workspace views, and shows each routine, whether it is active, and when it last ran.

Each routine has its own page. Click one to see its runs down the left, the selected run in the middle, and a Settings tab beside Runs if you can manage it. The header has Run now, an Active/Paused switch, and a menu with Edit routine and Delete routine.

New routine opens a page with a template gallery. Pick a template when the workflow is common, or start from scratch when you want Rize to answer a specific recurring question.

A routine page with the run rail on the left and a run's conversation in the middle
Every run keeps its conversation, so you can see exactly what ran and ask a follow-up.
Rize Routine template picker

Create a routine​

1

Pick a template

Start with Start of day, Midday check-in, End of day, Tag review, or Config review, or Start from scratch. Templates prefill the name, prompt, and schedule, and you can edit all three.

2

Review the prompt

Tell Rize what to analyze, what period to use, and what kind of brief to produce. Type @ to mention a client, project, team, person, or dashboard so the routine always runs against that record, and reference saved Skills when it should follow a team rule or client-specific instruction.

3

Choose who it runs for

Just Me runs on your own time. Team, for team admins, runs separately for every member of the team. Workspace, for workspace admins, runs for everyone. This cannot be changed after the routine is created.

4

Set the schedule

On-demand, Daily, Weekdays, Weekly, Monthly, or every few minutes, with the run day and time. A daily routine can prepare a same-day brief; a weekly routine can summarize the previous week.

5

Choose delivery

Send the finished brief by in-app notification, email, Slack, or any combination your workspace has connected, then click Create routine.

Team and workspace routines run per member

A team routine runs once for each member, on that member's own data, and each member sees the run that ran for them. Only admins can manage team and workspace routines.

What a brief contains​

A routine run produces a brief: a written result saved to Rize with the routine, run time, status, and markdown body.

For a Start of Day Prep routine, the brief can look at yesterday's work, today's calendar, open tasks, and recent patterns. For an End of Day Review, it can call out entries that need cleanup before the day is closed.

Start of Day routine configuration

Use Skills for repeatable instructions​

Skills make routines more consistent. Instead of pasting a long policy into every routine, save it once in Settings > Agent, then reference it from the routine prompt.

Good examples:

  • A client tagging policy.
  • A weekly team review format.
  • A rule for what counts as billable.
  • A manager's preferred morning brief structure.
Skills can be shared

Personal Skills are private to you. Team and workspace Skills can be reused by teammates and by external agents through the Rize MCP server.

API and MCP access​

Routine runs are readable from outside Rize. MCP clients use list_routine_runs and get_routine_run; API clients use routineRuns and routineRun.

This is useful when another assistant should consume the finished brief instead of re-running the same analysis from raw time entries.