Operate
Operate a Fleet
Route each operational outcome to its owning Skill and native authority.
Fleet operations are conditional judgment, not a memorized command list. Each page explains when a capability applies, what it owns and what you should observe. The linked versioned Skill owns the ordered procedure for the selected release.
Explore this section
Delegate an outcome
Turn accepted intent into one bounded, owned and deliverable Assignment.
Create a Second Mate
Add one persistent domain leader only when a durable charter justifies it.
Supervise and steer
Reconcile durable work with live runtime state and correct moving work precisely.
Ask for a decision
Preserve consequential questions and exact answers without inferring from prose.
Work with projects
Preserve the repository, provider and selected delivery workflow as authorities.
Agent memory
Recall and maintain private Mate context without confusing it with authority.
Choose a harness
Select and operate only launch shapes verified by the chosen AgentOS release.
Authentication
Keep credentials inside the owning Agent boundary and choose identity deliberately.
Fleet AI Gateway
Optional pooled model capacity without making a proxy mandatory for AgentOS.
Upgrade AgentOS
Reconcile an immutable release without losing the Mate home or loaded instructions.
Diagnose and recover
Establish causality, inspect native authorities and preserve accepted work.
Native interfaces
Use PostgreSQL, Kubernetes, Herdr, Git, PVCs and providers through their native interfaces. Stop at an unverified boundary instead of constructing behavior from documentation prose.
Last updated on