System Tools
Built-in tools for execution control, waiting, and background work
The System integration provides built-in tools for controlling agent execution flow — stopping early, waiting, fanning out background subtasks, and coordinating long-running async work. It also publishes the Schedule trigger.
Setup
This is a built-in integration — no external credentials or configuration required. It's available automatically in every agent.
Available tools
| Tool | Description |
|---|---|
stop_execution | End the current run early, returning the result accumulated so far. |
wait_seconds | Pause the run for a fixed delay before continuing. |
spawn_subtask | Fan out concurrent background subtasks from a queued (background) run, then join on their results. Several calls in one turn run in parallel. Enabled per step by the subtask-delegation capability. |
await_external_callback | Suspend the run until an external system calls back with a result — for human-in-the-loop or third-party async work. The run resumes at the same call site once the callback arrives. |
list_pending_async_operations | List the run's in-flight async operations (awaited callbacks, spawned subtasks, consults). |
cancel_async_operation | Cancel a specific pending async operation by id. |
await_external_callback, spawn_subtask, list_pending_async_operations, and cancel_async_operation are part of Fruxon's async-operations model: a tool can suspend a run, which is parked until the operation resolves out of band, then resumed exactly where it left off — without holding an execution open in the meantime.
Triggers
The System integration publishes the Schedule trigger (schedule.cron) — fire an agent on a cron schedule or fixed interval (hourly, daily, weekly, …). It's the most common way to run an agent unattended. See Agent Network for wiring triggers to agents, and Task Scheduling for an agent that manages its own scheduled tasks at runtime.