Skip to main content

What this does

This creates a fleet from one published Library revision. You review the revision’s setup under your fleet name, then save it. Saving pins the fleet to that revision. A later revision of the same entry never changes the fleet until you apply it yourself.

Before you begin

Sign in and select a workspace. Save every secret the entry needs; the review lists them. <MODEL_REF> names an authoring model the workspace owner enabled. Author a fleet shows where it comes from. A Library draft starts without a chat message, so no authoring model call runs.

Steps

  1. Browse the workspace gallery.
    The gallery holds both tiers. TIER reads platform for an entry every workspace sees and tenant for one your account owns. REVISION is the entry’s latest revision.
  2. Open a private draft from that revision and review it under your fleet name. <LIBRARY_ID> and <REVISION_ID> come from the gallery. <NAME> is the fleet name you choose.
    The review shows the full setup, the secrets, tools, and network hosts it needs, and a readiness line for each.
  3. Save the draft with the digest you reviewed.
    Add --run-now <MESSAGE> to send the fleet one message once it is active.
  4. Read the fleet’s webhook URLs, if its setup declares a webhook trigger. <FLEET_ID> comes from agentsfleet list.
    Each webhook_urls entry pairs a source with its url. For GitHub, open Repository settings → Webhooks → Add webhook. Use the matching workspace webhook secret.
In the dashboard, open Fleet library, choose an entry, and choose Start chat from this revision.

Verify it works

Waiting counts approvals that need your decision. A count above zero also prints the command that lists them.

Common problems

A Save that prints installing and exits with code 1 is waiting on a setup check. The lines after it name each check, such as a missing secret or a pending integration grant, and its next step. Fix each check, then run agentsfleet resume <FLEET_ID> to check again. The fleet keeps its identifier while it waits. UZ-AUTHOR-006 means the setup or its access changed after your review. Review again and save with the new digest. UZ-AGT-006 means the fleet name already exists. Review again under a different --name.
Deleting a fleet permanently removes its events, sessions, schedules, integration grants, connector channels, and memory. Choose a different name to keep the existing fleet and its data.
To reuse the taken name, run agentsfleet kill <FLEET_ID>, then agentsfleet delete <FLEET_ID>. Deletion releases the name. A Save whose reply was lost, or that stays installing, prints a recovery line with --operation-id and --candidate-id. Repeat the same command with both flags to resume that Save without creating a second fleet.

Remove or undo

Deleting a fleet removes its events, telemetry, sessions, grants, keys, and memory. This loss cannot be undone. <FLEET_ID> comes from agentsfleet list. Kill the fleet before deleting it.