Phase 1 — Fork surface. Own browser login, account pages, docs, deeplinks, update hosting, and cloud APIs. The desktop app treats the fork as a first-party service.
Phase 2 — Commercial parity. Optional billing, organization administration, and plan mutation through webhooks. Existing user identities continue to work without migration.
Phase 3 — Independent features. Fork-specific features that do not have an upstream equivalent. These are proposed and tracked in the public issue tracker before they ship.
Upstream Zed changes are merged continuously and rebased into the fork on each release cut.