OpenWork Review: Open-Source Claude Cowork Alternative

TL;DR

OpenWork is a free, open-source desktop app for macOS, Windows, and Linux that lets you run AI agents against your own files and folders. Built on opencode and shipped by Different AI, it positions itself as the open-source alternative to Claude Cowork and Codex — Anthropic’s and OpenAI’s desktop “digital coworker” agents. It’s crossed 20,000 GitHub stars and picked up nearly 3,000 in a single week. Highlights:

• Agent-agnostic MCP — one OpenWork MCP endpoint exposes your skills, plugins, and connected services to Claude Code, Codex, Cursor, OpenCode, or any MCP client, so you don’t have to live in the desktop app.
• Share-first design — create a skill or workflow once, then share it across your own machines, teammates, or friends.
• OpenWork Den — an admin/control-plane layer for teams: provision inference, manage access per model provider, publish skills through marketplaces, and set desktop policies.
• opencode under the hood — inherits opencode’s provider flexibility (Anthropic, OpenAI, local models via Ollama/llama.cpp, and more).
• Two MCP tools — search_capabilities finds what you can use, execute_capability runs it. That’s the whole surface.
• A real licensing asterisk — the project was pitched as MIT, but community members flagged that some components were quietly relicensed and the MIT terms were modified. Read the fine print before you build a business on it.

If you want Cowork-style “AI that touches my actual files” without being locked into a single vendor’s cloud, OpenWork is one of the more polished options. Just go in clear-eyed about the license.

---

What OpenWork Actually Is

To understand OpenWork, you first need to understand what it’s cloning.

Claude Cowork (released by Anthropic as a research preview in January 2026, later GA) is a desktop agent that grew out of Claude Code. Where Claude Code lives in the terminal for developers, Cowork brings the same agentic loop — plan, act, iterate — to a friendlier desktop app aimed at non-coders. It reads and writes files inside folders you explicitly grant, automates local apps, and runs multi-step tasks in a sandboxed VM. OpenAI’s Codex desktop occupies similar ground.

The catch, for a lot of people, is obvious: these are vendor-cloud products. Your workflows, your file context, and your model choice are all mediated by one company’s stack.

OpenWork is the “what if this were open and portable” answer. It’s a desktop app you download and run yourself, built on opencode — the open-source coding-agent runtime from the SST team. The pitch is threefold:

1. You own the workspace. OpenWork runs on your machine against your files, not in a rented VM.
2. You’re not locked to the app. The OpenWork MCP means the same skills and connections work from whatever agent you already use.
3. Sharing is the point. Build a capability once, publish it, and let a team or a friend reuse it.

That third pillar is what separates OpenWork from “yet another opencode wrapper.” Plenty of projects put a GUI on opencode. OpenWork is trying to be the distribution layer for agent capabilities.

Getting Started

There are two ways in, and the docs push both.

Option 1: The desktop app

Download the app from openworklabs.com/download, point it at a workspace, and go. This is the Cowork-equivalent experience: a dedicated window where the agent works on your files.

Option 2: Install via your existing agent

This is the clever bit. If you already use a coding agent, you can hand it a one-line install prompt and let it set everything up:

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?v=hero

Paste that into Claude Code, Cursor, Codex, or ChatGPT, and the agent installs OpenWork, creates a workspace, and opens it. It’s a nice demonstration of the “agents installing agents” pattern that’s become common in 2026 — the install instructions live at a plain .md URL specifically so an agent can fetch and follow them.

Using OpenWork From Any Agent

The MCP integration is the feature I’d actually reach for. Instead of running the OpenWork desktop app, you register its remote MCP server and pull your capabilities into the agent you already live in.

Codex:

codex mcp add openwork --url https://api.openworklabs.com/mcp/agent

Claude Code:

claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent

OpenCode — add this to opencode.json:

{
  "mcp": {
    "openwork": {
      "type": "remote",
      "enabled": true,
      "url": "https://api.openworklabs.com/mcp/agent",
      "oauth": {}
    }
  }
}

Any MCP client — just point at the server URL:

https://api.openworklabs.com/mcp/agent

