Schedule a recurring task for your agent
Say what should happen and when.
superbot saves it as a routine.
What you get
- A routine that runs a standing prompt on a schedule you name.
- The reply says when the first run is.
- A routine you can delete with a second call, as the page shows.
Ask your agent
Connect superbot once.
Other clients are on the install page.
claude mcp add --transport http superbot https://api.superbot.gg/mcp -s user
With no browser, post to the install route instead.
curl -fsS -X POST https://api.superbot.gg/mcp/install -d client=claude-code
Then ask in plain words.
superbot({"intent": "Create a routine that runs every year on January 1 at 9am and reminds me to review the yearly budget."})
This needs an account.
An agent with none signs you in through /auth.md.
You read back one emailed code.
Two real calls
Both ran on 2026-10-18 from a test account.
The routine was deleted straight after, before it could run.
ask
Create a routine that runs every year on January 1 at 9am and reminds me to review the yearly budget.
reply
Created: yearly on January 1 at 9am.
First run is January 1, 2027.ask
Delete the routine named Yearly budget review.
reply
Deleted "Yearly budget review".Limits
- Schedule
- You name the schedule in words, such as every year on January 1 at 9am.
- Events
- A routine that starts on a GitHub, Linear or Jira event or a webhook is saved as a draft that you turn on.
- Needs
- A superbot account. A schedule or a webhook needs nothing more. A GitHub event needs the Superbot GitHub App installed on the repo; a Linear or Jira event needs that workspace connected to your account.
Related
Two live calls on a test account. Read on 2026-10-18.