Many tasks don't need to happen the moment you think of them — they need to happen at a specific time, or on a recurring basis, without you having to remember to trigger them yourself. Sending a daily standup summary, compiling a weekly report, or firing off a one-time reminder before a big meeting are all things you'd otherwise have to remember to do manually, every single time.
elvex solves this with schedules. A schedule lets you set up a task once and have elvex run it automatically, whether that's a single time in the future or on a recurring cadence like every day, every week, or every month.
Schedules aren't limited to agents. You can attach one or more resources to a schedule — such as an agent, a space, or a datasource — so the task runs with whatever context you've set up for it, the same way you'd reference them in a normal conversation.
You might need a schedule when:
You want a daily or weekly summary sent to you automatically instead of having to ask for it each time
You need a report compiled at the end of every month without manually kicking it off
You want a one-time reminder or task to run at a specific date and time in the future, like a briefing before a meeting next Tuesday
You want a recurring task tied to a specific space or datasource, so it always runs with the right context attached
Creating a Schedule
There are three ways to create a schedule in elvex:
Click the + button in the top-left navigation and select Schedule from the menu (alongside Thread, Agent, Datasource, and Space) to create a schedule from scratch
While composing a message, click the dropdown arrow (▾) next to the send button and select Schedule this prompt to turn your current message into a schedule
Ask your home agent (My Space) to set one up for you in natural language — for example, "Create a schedule with the Sales Report agent to run weekly on Tuesdays with this input: ..."
If you use the composer shortcut, elvex automatically attaches whatever resource you're currently chatting with — if you're chatting with an agent, the schedule will run against that agent; if you're chatting with a datasource or space, the schedule will run with that same context attached.
The first two approaches open the Create a schedule form, where you'll configure the following:
Name: A label to help you identify the schedule in your schedules list
Task Instructions: The prompt that elvex will run when the schedule fires, along with the resources attached to it. You can attach more than one resource here — for example, an agent along with a specific datasource — by adding chips in the Task Instructions section
Frequency: How often the schedule runs
Schedule Frequency Types
elvex supports several frequency types, so you can match the schedule to how often the task actually needs to happen:
Hourly
Runs once every hour, At minute (0–59) that you specify, in the Timezone you set. For example, setting the minute to 0 runs the schedule at the top of every hour.
Daily
Runs once a day at a Time and Timezone you set.
Weekly
Runs once a week at a Time and Timezone you set, on the day or days you choose using the Repeat on day-of-week picker (Sun–Sat).
Monthly
Runs once a month at a Time and Timezone you set, on the Day of month you specify.
One-off
Runs exactly once, at a specific Date, Time, and Timezone you set. This is useful when you need something to happen once in the future — like a briefing before a meeting or a reminder in a few days — without setting up and then having to remember to cancel a recurring schedule.
Once a one-off schedule fires, it marks itself as Completed and will not run again. You can find completed one-off schedules in your schedules list alongside recurring ones, clearly labeled so you can tell them apart. One-off schedules are checked every minute, so your task will run within approximately one minute of the time you set.
Custom
Runs on whatever cadence you define using a 5-field CRON expression, for schedules that don't fit neatly into the hourly, daily, weekly, or monthly options. If you're not familiar with CRON syntax, just ask elvex to help you write the expression for what you want — for example, "give me the CRON expression for every weekday at 8am."
For every frequency type, the schedule form shows a Next runs preview so you can confirm the timing is what you expect before saving. You can also click View full config to review the complete schedule setup.
Common Questions
Can a schedule use a specific space or datasource instead of just an agent?
Yes. When you set up a schedule's Task Instructions, you can attach a space, a datasource, an agent, or a combination of resources as context, the same way you would in a regular conversation. The schedule will run with that context attached every time it fires.
If I use "Schedule this prompt" from the composer, what gets attached to the schedule?
Whatever you're currently chatting with. If you're in a conversation with an agent, the schedule runs against that agent. If you're chatting with a datasource or space, the schedule runs with that same resource attached.
Can I create a schedule just by asking for one in a conversation?
Yes. You can ask your home agent (My Space) to create a schedule for you in natural language, describing the resource, cadence, and prompt you want, and it will set up the schedule on your behalf.
Can I edit a one-off schedule after creating it?
The run time is locked after creation to prevent accidental changes. If you need to change the time, delete the schedule and create a new one.
How is a one-off schedule different from a recurring schedule?
A recurring schedule (Hourly, Daily, Weekly, Monthly, or Custom) fires on a repeating cadence and stays active until you pause or delete it. A one-off schedule fires exactly once and then completes automatically.
What's Next
After a schedule runs, you can find the conversation or output it created in your thread history. If a one-off schedule captured a task you want to repeat going forward, you can create a new schedule with a recurring frequency instead.