Zephr Docs

Workspace, hosts & plugins

This page groups the surfaces that carry Zephr onto an end user's host and editor. workspace-sync is the skill/workspace sync plane; workspace-product-surface is the live Slack / Discord / Linear / Notion verb contract; fleet-connect is the Fleet-to-connect handoff (install connection state, MCP export, OAuth/disconnect, devpod-launch enqueue); personal-agent-hosts is the first-party install packages and honesty contract for Hermes, OpenClaw, and Pi; and native-host-plugins is the first-party host-plugin parity requirements. The first three ship; the last two are platform-extension parity surfaces whose install paths ship but whose full command-id coverage is a reviewed target, not a frozen claim.

Capability status

CapabilityTierStatusEvidence
workspace-syncCloses circuitShippedSkill / workspace sync plane
workspace-product-surfaceCloses circuit (Workspace)ShippedSlack/Discord/Linear/Notion verb contract; unreviewed captures
fleet-connectCloses circuit (Connect)ShippedInstall connection state, MCP export, OAuth/disconnect, devpod enqueue
personal-agent-hostsPlatform extensionEvolvingFirst-party install packages + honesty contract for Hermes/OpenClaw/Pi
native-host-pluginsPlatform extensionEvolving12/12 command-id parity; simulator disposition; hook-pack parity

workspace-sync

workspace-sync ships as the skill/workspace sync plane — the band that reconciles a workspace graph across agent clients. It depends on surfaces (the hook vocabulary) and fleet (the profile projection it syncs against).

workspace-product-surface

workspace-product-surface ships the live verb contract for Slack, Discord, Linear, and Notion: the same remember / recall / status / why / bind / help semantics as Claude and Pi, with unreviewed captures (routed through the governance/trust review state) and tenant-scoped reads. A workspace adapter may implement the closed verb set or an honest subset; it never invent a verb the surface does not carry.

fleet-connect

fleet-connect ships the Fleet-to-connect handoff: the installation connection state, MCP export and OAuth/disconnect behavior, and the Launch devpod enqueue surface. The CLI exposes zephr devpod launch as a stub that enqueues a materialization job; the compute-plane runtime owns the actual pod lifecycle. Devpod launch is a materialization contract only — the enqueue returns { devpodId, status: "provisioning", estimatedReadyAt }, and the pod's lifecycle is owned by compute-plane from that point.

personal-agent-hosts

personal-agent-hosts ships first-party install packages and an honesty contract for Hermes, OpenClaw, and Pi host integrations. It complements native-host-plugins / the host-plugin work for Claude, Cursor, and Codex; it does not own the @zephr-ai/pi runtime implementation.

native-host-plugins

native-host-plugins owns first-party host-plugin parity: the 12/12 host-sdk command-id ceiling per host, simulator disposition, status-ledger coverage, hook-pack parity, and the no-unshippable-install-path honesty rule. Agent-side skill/command packs carry every host-sdk command id a host dialect can express (including fleet-profile switch, sync push/adopt, and docs search) instead of the current 8/12 subset; where a host genuinely cannot express a capability, the pack documents the exclusion. In-memory simulators are never counted as products.

Availability

SurfaceTierResidencyNotes
zephr sync (CLI)——Workspace sync entrypoint
Workspace verb contract (/pulse/*-adjacent surfaces)—local, cloudSlack/Discord/Linear/Notion verb surface
zephr hosts emit <platform> (CLI)—localEmit a supported host integration pack
zephr integrations list|install|remove|status—localIntegration pack lifecycle
zephr devpod launch (CLI)—cloudEnqueue-only stub; compute-plane owns pod lifecycle
Host-plugin catalog (check-host-plugin-command-parity.mjs)——12/12 command-id parity check

Egress

SurfacePublic service classPayload classBoundary owner
Devpod materialization enqueuecompute-planemetadata + identityfleet-connect
Workspace signal egressworkspace-surfaceuser-content + metadataworkspace-product-surface

No surface here carries a tenant identifier, queue name, or infrastructure hostname.

Limits and failures

  • fleet-connect devpod launch enqueues work only; a stuck or failed pod is owned by compute-plane, not the connect surface.
  • workspace-product-surface captures are unreviewed on the way in; a recalled workspace belief still carries its UNREVIEWED review state until a human path confirms it.
  • native-host-plugins parity is measured by check-host-plugin-command-parity.mjs; a host that cannot express a command documents the exclusion rather than stubbing it.

fleet (profile projection this surface syncs and connects), workspace-sync (the sync plane), compute-plane (devpod lifecycle), and Data flows: fleet and sync for the handoff sequence.