I Cancelled My $20 Claude Cowork Plan After a Week With OpenWork

I didn't expect to cancel. I'd been paying for Claude Cowork, it worked, and switching tools is usually more hassle than it's worth. Then I spent a week running OpenWork — open-source, free — on actual work instead of a toy demo. By Friday I'd cancelled the plan.

Here's the honest version of what happened, including the part that nearly made me quit on day one.

The setup that took two minutes

I went in skeptical. Free open-source agent clients usually mean "free, but you'll spend a weekend configuring it." OpenWork wasn't that.

It ships with a provider called OpenCode Zen, and there are five free models sitting in the selector before you sign into anything — DeepSeek V4 Flash, Qwen3.6 Plus, MiniMax M2.5, and two more. No card, no subscription. I picked DeepSeek, handed it a refactor task on a real repo, and it generated the diff, applied it, tests green on the first run.

That was the moment the skepticism dropped. Same task in Cowork needs the $20 plan. Same machine, two windows, one charges and one doesn't.

The thing that actually sold me

It wasn't the free models. It was MCP setup.

If you've added an MCP server to Claude Cowork, you know the drill: open the JSON config, find the right format, paste the server command, restart, hope it loads. I'd timed it once — about twenty minutes for five tools the first time.

In OpenWork it's a tile with a Connect button. Notion, Linear, Sentry, Stripe, Context7 — tap, OAuth, done. All five connected in under three minutes. No JSON. That's the whole story. After fighting config files for months, that one button is what made me close the Cowork tab.

The part I didn't see coming

You can tell the agent to drive its own UI. I typed "open Settings, then go to Appearance" and watched the panel open and the tab switch with my hands off the mouse. It sounds like a gimmick until you see it work — it's the demo every assistant vendor has been promising for two years, actually running in something I installed today.

Caveat, because I'm not going to oversell it: this works on the OpenCode Zen models. Point it at Gemini Flash and it falls back to browser tools instead of clicking the native UI. So the free-model story and this feature line up on Zen specifically.

The part that nearly made me quit

Day one, fresh Windows machine, the UI Control feature crashed with a cryptic Bun runtime error. No explanation. The installer never told me it needed Node.js.

I lost an hour to this, so here's the fix so you don't:

1. Install Node.js from nodejs.org.


2. Close OpenWork through Task Manager, not the X button — there's no tray icon and the normal close leaves the process alive, so the next launch reuses the broken state.


3. Relaunch. It works.

That's the kind of thing that makes people uninstall and write a bad review. It's a five-minute fix once you know it, and it's documented nowhere.

Would I tell you to switch?

If you need deep terminal control, Claude Code and Cowork still earn their place. But if you want the no-terminal, get-things-done workflow without a subscription and without being married to one model provider — OpenWork covers it, and it covers it well.

The thing I keep thinking about isn't OpenWork specifically. It's that open-source dev tooling is catching the paid tier on workflow now, not just undercutting on price. That gap closing from the open-source side is the real story.

Tested on a fresh Windows 11 install. Not sponsored. There's one task where OpenWork still loses to paid Claude — saving that for the next one.