Requests and votes for FleetCommand — the controls you run your fleet with. In your words; we build in order of what matters to operators. The Rules of the register are not on this board: they change only by published edition, at fleetregistry.ai/rules, and corrections are published at fleetregistry.ai/corrections.
What should FleetCommand do next?
Lay up a fleet on a schedule
[Command] Park agents over the weekend or outside business hours and bring them back by survey automatically, so the clock stops when they do.
A mobile view of the console
[Command] Decide an ask, take the watch, raise the condition from my phone.
Show harness and model on the public entry
[Sight] The record already knows what loop an agent runs in and what model it reasons with. Put it on the public page so a relying party can see it without asking me.
Print the muster plan
[Command] One page, per fleet: who answers, who witnesses, what stops at each condition. Something I can pin up or attach to a policy.
A read-only seat for auditors and insurers
[Sight] A member role that can read everything in my account and change nothing — no asks, no orders, no signatures.
Export the Fleet Log
[Command] CSV or PDF of the log for a date range, for the auditor who wants a file, not a login.
Show only part of the record
[Sight] Sometimes a partner needs to see class and nothing else; sometimes only the history. Let me share less than the full entry.
A daily digest of the Fleet Log
[Notices] One message a day: what happened across my fleets, who did it, what needs a person. Email or Slack.
4. Notices in Slack, not only email
[Notices] Survey due, class suspended, a condition coming due — post them to a channel my team already watches.
Works with my harness out of the box
[Integrations] Adapters for Claude Agent SDK, OpenAI Agents SDK, LangGraph and CrewAI, so my runtime states what it did on the record with a few lines, not a rebuild.
Planned
Move an agent to another fleet and keep its history
[Command] When an agent changes hands inside my company, carry its number, its class, its open conditions and its whole record with it. No re-registering, no gap.
Planned
Share a recording with an investigator
Your runtime keeps its own black box — what it saw, decision by decision. Let me hand a segment of it to an auditor or insurer for a set number of days, checked against the seal already on the record, so they can verify it without me sending a spreadsheet.