After you add the MCP, the client opens a browser so you can sign in and pick your OpenWork organization. From there the server exposes exactly two tools:

• search_capabilities — discover the skills, plugins, MCP connections, Google Workspace, and Microsoft 365 capabilities assigned to you.
• execute_capability — run one.

That minimalism is deliberate and, honestly, refreshing. Your agent doesn’t need to understand every downstream integration; it just searches for a capability and executes it. The complexity lives behind the MCP, not in your agent’s context window.

OpenWork Den: The Team Layer

For solo users, the desktop app plus MCP is the whole story. For organizations, OpenWork Den is the control plane, and it’s where the product ambition shows:

• Provision inference at scale and control which members and teams can use each model provider.
• Invite teammates, create teams, and manage access from one place.
• Set desktop policies — restrict local model access and control which app versions your org runs.
• Publish skills and plugins through marketplaces, then assign them to the org, a team, or specific people.
• Import Anthropic-compatible plugins and surface their skills and remote MCPs through the OpenWork MCP.

That last point matters: OpenWork is explicitly designed to consume the same plugin/skill format that Anthropic’s ecosystem uses. So the “Anthropic-compatible” skills you or your team have already built aren’t stranded — they become OpenWork capabilities.

This is the part that reads less like a hobby project and more like a company building a SaaS control plane on top of open-source agent tooling. Which brings us to the elephant in the room.

The Licensing Controversy (Read This Part)

OpenWork was introduced to communities like r/LocalLLaMA and r/ollama as an MIT-licensed open-source Claude Cowork alternative. That framing is a big reason it took off — “MIT” signals you can use, fork, and commercialize freely.

Then developers noticed a problem. A widely-upvoted r/LocalLLaMA thread (“OpenWork, an opensource Claude Cowork alternative, is silently relicensing under a commercial license”) documented that:

it has silently relicensed some components under a commercial license and modified the overall project’s MIT license to limit its reach (which I am not even sure makes it a MIT license anymore).

The concern escalated into a formal GitHub issue, #1412 “Future licensing: is OpenWork going closed source?”, which raised a pointed governance question:

Given how the project gets many contributions from third-party developers, the future licensing plans need to be clarified to avoid misleading developers into contributing to features that will end up providing financial benefits as well as relicensing nightmares for Different-AI.

The maintainers’ answer to “is OpenWork going closed source?” was No — the repo remains open and the desktop app is downloadable. But “not going closed source” and “purely MIT with no strings” are not the same claim. The practical takeaway:

• The core is open and you can run it today for free.
• Some components carry a commercial license, and the top-level license terms have been modified from vanilla MIT.
• If you plan to build a commercial product on top of OpenWork, or contribute significant code, read the actual LICENSE file in the repo as of the commit you depend on — not the marketing copy, and not this article.

This isn’t unique to OpenWork. The same week, r/LocalLLaMA had a parallel blow-up over MiniMax M2.7 shipping a non-open license. Open-washing — pitching a project as “open source” while attaching commercial restrictions — is a recurring 2026 pattern. OpenWork is a genuinely useful tool; it’s just not the no-strings MIT project the initial pitch implied.

Community Reactions

The response has been a mix of genuine enthusiasm and license skepticism.

The upside people cite:

• It fills a real gap. Comments in r/ollama noted that “Claude Code + Ollama + Qwen3 only has Write and Workflow tools, no folder access” — OpenWork’s file-and-folder access with local models is exactly the missing piece.
• The MCP-first approach means you’re not forced into another Electron window if you don’t want one.
• opencode as a foundation gives it credibility and provider flexibility out of the gate.

The skepticism:

• The licensing episode burned some trust. When a project leads with “MIT” and then modifies the terms, the community remembers.
• There’s a broader r/LocalLLaMA fatigue about opencode-adjacent projects and “stealth marketing,” with one thread bluntly calling the sub “a 24/7 OpenCode dick riding + stealth marketing channel.” OpenWork inherits some of that suspicion by association.
• “Not truly local” concerns dog opencode-based tools generally — the OpenWork MCP routes auth and capability resolution through api.openworklabs.com, so the capability layer is a hosted service even if inference can be local.

How It Compares

OpenWork isn’t the only open Cowork alternative — the category filled out fast in 2026:

Tool	Basis	Open source?	Angle
OpenWork	opencode	Core open, some components commercial	MCP-first capability sharing + team control plane
Eigent	Multi-agent	Yes	Local-first, multi-agent workforce
Nimbalyst	Custom	MIT (desktop + iOS)	Visual editors, planning/kanban layer
Paseo	Custom	MIT	Multi-agent, open
Claude Cowork	Anthropic cloud	No	The polished vendor original

If you want the cleanest license story, the fully-MIT projects (Nimbalyst, Paseo) are worth a look. If you want the deepest capability-sharing and team-admin story — and you’re comfortable reading the license — OpenWork is the most feature-complete of the open options right now.

Honest Limitations

• The license is a genuine caveat, not a footnote. Don’t build a commercial product on it without reading the current LICENSE.
• The capability layer is hosted. “Open source” and “runs on your machine” don’t mean “fully self-hosted control plane.” OpenWork MCP auth and org resolution go through Different AI’s servers.
• It’s young and moving fast. Trending repos with thousands of stars a week churn quickly; APIs, licensing, and the Den feature set can shift under you.
• It’s a wrapper, ultimately. The heavy lifting is opencode’s. If opencode’s model support or behavior doesn’t work for you, OpenWork won’t fix that.
• Team features imply monetization. The Den control plane and commercial-licensed components strongly suggest a paid tier is the business model. Free today doesn’t guarantee free-forever for teams.

Should You Use It?

Use OpenWork if:

• You want a Claude Cowork-style file-and-folder agent without committing to Anthropic’s or OpenAI’s cloud.
• You value the MCP-first design so your capabilities follow you across Claude Code, Cursor, Codex, and OpenCode.
• You’re a team that wants a shared, governable set of agent skills and connections.

Look elsewhere if:

• You need an unambiguous, no-strings MIT license — pick Nimbalyst or Paseo.
• You want fully self-hosted with zero hosted dependencies — the OpenWork MCP’s hosted auth layer will bother you.
• You’re allergic to fast-moving, VC-shaped open-source projects where the business model is still crystallizing.

For most individual users kicking the tires, OpenWork is free, polished, and does exactly what it says: gives you a Cowork-like agent on your own files, plus a slick MCP that plugs into the agent you already use. Just keep one eye on the LICENSE file.

FAQ

Is OpenWork really free? The desktop app and core are free to download and run today. However, some components carry a commercial license, and the team-focused OpenWork Den control plane looks positioned for a paid tier. “Free for individuals now” is accurate; “free forever for everything” is not guaranteed.

Is OpenWork actually open source / MIT-licensed? It was pitched as MIT, but the community documented that some components were relicensed commercially and the top-level MIT terms were modified. The maintainers confirmed the project is not going fully closed source, but it’s no longer vanilla MIT either. Read the LICENSE file at the exact commit you depend on before building anything commercial on it.

What is OpenWork built on? opencode — the open-source coding-agent runtime from the SST team. OpenWork inherits opencode’s provider flexibility (Anthropic, OpenAI, local models via Ollama/llama.cpp, and others).

Do I have to use the desktop app? No. The OpenWork MCP (https://api.openworklabs.com/mcp/agent) exposes your capabilities to Claude Code, Codex, Cursor, OpenCode, or any MCP client. Many users skip the desktop app entirely and use OpenWork from the agent they already have.

How is OpenWork different from Claude Cowork? Claude Cowork is Anthropic’s closed, cloud-hosted desktop agent running in a sandboxed VM. OpenWork is open (with the license caveats above), runs on your own machine against your own files, is built on opencode, and is agent-agnostic via MCP rather than tied to one vendor.

Is OpenWork safe to run on my files? It has the same access model as any file-touching agent — it works within folders you grant it. The bigger caution is the hosted capability layer: OpenWork MCP routes auth and org resolution through Different AI’s servers, so it’s not a fully air-gapped local tool even when inference runs locally.