# roadmap-every-surface — The desktop app is home and the same workspace expands to every surface

This demo proves the public roadmap tells one coherent product story on both the landing and docs routes.

1. The roadmap now starts with a plain-language introduction and goes directly into the dated product sections. The large system diagram is gone, so the status labels and written roadmap carry the story.

2. The desktop section makes the current product clear. Files, skills, artifacts, and built-in browser control are live in the main OpenWork experience, isolated sandboxes are partially supported, and better organization for long-running work is being built.

3. OpenWork Connect is how that setup travels. The roadmap shows one MCP connection bringing the same capabilities into Codex, Claude Code, Cursor, and OpenCode while keeping marketplace access and authentication under organization control.

4. OpenWork Cloud provides central management for the organization. Admins can apply desktop policies, assign marketplace skills and Anthropic-compatible plugins, manage identity with SSO, and understand adoption through telemetry.

5. Hosted workspaces are the next runtime layer. A persistent filesystem and reproducible environment keep files, dependencies, repository state, and background work available after the laptop closes.

6. From there, OpenWork reaches people on more surfaces. Desktop and compatible agents are live, Slack and mobile are next, and email, messaging, and custom organization agents are being explored.

7. The docs route presents the same shared roadmap, including central management and the full desktop capability list. The specifications section is gone, so the page closes with the product roadmap and an invitation to share feedback.
