Desktop app for macOS, Windows, and Linux
A complete local-first workspace for agentic work.
OpenWork roadmapUpdated July 2026
your workspace,
on every surface.
Most people use OpenWork through the desktop app today. It is where you create a workspace, work with files, connect services, add skills, and customize how your agent works.
What you create there should not stay trapped there. OpenWork Connect already brings the same capabilities into compatible agents. Next come persistent hosted workspaces, Slack, mobile, and more.
LiveAvailable today
PartialSupported with limitations
BuildingActive work
NextThe next product horizon
ExploringA direction, not a commitment
01 · the home base
the desktop app is home
The desktop app is the main OpenWork experience. It is where people work with files, run agents, manage sessions, create skills, connect services, and customize a workspace.
The desktop app is where most people configure OpenWork today. Connect is how that configuration travels.
Live
Local files and workspaces
Work directly with the files and repositories already on your computer.
Skills, plugins, MCPs, and connected services
Customize what your agent knows and which systems it can use.
Organization-managed capabilities
Share approved skills and connections without rebuilding every setup by hand.
Artifacts
Preview, edit, download, and reopen generated files without leaving the desktop workspace.
Built-in browser control
Let agents navigate, click, type, and capture pages in a browser that stays visible inside the app.
Isolated sandbox workspaces
Run work in a separate Docker or microsandbox environment, with some platform and setup limitations today.
Better organization for long-running work
Make active, waiting, and completed work easier to understand and return to.
02 · portable by design
your setup follows you
What you configure in OpenWork should not stay trapped in one interface. OpenWork Connect brings the same capabilities into the agents you already use.
OpenWork Connect MCP
Search and run your assigned capabilities through one remote MCP connection.
Codex, Claude Code, Cursor, and OpenCode
Use OpenWork from compatible agents without rewriting skills or changing MCP servers.
Organization marketplaces and access controls
Publish capabilities once and decide which people and teams receive them.
Shared and per-user authentication
Admins can provide a shared connection or ask each member to sign in with their own account.
Git-based publishing and automatic sync
Keep shared capabilities aligned with the repositories where teams build them.
03 · central management
central management
OpenWork Cloud is the control plane for distributing capabilities, applying desktop policies, managing identity and access, and understanding adoption across the organization.
Configure policies and access once in OpenWork Cloud. The desktop app and OpenWork Connect apply them for each member and team.
Desktop policies
Control custom providers, OpenCode Zen, workspaces, settings, extensions, built-in tools, and onboarding by organization, team, or member.
Members, teams, and roles
Invite people, organize teams, and decide who can manage capabilities and security settings.
Skills and plugin marketplaces
Publish skills, commands, MCP dependencies, and extensions once, then assign them to the right people and teams.
Anthropic-compatible plugins
Import Claude-compatible plugin and marketplace manifests and normalize their skills, MCPs, commands, and tools into OpenWork extensions.
SAML SSO
Connect an identity provider and provision organization members when they first sign in.
Usage and adoption telemetry
See active members, sessions, and task outcomes over time using event metadata, never prompts, code, or file contents.
OpenTelemetry coverage
Extend OTLP traces, metrics, and logs across OpenWork services and deployment paths.
04 · work that stays on
a workspace that stays on
Hosted workspaces give a person or team a persistent filesystem and a predictable environment in the cloud. Files, dependencies, repository state, and running work remain available after the laptop closes.
Start with the desktop app. Leave work running in a hosted workspace. Return from the desktop, Slack, mobile, or another surface.
Remote workspace connections
Open a compatible remote runtime through the normal desktop workspace flow.
Persistent hosted workspaces
Give every user or team a durable filesystem and agent environment in the cloud.
Reproducible environments
Provision known tools, dependencies, permissions, and workspace configuration every time.
Long-running and background tasks
Keep work moving without requiring the desktop app or laptop to remain open.
Scheduled workflows
Run recurring work against the same workspace, files, and authenticated services.
Continue from another surface
Move between interfaces without losing the workspace or the work already in progress.
05 · meet people where they work
OpenWork on every surface
The desktop app remains the richest OpenWork experience. Other surfaces provide focused ways to reach the same capabilities, permissions, workspaces, and history.
OpenWork desktop
The complete interface for creating, configuring, and doing work.
Existing AI agents through MCP
Bring OpenWork into the coding and agent tools you already use.
Slack
Start work, receive results, and return to the same workspace from a team channel or private chat.
Mobile
Check work, approve actions, and keep tasks moving away from your computer.
Email and messaging
Reach OpenWork from more of the places where requests and decisions arrive.
Custom organization agents
Build specialized surfaces on top of the same OpenWork workspace and capability system.
06 · beyond a single conversation
systems, not just conversations
Persistent environments and portable authentication make it possible to turn successful agent work into reliable systems that can run again.
Search and execute
Keep agent context small while making the full OpenWork capability catalog available on demand.
Authenticated multi-step execution
Combine multiple services and actions into one controlled server-side run.
Schedules and event triggers
Start work at a specific time or when something changes in a connected system.
Human approvals and resumable runs
Pause at sensitive steps, ask for a decision, and continue from the same state.
Retries, logs, and run history
Make repeated workflows observable and easier to operate when something fails.
Help shape what comes next
what should OpenWork build next?
Tell us which workflow, workspace, or surface would make the biggest difference to how you work.