Talk to us ↗DELEGATION & AUTOMATION
Combine focused delegation, reusable skills, scheduled runs, and delivery channels. Start with a task you can inspect, then expand the workflow deliberately.
04 / WORK THAT MOVES FORWARD
Break a larger task into focused workstreams, or run a repeatable workflow on a schedule. These illustrations show supported patterns, not live execution.
Child agents work with fresh conversations, inherited tool access, and their own terminal sessions. Their final summaries return to the parent for coordination.
Read about delegation ↗A one-time schedule, recurring cron expression, or configured webhook event.
Run a fresh agent session with relevant skills, or use script-only mode for a deterministic job.
Send output to the origin chat, a configured platform target, or local files.
Create, pause, resume, edit, and trigger jobs through the scheduling tools. Pick the delivery destination that fits the task.
Explore scheduled tasks ↗WORKFLOW PATTERNS
ONE GOAL. FOCUSED ROLES.
A parent agent can coordinate focused child tasks, bringing their final summaries back together. Clear goals and relevant context help each workstream stay useful.
Give each task relevant context and an expected output, then use the parent conversation to compare results and decide what happens next.
Example pattern: assign independent questions to child agents, collect final summaries, and have the parent compare findings. Validate the result against the sources the task requires.
Example pattern: keep coordination in a parent conversation while child tasks inspect a problem, build a change, or review a result. Give each task clear context and an expected output.
Example pattern: attach skills to a scheduled session, gather information from configured tools, and deliver a brief to a chosen channel. Data access depends on those integrations.
DESIGN THE HANDOFF
Define the goal, context, and final output. Child agents start with fresh conversations and their own terminal sessions. Their final summaries return to the parent, rather than a full copy of each conversation.
Independent subproblems suit parallel work. Tightly dependent tasks need coordination so one result is available before the next step begins.
Choose a trigger, attach skills, and identify where output should go. Jobs can run once, recur, or respond to configured webhook events.
Script-only mode runs a scheduled script and delivers output without an agent or LLM step. Select the mode appropriate to the task.
OPERATE THE WORKFLOW
Create, pause, resume, edit, trigger, or remove a job. Review the trigger and destination before relying on a recurring workflow.
Scheduling reference ↗Skills package instructions that a workflow can load when needed. Reuse them across interactive work and scheduled sessions.
Skills reference ↗Unattended sessions can encounter command approval boundaries. Review how jobs should behave when no person is present.
Approval behavior ↗