Schedule a message to the agent, or into its conversation with a user
Schedule a message to the agent.
It fires as the agent's owner and the agent runs a turn on it; whoever created it is stamped on the message.
By default it lands in the owner's conversation with the agent — the agent's durable home, yours if you own it.
With --user it lands in the agent's conversation with that user instead — visible to them (that conversation must already exist).
Start the instruction with /clear on its own line to run each firing from a clean context — the agent will not see earlier conversation history, including previous runs of the same schedule.
mutiro agents schedule message <agent> <instruction> [flags]
| Flag | Type | Description |
|---|---|---|
| --catch-up | string | Catch-up policy: skip-missed or catch-up-once (default "skip-missed") |
| --cron | string | Standard 5-field cron expression |
| --ends-at | string | Optional schedule end boundary (RFC3339) |
| -h, --help | bool | help for message |
| --interval-anchor-at | string | Optional anchor time for interval schedules (RFC3339) |
| --interval-every | string | Run at a fixed interval (for example 1h, 24h, or 7d) |
| --max-occurrences int32 | bool | Optional maximum number of sends |
| --metadataToString | string | Message metadata key=value (repeatable) (default []) |
| --once-at | string | Run once at RFC3339 time with explicit offset |
| --starts-at | string | Optional schedule start boundary (RFC3339) |
| --user | string | Target the agent's conversation with this user instead of yours (visible to them, sent as you) |
| Flag | Type | Description |
|---|---|---|
| --addr | string | Scheduling service address (defaults to config) |
| --config | string | config file (default is ./.mutiro.yaml in current directory) |
| --debug | bool | debug mode |
| --json | bool | Output in JSON format |
| --timezone | string | IANA timezone for cron and wall-clock schedules |
| -v, --verbose | bool | verbose output |