Set up an agent fleet

From management#

Open crossfire’s Set up an agent page. Paste the personalized guide into an agent with shell access on your machine. The guide pins the public fleet package to the instance’s release and runs noninteractive setup:

fleet setup --descriptor 'https://example.test/onboarding/setup.json?ownerMatrixId=%40member%3Aexample.test'

Use the actual personalized URL, not this example. Setup validates the exact owner, origin and installed release. It creates/reuses a private controller and a project-derived one-agent fleet, displays the exact approval code/URL, waits for owner approval in ordinary code, then checks readiness. Setup asks no configuration questions and makes no model call.

The agent running setup keeps its own process, history and permissions. fleetd creates a separate managed session. Existing approved identity/history is reused on repeated setup; an explicitly stopped binding stays stopped.

Prerequisites#

Install the selected fleet/fleetd implementation first. Node npm packages and the managed, NativeAOT and Rust distributions have separate installation guides. The setup command and product configuration are shared; native fleet selects its sibling controller, not a different implementation on PATH.

Installation and packaging by target

The host must already have the selected native runtime and provider login. Codex is the default. Pi requires an explicit ordinary roster and verified native 1.0.0. Setup reports missing prerequisites; it does not silently upgrade a runtime, copy the current conversation or weaken native permissions.

Optional configuration#

fleet setup --descriptor 'https://example.test/onboarding/setup.json?ownerMatrixId=%40member%3Aexample.test' \
  --root /absolute/private/controller \
  --config /absolute/private/fleet/runtime.toml

The configuration must match the descriptor’s server and owner. Unknown fields, duplicate names and unavailable model/effort combinations fail. Role definitions, skills and workareas follow the normal fleet loader.

For a complete example, fleet-street generates a private ten-agent theatre fleet from public templates:

python3 -m tools.fleet_street configure \
  --server https://chat.example.org \
  --owner '@alice:chat.example.org' --prefix alice-fs
./node_modules/.bin/fleet setup --config "$(pwd)/.local/fleet/runtime.toml"

Run these in the example directory after installing its matching tools. Replace the placeholder server and owner. Configure prepares the files; setup then shows the roster for you to approve in crossfire. See the setup and prerequisites .

After approval#

Inspect fleet list, fleet show FLEET and fleet agent list FLEET.
Run fleet test FLEET for model-free readiness.
Create ordinary rooms in Element and grant only needed participation.
Configure wake senders independently of room membership.
Send an actual authorized task through the room, DM or explicit fleet message.

Enrollment creates no chats. A protected owner DM is created on first contact, terminal output or a question. Closing the CLI does not stop the controller.