Interfaces
Platform Reference
Understand how local agents, the macOS app, governance policy, and the managed Multiplayer OS platform fit together.
Recommended path
Local agents have one supported integration path: write event JSON, submit it with mos event submit --file -, and let the menu bar app handle review, sign-in, and workspace routing.
The managed platform handles accounts, workspace access, source connections, policy, sync, audit history, and approved workspace records. Local agents stay on the mos path.
Agent surface
mos event submit --file -- Queues a local pending proposal for menu bar review.
mos event validate --file -- Checks event JSON before a skill submits it.
mos doctor- Confirms the CLI, app connection, sign-in, and workspace routing are ready.
Credential boundary
Credentials and workspace routing stay inside the menu bar app. A local agent emits JSON to mos and stops there.
Governance surface
- Policy
- Workspace policy decides which agents can read or write wiki paths, use skills, touch sources, or perform external actions.
- Approvals
- The platform stores reviewable proposals and decision outcomes so important agent work has an explicit human step.
- Audit
- Approved events retain producer, actor, source references, privacy posture, artifacts, action results, and timestamps.
- Rollback
- Workspace writes should be reversible so a mistaken approved change can be corrected without losing history.
Managed app flow
- Account sign-in
- The app connects the device to a Multiplayer OS account through the managed platform.
- Device session
- The app keeps the device signed in so agents can submit local proposals without handling platform credentials.
- Workspace sync
- The app loads accessible workspaces and syncs approved proposals to the selected workspace.
- Review continuity
- The app and dashboard show the same underlying proposal, status, and audit result so review can move between surfaces.