Roadmap
What is being built next — gathered from the honest status line every other page already carries.
Every page in these docs carries a status. ships means it works today. partial means part of it is live and part is gated, and the gate is spelled out at the top of that page. This page collects those gates in one place, so you can see what is coming without reading all of them.
Nothing here has a date. These are the lines being wired next, and each one links to the page where it lives.
Getting in
The companion is a macOS app, and it is what flashes your board and pairs your device. It is in closed beta — builds open to the waitlist in waves rather than all at once.
Building on Zeph
Three things you build — device apps, published bundles, the catalog — are first-party today and opening up next.
The guest SDK for device apps is not published yet, so authoring a device app is first-party only for now. You can still build one against the real renderer by copying an example rather than running a scaffold — the quickstart walks that path.
Publishing a bundle to others waits on the production publisher key, which is not issued yet. The dual-signing format that binds code, capabilities and version together already works; what is missing is the key that lets a third party sign for the store.
The catalog installs signed, first-party apps today. It is not open for third-party submissions yet — until it is, an app you build installs from a local .zeph-app file.
Choose your surface
The three ways to build on Zeph, ranked by how ready each one is.
Publishing
How a bundle is signed, and where the third-party path stands.
Install an app
From the catalog, or from a local file while submissions are closed.
The assistant's reach
The companion's assistant runs today with its built-in tools. Two ways of extending its reach are being wired.
Your own MCP tools. The assistant already calls built-in tools; connecting an MCP server of your own into it is in progress.
Connectors that act. Signing into an account — Gmail, Calendar, Slack — works now. Having a connector act through that account on the assistant's behalf is the part still being wired: the door exists, but nothing runs actions through it yet.
Tool
What the assistant can call — and connecting your own MCP server into it.
Connector
A signed-in door into an account. Acting through it is coming.
How to read status anywhere in the docs
A partial page states its own gate in the frontmatter, right under the title — one line naming exactly what is live and what is not. If a page says ships, all of it works today. This roadmap is only the gates, gathered.