Skip to main content

​
agentsfleet documentation

​
What it is

agentsfleet runs fleets that respond to events. A fleet can inspect data, call allowed tools, and return a result. Each fleet uses a SKILL.md file and an optional TRIGGER.md file. The first file defines its task; the second defines its access.

​
Why it exists

Use a fleet for repeated work that starts from a webhook, schedule, or message. You keep approval over sensitive actions.

​
How it behaves

Create a workspace, save the required secrets, and install a fleet. Then connect the trigger source shown by the install output. Every event creates one run. You can inspect the run through the activity stream. Start with the quickstart. It shows the shortest complete path from installation to a GitHub event.

​
Limits

A fleet can use only the tools, secrets, and network hosts declared in its files. Budget and account limits can stop new runs. The service is in early access. Public behavior may change before version 2.0.0.