16 , fleet
Fleet operations are where policy quality meets operational reality. A single-agent setup can tolerate manual guardrails; a fleet cannot. As soon as you run many autonomous agents across services, regions, or teams, you need deterministic rollout, fast containment, and clear blast-radius control for policy and runtime changes.
Faramesh fleet commands are designed for two goals: consistency and containment. Consistency means policy state does not fragment across instances. Containment means when one segment misbehaves, you can isolate quickly without freezing unrelated workloads. This is the difference between a targeted incident response and a platform-wide outage.
Rollouts should be progressive and observable. Start narrow, verify decisions and error rates, then widen scope.
List registered agents and current health/trust status.
Push a policy update across a fleet scope. Include a rollout message so operators can map behavior changes back to a specific control event during audits and incident triage.
Emergency deny for all tool execution across selected fleet targets. Use kill for containment, then restore by policy correction and staged re-enable, not by blindly unfreezing everything.
These mistakes cause the most avoidable outages in large deployments:
At fleet scale, governance failures are distribution failures as often as policy logic failures. Rollout discipline is a security control.
Need help? Use any of these support options.