TheDocumentation Index
Fetch the complete documentation index at: https://docs.agentastic.dev/llms.txt
Use this file to discover all available pages before exploring further.
dev task command manages Agentastic scheduled tasks through the app’s local IPC socket. Use it to create recurring or one-time tasks, check execution history, and control task state — all from the terminal or from within an agent workflow.
Usage
Commands
List tasks
Returns all scheduled tasks and their latest execution summary.View history
Returns the execution history for all tasks, or for a specific task by ID.Run a task manually
Trigger a task immediately, regardless of its schedule.Pause and resume
Pause a task to stop it from running on its schedule, or resume it to re-enable it.Delete
Permanently remove a task.Creating tasks
Usedev task create with --name, --command, and --schedule to create a new task. The --schedule flag determines the schedule type and which additional flags are required.
Once
Run a task a single time at a specific date and time.Interval
Run a task repeatedly at a fixed interval in seconds.Daily
Run a task every day at a specific hour and minute.Weekly
Run a task on a specific day of the week at a specific time. The--weekday flag accepts values 0 (Sunday) through 6 (Saturday).
Monthly
Run a task on a specific day of the month at a specific time.Cron
Run a task on a custom cron schedule.Updating tasks
Usedev task update to change a task’s name, command, or schedule. Pass --task-id to identify the task, then include any fields you want to update.
Optional flags
The following flags are available on bothcreate and update commands.
| Flag | Description |
|---|---|
--working-directory <relative-path> | Working directory for the task, relative to the selected workspace, repo, or worktree root |
--workspace-url <file-url> | Target a specific workspace by file URL |
--repo-url <file-url> | Target a specific repository by file URL |
--worktree-url <file-url> | Target a specific worktree by file URL |
--max-concurrency <n> | Maximum number of concurrent executions |
Working directories must be relative to the selected workspace, repo, or worktree root — not absolute paths.