CLI reference

fleet fabric

Name: Fleet
Author: Fleet

fleet fabric <publish|claim|handoff|blocker|artifact|ack|tasks|inbox> [flags]

The agent coordination layer: publish fabric events, claim and hand off tasks, raise blockers, attach artifacts, acknowledge inbox items, and list tasks or an agent's inbox. The fabric is the shared event bus all agents and daemons use to coordinate across repos.

When ~/.fleet/fabric.sock is present, operations go through the socket; when absent, Fleet falls back to direct SQLite. fleet fabric publish requires --kind, --sender, and --summary (or the --event shorthand). Most day-to-day fabric traffic is automatic; this command is for debugging and manual intervention.

Flags

--kind <kind>	Event envelope for publish (task, claim, handoff, blocker, artifact, decision, note, status) — required
--sender <agent>	Agent publishing the event (or system:<label> for non-agent senders) — required for publish
--summary <text>	Short description of what happened — required for publish
--payload <json>	Optional structured JSON payload consumers read (must be valid JSON)
--event <name>	Chain-event shorthand for publish: equivalent to --kind note --summary <name> (e.g. ticket_ready, pr_approved)

Examples

Publish a reactive-chain event via the --event shorthand

fleet fabric publish --event ticket_ready --sender system:operator --payload '{"issue_number":42}'

Publish a decision event

fleet fabric publish --kind decision --sender tech-lead --summary pr_approved --payload '{"pr_number":99}'

List an agent's inbox

fleet fabric inbox --agent tech-lead

Frequently asked questions

What does fleet fabric publish require?

Envelope form requires --kind, --sender, and --summary; the chain shorthand requires --event and --sender. A positional form is rejected, and --payload, when present, must be valid JSON.

What happens if fabric.sock does not exist?

Fleet falls back to direct SQLite access. The watcher daemon creates the socket when it starts; it is optional.

Related commands

fleet event →fleet watcher →fleet log →

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet