OpenWork — Open-Source Desktop App for AI Workflows
OpenWork is a free open-source desktop app alternative to Claude Cowork for sharing AI workflows across Claude Code, Cursor, Codex, and more.
If you use multiple AI coding agents — Claude Code for one task, Cursor for another, Codex for automation — you’ve probably wished you could share your skills, MCP connections, and integrations across all of them. Each agent has its own config, its own tools, its own setup.
OpenWork solves this by giving you a free, open-source desktop app that acts as a shared platform for AI workflows. Create a skill once, and use it from any agent. Connect Google Workspace or Microsoft 365 once, and every agent has access.
What is OpenWork?#
OpenWork is an open-source desktop app (macOS, Windows, Linux) and control plane for sharing AI workflows across tools, teammates, and machines. It’s built by the same team behind OpenCode Scheduler ↗ and runs on top of OpenCode.
Think of it as an open-source alternative to Claude Cowork — but one that works with any compatible AI agent, not just Anthropic’s ecosystem.
The desktop app provides a dedicated workspace when you want one, but it’s not required — you can use OpenWork entirely through your existing AI agent via its MCP server.
How It Works#
The OpenWork MCP#
At its core, OpenWork exposes a remote MCP server that any compatible agent can connect to. It provides two tools:
search_capabilities— Find what skills, plugins, and connections are available to youexecute_capability— Run a capability from any connected agent
After adding the MCP, your client opens a browser for you to sign in and choose your OpenWork organization. From there, all your assigned capabilities are available in any agent you use.
Agent Integration#
Connect OpenWork to your preferred agent:
Codex:
codex mcp add openwork --url https://api.openworklabs.com/mcp/agentbashClaude Code:
claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agentbashOpenCode:
{
"mcp": {
"openwork": {
"type": "remote",
"enabled": true,
"url": "https://api.openworklabs.com/mcp/agent",
"oauth": {}
}
}
}jsonAny MCP client:
Remote MCP URL: https://api.openworklabs.com/mcp/agenttextQuick Install#
Copy this prompt into Claude Code, Cursor, Codex, ChatGPT, or any agent that can run commands:
Install OpenWork on my computer, set up my first workspace, and open it ready to use. Follow the steps in https://openworklabs.com/start.md ↗
This installs OpenWork, creates your workspace, and opens it ready to run.
Key Features#
Shared Capabilities#
Create a skill, plugin, or MCP connection once and use it from any agent. No more duplicating configs across Claude Code, Cursor, Codex, and OpenCode.
Google Workspace & Microsoft 365 Integration#
Connect your Google Workspace or Microsoft 365 account once. Every agent that uses OpenWork gets access to your documents, sheets, emails, and calendar — no per-agent setup needed.
OpenWork Den (Team Management)#
For organizations, OpenWork Den provides a control plane for managing AI workflows across teams:
- Inference provisioning — Control which members and teams can use each model provider
- Access management — Invite teammates, create teams, and control access from one place
- Desktop policies — Restrict local model access and control which app versions your organization can use
- Marketplace publishing — Publish skills and plugins through marketplaces, assign them to org, team, or specific people
- Plugin import — Import Anthropic-compatible plugins and make their skills and remote MCPs available through OpenWork
Workspace Isolation#
Each workspace has its own profile, keeping skills, connections, and configurations separate. You can have different workspaces for different projects or clients.
Why OpenWork Matters#
If you use more than one AI coding agent, you face a fragmented experience. Skills you build for Claude Code don’t carry over to Cursor. MCP servers configured in one tool need to be reconfigured in another. Google Workspace integration requires separate setup per agent.
OpenWork solves this by decoupling capabilities from agents. You define your skills, connect your services, and configure your tools once — then access everything from any compatible agent.
It’s the same philosophy that made OpenCode Scheduler successful: thin wrappers around established infrastructure (in this case, MCP protocol), adding just enough platform to make the experience seamless.
OpenWork vs. Claude Cowork#
| Feature | OpenWork | Claude Cowork |
|---|---|---|
| Open source | ✅ Yes | ❌ No |
| Desktop app | ✅ macOS, Windows, Linux | ✅ Yes |
| Agent-agnostic | ✅ Any MCP-compatible agent | ❌ Claude Code only |
| Team management | ✅ OpenWork Den | ❌ Limited |
| Google Workspace | ✅ Yes | ❌ No |
| Microsoft 365 | ✅ Yes | ❌ No |
| Marketplace | ✅ Plugin & skill marketplace | ❌ No |
| Plugin import | ✅ Anthropic-compatible plugins | ✅ Yes |
Summary#
OpenWork transforms how developers work with AI coding agents. Instead of managing separate configurations for each tool, you build your capabilities once and access them from anywhere. It’s an open-source, agent-agnostic platform for the age of multi-agent development.
Backed by the same team behind OpenCode Scheduler, OpenWork is rapidly becoming an essential part of the AI development stack — especially for teams that use multiple AI coding agents.