Routines

Routines run an agent for you on a schedule. You choose how often it runs, which tools it may use each time, and how deep it should think. You can then check the history when you want to see what it produced.

You create and edit routines from the same chat workspace you already use, so it should feel familiar if you chat with agents today. Open Routines from the sidebar to manage schedules, the Calendar, and run history in one place.

📝 Note: Which schedules, tools, and plans are available depend on your organization and subscription. Routine management from chat, Calendar bookings, and spending controls roll out progressively to organizations with Routines enabled. If you do not see routines or these options, ask your organization admin.

What you can do

• Pick a schedule — Daily, weekly, monthly, or a custom pattern (for example every Monday morning or the first day of the month).
• Book from the Calendar — Choose a date, time, and time zone for a one-time or recurring run (see Calendar and spending).
• Limit tools per run — Give the routine only the tools it needs so each run stays predictable and lower risk than turning on every tool at once.
• Adjust reasoning effort — Trade speed and cost against depth for automated runs versus when you are chatting live.
• Pick an approved model — When you choose a model directly on a routine, the list reflects organization model settings for the routines surface. Routines that run through an agent use the agent’s model instead.
• Set a spending limit — Cap how much a run may cost before further paid work stops.
• Review past runs — Open earlier runs to read outputs, timestamps, spending, and errors when something failed.
• Manage from chat — Create, inspect, pause, resume, change, delete, or run a routine from a regular or agent conversation.

Manage routines from chat

When chat routine management is enabled for your organization, you can ask Devs.ai to create and manage routines directly from a regular chat or an agent chat. Describe what should happen and when, then refine the schedule, task, and available settings in the same conversation.

Ask to inspect a routine, pause or resume it, change it, delete it, or run it now. You can also review its run history and open results you have access to. A manual run can start even while the schedule remains paused.

When a conversation suggests a task you might repeat, chat can offer Make this a routine? Choosing Set up routine starts the conversation about timing and settings. The offer itself schedules nothing, and you can dismiss it.

Example: “Every Monday at 9 a.m. Toronto time, have my research agent prepare a short industry update with sources.”

Calendar and spending

The Calendar tab in Routines lets you Book an agent for a specific date, time, and time zone—once or on a recurring schedule.

• Switch between Month and Agenda views (on phones, the calendar starts in agenda view).
• Filter by agent and inspect upcoming work alongside recorded runs.
• Times are shown in the time zone you select for the booking.

Example: set the task, schedule, optional spending limit, and completion email in one place. Sample agents and prompts in the screenshot are for illustration.

Spending limit per run

When you book work, you can turn on Set a spending limit and choose whether to receive an email when the work finishes or stops. New bookings start with an adjustable allowance (for example $2 USD); existing routines keep their current settings.

Run History shows recorded spending, the allowance, the outcome, and a link to available results. When recorded spending reaches the allowance, further paid work stops (Stopped — spending limit reached). Operations already running may finish above it, and external services may charge separately. A spending stop leaves future scheduled runs active, each with its own allowance, and any partial results remain in the run’s chat.

Your calendar vs organization routines

The calendar opens with your own routines and runs. Admins with organization-level access can select Show organization routines to inspect the broader schedule. The organization view is optional and resets when the page is opened afresh.

Common patterns

• Daily summaries — inboxes, queues, or dashboards the agent can already reach with tools.
• Weekly reports — pull numbers or text from documents and connectors you trust.
• Monthly checks — same instructions you might type once in chat, repeated on a calendar.

How this fits with agents

You still shape the agent in Creating agents, then refine models and data in Configuring model and data sources and tools in Configure extended capabilities. A routine reuses that agent and adds when it runs and how tightly each run is scoped.

Organization-level routines (admins)

Organization admins and custom roles with organization-level Routines access can review scheduled work across the whole organization, not only their own routines.

Open the routines management page

1. From the sidebar, open Routines.
2. Use the Routines tab to see every routine you are allowed to view, the Calendar tab to book and inspect schedules, and the Run history tab to filter executions by status, routine, and time range.

Members with only self-level Routines permission see routines they created. Members with organization-level Routines permission see routines created by anyone in the organization (including via Show organization routines on the calendar).

Agent and model precedence

Each routine runs against either an agent or a model:

Target	What runs
Agent	The selected agent’s configuration—its model, tools, and instructions—drives each scheduled run.
Model	You pick the model (and tools) on the routine itself; the run does not inherit a full agent profile.

The Agent column on the routines list shows which agent or model is configured so admins can spot conflicts—for example, two routines pointing at different agents for the same workflow.

When a routine targets an agent, the agent’s settings take precedence over ad hoc chat defaults. When it targets a model, the routine’s own model and tool selections apply.

Control who can view or edit routines

Grant Routines permissions under Organization > User Permissions when you create or edit a role:

• User (Self) — view or edit only that person’s routines.
• Organization — view or edit routines across the organization (typical for leads and admins auditing scheduled agents).

See Custom user permissions for how roles combine and how to assign them.

Related topics

• Getting started — sidebar navigation and how you open agents.
• Working with agents — everyday chat, including Make this a routine?
• Agent tools and Add AI actions — how tools work before you attach them to a routine.
• App Builder — for publishing an app; use routines when you only need a scheduled agent, not a full app.
• Organization model settings — admin controls for which models appear in routines and other surfaces.