Zephr Docs

Fleet & sync

fleet owns MCP configuration portability — the canonical profile that describes which MCP servers a person runs, under what scope binding, with which credential references — and the deterministic projection of that profile into every client's native, mutually incompatible config file. sync owns the unified reconciliation plane over WorkspaceSnapshot across agent clients, with CLI and MCP parity. Together they close the circuit that continuity opens: after a handoff packet moves the work, fleet moves the setup, and sync keeps every client's view of that setup consistent. fleet does not own Zephr's own MCP endpoint or transport conformance (that is surfaces), nor session/workstream state (continuity), nor admission/identity/tenancy (platform, which fleet consumes without redefinition).

Capability status

CapabilityStatusEvidence
fleetPartialCanonical profile + client projection ship; sweep + revocation
syncShippedUnified WorkspaceSnapshot reconciliation; CLI + MCP parity

fleet

fleet ships the canonical profile artifact, its layering, its client projection, its credential references, capability negotiation, and revocation sweep surface. The credential- sweep projection and process revocation remain unimplemented, and the marketing registry status is planned — so a revoked profile is not yet swept from a live client automatically; the profile document is canonical, but its distributed effect is not enforced at the host edge.

sync

sync ships as the single reconciliation band over WorkspaceSnapshot shared across agent clients, with parity between the CLI (zephr sync) and the MCP surface (zephr_sync_status). The sync plane depends on surfaces for the hook vocabulary and on platform for scope binding; it records no state of its own beyond the reconciled snapshot.

Availability

SurfaceTierResidencyNotes
zephr_sync_status (MCP)coredeferredReconciliation status and last sync epoch
zephr sync (CLI)——Unified reconciliation entrypoint
Fleet profile projection—localPer-client config derivation from the canonical profile

Limits and failures

  • fleet owns credential references, never the credentials themselves; credential material is resolved by platform credential planes and never materialised into a projected client config.
  • Because process revocation is unimplemented, a profile revoked in the cloud is still live until the next manual sweep; zephr sync will surface the drift but cannot kill the host process for you.
  • sync is reconciling, not streaming: a divergent client re-adopts the canonical snapshot on the next sync epoch rather than receiving incremental live edits.

continuity (session/workstream handoff) and agent-envelope-dispatch (MCP-to-Agent dispatch) bound fleet; workspace-sync and fleet-connect consume the profile. See Shared sync and continuity flows for the reconciliation sequence.