A follow-up is a durable, one-shot scheduled callback for a channel’s agent. Use one whenever you promise to ping, remind, or check back later. A natural-language acknowledgement is not enough — the promise is only scheduled once the follow-up is created and returns an ID.
You can schedule with an absolute time (--at <iso_timestamp>) or a relative duration (--in <duration>), optionally targeting a thread.
Follow-ups vs workflows
Follow-ups fire once. They do not recur, and they do not watch rows, threads, workflows, webhooks, or external resources for changes.
- Reminder or single check-back → follow-up.
- Recurring schedule, row-change/webhook trigger, reusable multi-step automation, or durable run history → workflow.
If the task is “keep checking until something changes,” the follow-up must explicitly decide whether to schedule the next follow-up and when to stop.
followup is part of the in-workspace agent command surface (workspace_cli), not the external kylon workspace CLI.
