Routines

A routine is a session that starts itself. You write the prompt once and pick when it runs, and every run opens a new conversation with that prompt already sent, so Monday's competitor sweep or the first of the month's performance read is waiting for you rather than something you remember to ask for.

Making one

Open Agent in the rail and pick Routines under New task in its sidebar. The page lists your own routines in the brand you are in: a routine runs as the person who made it, so a teammate's are theirs and do not appear here. New routine, at the top right, asks for four things: a name, the prompt, how often it runs, and the time and timezone it runs at.

• Every day and Weekdays run at the time you set.
• Every week runs on the weekday you pick.
• Every month runs on a date from 1 to 28. Past 28 a month is not guaranteed to have the day, and a routine that silently skipped February would be worse than one that refused to be made.

The time is a wall clock in your own timezone, taken from your browser when you make the routine. Nomi looks for routines that are due every fifteen minutes, so one set for 09:00 runs within a quarter of an hour of it.

The switch on a routine's row turns it off without deleting it: a paused routine keeps its schedule and simply stops being due, so turning it back on resumes it. The row shows its schedule and when it last ran, and the pencil opens it to change or delete it. Deleting one stops it running, and the sessions it has already made stay where they are.

The list has tabs by schedule, All first, then Every day, Weekdays, Every week and Every month for the kinds you have, and Paused for the ones that are off. A search sits beside them.

Where the answers go

Each run opens a new session, named after the routine, with the prompt as its first message. It is in Recents like any other conversation, and anything it makes is in the Library like anything else. Nothing is overwritten and no run touches the run before it, so a daily routine leaves you a week of separate sessions rather than one long thread.

A run remembers nothing from the run before it. If a routine needs continuity, say so in its own message: ask it to write what it found into a document, and that document is its memory.

A routine acts as whoever made it, and only they can change, pause or delete it. If that person loses access to the brand, the routine stops. Someone who can only read a brand has no routines in it, and the page says so.

What it costs

Whatever the turn costs. A routine is a normal conversation turn, metered on what it used, out of the same balance everything else comes from.

When one does not run

Two things stop a run, and both leave the session behind so you can see what happened rather than finding nothing.

• Not enough credits. The session opens, the prompt is in it, and Nomi's reply is the sentence saying the balance is short. Nothing is charged.
• Something went wrong. The session carries a line saying the routine could not run, that nothing was charged, and that it will try again at its next time.