Scheduling tasks

Scheduling is a set of reserved tools the agent can call. Enable it in your project settings and four tools become available to the model: schedule_task, list_scheduled_tasks, update_scheduled_task, and cancel_scheduled_task. You do not wire anything up. The agent decides when to use them from what the user asks.

Users do not fill in a form. They just say what they want, and the agent turns it into a task.

"Every weekday at 9am, check my open orders and message me if any are stuck."
"Remind me to review the Q3 numbers next Monday morning."
"Run the weekly summary every Friday at 5pm my time, but only for the next month."

Under the hood each of those becomes a scheduled task with a schedule, a timezone, and a run cap.

When a task fires there is no browser open and no user typing. EERRAA re-signs the user's identity for that run, so the agent acts as the right person with the right private knowledge, vault credentials, and policies, exactly as if they were present. Runs are budget-aware: they draw on the same monthly token budget as live chat and stop cleanly if it is exhausted.

Results do not vanish into a log. They are held and surfaced to the user on their next visit, so a Friday summary is waiting for them Monday morning.

The widget ships a My tasks panel where a user can see their scheduled tasks, what ran, and cancel anything they no longer want. Open it from your own UI with ERA.openTasks(). The panel is backed by the scheduled-tasks API, which you can also call directly with the user's signed identity in the X-Era-User header.

GET lists a user's tasks and results, POST marks results seen, PATCH edits a schedule, and DELETE cancels one. The panel is per user, so a person only ever sees and controls their own tasks.