Skip to main content

​
fased task

Use fased task to manage Agent-owned scheduled work from the terminal. Browser equivalent: Agent > Tasks for the selected Agent. Related: Run fased task --help for the full command surface.

​
Common flow

Create a recurring isolated task:
Choose exactly one schedule flag: --at, --every, or --cron. Isolated tasks use --message. Main-session tasks use --system-event. Operate the task:
Inspect runs:

​
Run control

Use run-id commands when a specific queued or leased run is stuck, failed, or needs retry:
These operate on run ids, not task ids.

​
Repair and sources

When a task stops because access, source quality, or evidence is missing, use:
Trusted source memory:

​
Workflows and graphs

Inspect workflow runs:
Preview or run graph JSON:

​
Ask Agents

Tasks can store coordination intent for local Agent review:
The run detail shows helper Agent evidence under the same run-history chain.

​
Workers

Run an external task worker:
Install a supervised worker:
The gateway schedules runs. Workers lease queued steps and write results back to the same local task store.

​
Smoke checks

Use --keep when you want to retain temporary smoke tasks for inspection.

​
Channel commands

Connected command surfaces can create and edit tasks with natural text:
Tasks created from Chat, Telegram, Discord, Slack, or another channel are still owned by an Agent and Session and appear in Agent > Tasks.

​
Compatibility

The internal RPC/storage names still use cron.* and ~/.fased/cron/.... Prefer fased task ... in user docs and normal operator instructions.