Schedules

A schedule is a prompt that runs on its own, on a timetable you set. Each run opens a new chat in your Chats, titled with the schedule’s name and the date, so you read the answer like any other conversation. Open your schedules from the top bar with Schedules, or at /schedules.

The Daily Brief

The Daily Brief card at the top of the Schedules page turns a morning brief on with one switch. It runs every weekday at 7:30 in your time zone and covers today’s calendar with prep notes, the email that arrived overnight and needs you, yesterday’s meetings and their action items, and the approvals waiting for you.

Once it is on, the card shows when it arrives, lets you pick another time with Save Time, and links to the last brief with Open the Last Brief. Turn the switch off to stop it. The same switch sits at the end of the Company Brain’s side panel. The brief is a schedule like any other, so it counts toward your schedules and follows the same rules.

Making a schedule

There are two ways.

• From the Schedules page. Choose New schedule, or one of the starting points shown when you have none. Give it a name, write what to do each time, pick the agent that answers, then pick when: every weekday, every day, every week on a given day, every month on a given date, or a custom cron expression. The page shows the next few runs in your time zone before you save.
• From any chat. Ask for it in plain words, such as “every weekday at 8am, brief me on my day”. The agent sets up the schedule and confirms the timetable back to you. A schedule made in a chat uses that chat’s agent and, in a skill’s chat, that skill.

Write the prompt as a complete instruction. Each run starts fresh and does not remember the chat the schedule was made in.

What a run can do

A run is you asking the question at that moment. It uses your model choice, your department access, your connected apps and the same skills and tools as a chat you typed. Its cost counts toward your budget.

If a run wants to save something outside the brain, such as a Gmail draft or a Google Doc, it never waits for you. The request is left in that run’s chat as an approval card, and nothing is written until you approve it there. See Approving writes.

A run is skipped, with the reason shown on the schedule, when:

• no model can answer,
• your allowance for the period is spent,
• your organization has no plan, or too few credits for an answer, while it runs on SkillTree’s shared model keys,
• the skill the schedule uses was switched off.

A run that runs out of credits partway stops and shows that reason as a failure.

Managing schedules

Each schedule shows its timetable, the agent that answers, when it runs next and how the last run went, with Open the Result to go straight to that run’s chat.

• The switch pauses and resumes it.
• Run Now runs it within a minute, then it carries on with its timetable.
• Runs lists its recent runs, each with a link to its chat.
• Edit changes anything, and the trash button deletes it after asking.

In a chat you can also ask the agent to list your schedules, or to pause or resume one.

Limits

• Each person can have up to 25 schedules.
• Two runs of the same schedule are at least 15 minutes apart.
• If the workspace was offline when a run was due, the schedule runs once when it is back, then follows its timetable. It never replays every missed run.

Admins can change these limits; see environment variables.

Schedules are private. Nobody else, admins included, sees or changes yours.

To start an agent when something happens instead of on a timetable, see Triggers.