Scheduled tasks
Scheduled tasks are stored on the WECOMMANDER service, not in the operating system's scheduler. Tasks on an agent device run through its agent, even while your own computer is off; tasks on a saved SSH server run from your desktop app, which holds the SSH credentials.
Create a task
- Open Scheduled tasks in the dashboard (Workspace → Scheduled tasks) or in the desktop app.
- Name it, choose the target (an agent device; SSH servers are chosen in the desktop app) and enter the exact command.
- Choose the schedule, the time zone, the time limit and when to e-mail you. The next five run times are shown before you save.
- Confirm. Creating the task is the approval for its runs: it runs at each due time without asking again. Check the command before saving.
Schedules
| Kind | Example | Notes |
|---|---|---|
| Every N minutes | every 30 minutes | 5 minutes to 7 days; the first run is one interval after saving. |
| Cron (advanced) | 0 3 * * * (03:00 every day) | Standard five fields: minute hour day month weekday; ranges, steps, lists and month/weekday names. A day matches if either day field matches. |
| Once | 2026-12-01T09:00+03:00 | A time in the past is refused. |
Times are wall-clock times in the task's IANA time zone (default Europe/Istanbul). A time skipped by a daylight-saving change runs right after it (02:30 becomes 03:30); a time that occurs twice runs once.
Options
- Time limit: 10 seconds to 1 hour (default 10 minutes); a run that takes longer is stopped and marked failed.
- Notification: e-mail on failure (default), always, or never. Failed and missed runs are e-mailed to the task's creator, or to the owners and admins when an API token created it.
- Enabled: turn a task off without deleting it.
Runs and history
- Exit code 0 is succeeded; any other is failed. Output (stdout, then stderr) is kept up to the last 64 KiB with secrets masked.
- A device that is offline at the due time gives a missed run. If the previous run is still running, the new one is skipped.
- No catch-up storm: after an outage a task runs once, then continues on its schedule.
- SSH tasks need the desktop app to be open and signed in; a run not picked up within 15 minutes is missed.
- Run now runs a task once outside its schedule. Finished runs are kept for 90 days.
Who can do what
Anyone in the workspace can read tasks; creating, changing, deleting and running them needs the owner or admin role. Every change is in the audit log with the exact command. The agent's own limits still apply: a device with commands switched off refuses the run.
Limits
The Free plan keeps up to 10 scheduled tasks; no workspace can have more than 100.
For AI
scheduled_tasks_list is read-only. scheduled_task_create (agent devices only), scheduled_task_update, scheduled_task_delete and scheduled_task_run_now need a human approval of that exact change, unless the task's device is on full trust. Tasks on SSH servers always need an approval, command allowlists do not apply, and the device's safety net refuses catastrophic commands.
- Server timers, cron and Windows tasks: View and manage a Linux server's systemd timers, read its cron jobs, and manage this computer's Windows Task Scheduler from WECOMMANDER, with the exact command shown first.
- MCP tool reference: Every WECOMMANDER MCP tool, grouped: what it does, its risk and approval rule, where it works (agent devices, SSH servers, Linux only) and its key arguments.
- AI permissions: trust levels, allowed commands, root and the safety net: Set per device and per SSH server what AI may do without asking: strict, standard or full trust (time-limited or not), allowed command patterns, run as root with two keys, the safety net and autonomous mode.