Overview
Scheduled Task is MuleRun’s automation capability that lets users hand off recurring work—such as “summarize AI news every morning” or “compile a weekly report every Friday”—to the system, which executes them automatically on schedule and delivers each result to a designated destination (MuleRun by default, or a connected IM channel). Unlike one-off conversations, the value of Scheduled Tasks lies in “unattended, recurring execution”: users describe the task and frequency just once, after which no manual triggering is needed—the system runs the task at each scheduled time and delivers the result. Key Characteristics:- Runs on your Computer instance — This is why you must have a Computer first. The interface prompts: “Scheduled tasks run on your Computer instance. Set one up first to get started.”
- Entry location — Found in MuleRun’s Toolbox → Scheduled Tasks (a standalone page at /tool/scheduler), not within the Computer chat interface. The page opens with a calendar view showing each task’s trigger schedule on the timeline, where you can create, edit, pause, resume, or delete tasks.
- Two ways to create — In addition to manually creating tasks on this page, you can also delegate creation from Super Agent Task. In Super Agent, describe something like “summarize AI news every day at 9am”; Super Agent will dispatch the task to your Computer via CLI, where it actually runs (see below).
Target Users
| User Type | Applicable | Typical Needs |
|---|---|---|
| Individual Paid User (Plus and above) | Yes | Daily news/market briefings, periodic reports, regular checks, and other tasks requiring scheduled automatic recurrence |
| Free User | No | Scheduled Tasks is a paid-tier (Plus and above) tool; clicking will redirect Free users to an upgrade prompt |
| Team / Enterprise User | Yes | Used under the team subscription; tasks run on each user’s own Computer instance |
Use Cases
- Daily News Briefing — Create a task “Summarize today’s most important AI news,” set frequency to Daily, and it auto-generates and delivers at the scheduled time each day.
- Periodic Reports — Create a task “Compile this week’s industry trends,” set frequency to Weekly, and the report is auto-drafted each week.
- High-Frequency Polling — Use Every… (custom interval) or Hourly to repeatedly execute a check at minute- or hour-level granularity.
- One-Time Reminder — Use No Repeat + specified date/time to execute only once at a future point in time.
- Send Results to IM — Set the task’s “Send to” to a connected channel like Telegram / Discord / Lark to push results directly into chat.
- Dispatch from Super Agent — Describe your scheduling need within a Super Agent Task, and Super Agent will create the task on Computer via CLI.
Quick Start
The shortest path to “create a scheduled task that auto-summarizes AI news every morning” (requires an existing Computer instance and a Plus-or-above account): 1. Open Scheduled Tasks from the Toolbox in MuleRun. 2. Click New Task. 3. In Title, fill in the task name, e.g., Daily AI News Summary. 4. In Prompt, describe what to do in natural language, e.g., “Summarize today’s most important AI news, list 5 key points.” 5. In Schedule, choose the trigger frequency, e.g., Daily, and set the specific time. 6. In Send to, choose the destination for results—default is Mulerun (default), or you can choose a connected IM channel. 7. Click Create. Once created, the task will appear in the calendar view and trigger automatically at the set time. If there are no tasks yet, the page shows: “No scheduled tasks — Create one to automate recurring work.”Detailed Guide
1. Create / Edit a Task Click New Task to open the task form (when editing an existing task, the title becomes Edit Task). Form fields:- Title — Task name used to identify this task in the list (e.g., Daily AI News Summary).
- Prompt — Describe in natural language what to execute each time; the system carries out the task per these instructions.
- Schedule — Trigger frequency (see options below).
- Send to — Destination channel for execution results; default is Mulerun (default), or select a connected IM channel.
- No Repeat — Execute only once at the specified date and time.
- Every… — Repeat at a custom interval, configurable by seconds / minutes / hours / days (e.g., “every 5 minutes,” “every 2 hours”).
- Hourly — Execute at a specific minute of each hour (e.g., Hourly at :30).
- Daily — Execute at a specified time each day.
- Weekly — Execute on a specified day of the week and time.
- Monthly — Execute on a specified day of the month and time.
- View schedule — See on the calendar when each task will trigger, including Next Run info.
- Edit — Modify the title, prompt, schedule, or send-to channel.
- Pause — Pause the task so it no longer triggers; status becomes Paused.
- Resume — Resume a paused task to trigger again on schedule.
- Delete — Delete the task with a confirmation prompt (“This cannot be undone”); once deleted, cannot be recovered.
- Mulerun (default) — Results are sent back to MuleRun (corresponding to Computer Chat).
- Connected IM channels — If you’ve previously connected channels like Telegram / Discord / Lark / WeChat to your Computer through conversation, they can be selected here, and results will be pushed to the corresponding chat.
Plans, Quotas, and Limits
| Item | Description | Individual Paid | Team | Enterprise |
|---|---|---|---|---|
| Available Tier | Plus and above paid tiers; not available to Free users (will be redirected to upgrade) | ✅ | ✅ | ✅ (Group-shared Knowledge only) |
| Regional Restriction | Currently not available in Mainland China (CN) | ✅ | ✅ | ✅ |
| Prerequisite | Must first have a Computer instance; tasks execute on that instance | ✅ | ✅ | ❌ (future roadmap) |
| Frequency Granularity | Supports No Repeat / custom interval / Hourly / Daily / Weekly / Monthly | Open-source Certified + User-Shared | Open-source Certified + User-Shared | Group-shared only |
| Credits Consumption | Each task execution counts as one task run, consuming Computer Credits based on actual runtime | |||
| Impact of Computer Downtime | Tasks rely on the Computer instance; if the instance is shut down or hibernating, tasks will not execute during that period |