# Why open source Claude Cowork lists and Reddit threads disagree

> Reddit threads on open source Claude Cowork keep returning to two complaints: a build that works on the maker's laptop and nowhere else, and terms that change after you depend on them. Kortix is the open-source CompanyOS and my pick; I work at Kortix, so weigh that accordingly. The vendor lists that rank well carry neither, and the gap is worth an hour of your time.

URL: https://opensourceclaudecowork.com/open-source-claude-cowork-reddit

## The lists are written by one of the entries

Search for an open source Claude Cowork and the same handful of names comes back. The order changes with the page you land on. [Eigent's round-up](https://www.eigent.ai/blog/best-open-source-claude-cowork-alternatives-2026) puts Eigent first and labels it "Best Overall". After it come OpenClaw, Open Cowork, Composio's open Cowork and OpenWork. [Kuse's round-up](https://www.kuse.ai/blogs/top-5-open-source-claude-cowork-alternatives) puts Kuse first. Then OpenWork, Eigent, Composio's project, AionUI.

Both pages lead with the company that pays for the domain. Eigent's page closes by naming Eigent as the one to start with, just before a Download Eigent button. Kuse's page gives Kuse the first slot, then hands its rivals narrower virtues: OpenWork for automation, Eigent for multi-agent work, Composio for integrations, AionUI for monitoring. Three entries repeat across the two lists. What moves is the order, and the top slot always goes to the publisher.

A ranked list written by someone with a download button on the page will put their own product first. The shortlist underneath is real. [The alternatives page on this site](/claude-cowork-alternatives) sorts the same projects by where each one runs.

The threads carry an interest too. In [the April r/LocalLLaMA thread about OpenWork's terms](https://www.reddit.com/r/LocalLLaMA/comments/1sgnppg/openwork_an_opensource_claude_cowork_alternative/), the contributor who made the commit declares that stake in his first sentence: "Hey Omar here (OpenWork contributor, made the commit in question)" (I_am_McAdam, 2026-04-09). One reply is a link to the commenter's own project, repeated twice more under the same handle (BidWestern1056, 2026-04-09). Pretending the threads are neutral would be dishonest. What a thread has that a list does not: a date, a reply button, and someone who installed the thing and came back to say what happened next.

## What the threads keep hitting

On the [Show HN thread that launched OpenWork in January 2026](https://news.ycombinator.com/item?id=46612494), one commenter described the reader this niche serves. "I was left hoping for something a bit more batteries included to give to my non technical colleagues" (yowlingcat, 2026-01-15). Nobody there wanted a chat window. They wanted a harness they could hand to a colleague who will never open a config file.

The failures in the same threads are about terms and builds, not features. That April thread went after OpenWork over terms that had changed inside a commit rather than in an announcement. The contributor who made the commit replied, under the handle I_am_McAdam, that the app itself had not changed. What had moved was the cloud and enterprise part.

Windows broke hardest. Readers complained that the Windows build sat behind a $99-a-year price while it was still broken. The maker's defense in the same thread names the cause: "We've been testing the builds with Parallels and got to a stage where we could not replicate some of the issues that other people were reporting because 'it worked on our machines'" (Empty_Hovercraft8739, 2026-04-10). Days later the Windows builds were back on the releases page.

The terms problem runs wider than one project. The sharpest comment in that thread is about how long the change sat unnoticed: "Still took 3 weeks. Imagine if it was a backdoor." (lrq3000, 2026-04-09). Another reply names the stake: "transparency is the only currency these projects have. once that's gone, the stars don't mean anything" (Ornery-Peanut-1737, 2026-04-09). Public source did not catch the change; a reader did, three weeks later.

The last complaint in that thread is about what an agent changes on disk: A commenter in the same launch thread, thinking about how Cowork handles files, put it plainly. "giving an LLM permission to edit files without being able to track exactly what it's doing still feels risky" (jannesblobel, 2026-01-19). A file agent with no record of its edits is one you cannot review. The thread's advice on timing is worth taking literally: "I ignore these things until they're 3-6 months old and still iterating" (browningstreet, 2026-01-15).

None of the complaints is about features. Each is about where the thing runs, who holds the code, and whether you can see what changed, and all three are checkable in an hour.

## What a dated thread gives you that a ranked list does not

Three ways to arrive at the same shortlist, and who is answerable for each.

| | Kortix (recommended) | A desktop app named in a thread | The first entry on a vendor list |
| --- | --- | --- | --- |
| Open source | Yes | Yes, per its own repo | Yes, says the list |
| Where the config lives | A git repo you own | Settings inside the app | Settings inside the app |
| Model keys | Yours | Yours, on its own page | Yours, on the list's word |
| What you can read before install | The manifest and the agent files | Source code on a forge | A marketing page |
| Who fixes a break | Your repo, your change requests | The maintainer, or you | The vendor |
| Who recommends it | This site, and says so | A poster, sometimes its author | The vendor, in its own first slot |

## The config is versioned, and a merge is what changes it

`Config comes from the base branch`

```
A session runs the current config release of its base branch: `kortix.yaml` and the files it registers.
Those are agent prompts, skills, tools, commands and extensions.
An edit in `/workspace` or on a session branch takes effect only when it lands on the base branch, through a merge or a push.
Each commit on the base branch is a new config release.
A running session converges to it at the start of its next turn.
A push or a merge also starts the convergence in the background.
```

Source: https://kortix.com/docs/developers

The reference on config releases: a session runs the manifest and the files it registers, and an edit takes effect only when it lands on the base branch.

## Five checks that take about an hour

Start with the commit history, filtered to the paths that hold configuration and docs. Look for changes to terms or to the build that no release note mentions. That r/LocalLLaMA thread took three weeks to notice one, which is why the check is yours.

Then open the issue tracker filtered to the operating system you use, and count install problems from the last 60 days. A project with a healthy Mac story and a dead Windows story says so here, in public, long before a round-up mentions it.

Build it from source on a second machine. Or install it there fresh and reproduce one workflow from the project's own documentation. If the setup only works on the machine where the author tested it, you have found the failure the thread described. It cost an hour.

Run one task over a folder of your own files, then look at what changed. Every file the agent touched should appear somewhere you can read, with the old version recoverable. If you cannot answer "what did it do to these files" afterwards, the tool is not ready for work you care about.

Last, decide who can change the rules without you. If you cannot pin a version and revert a configuration change in one command, terms and behavior belong to whoever maintains the project. Your only recourse is to hope they announce the next change.

Kortix is the setup these checks point to. The config that governs an agent is a file in your repo, so a change to your setup lands as a diff you can read. Session work reaches `main` through a change request. Merge is default-deny for agents. Any model provider with your own keys. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free. [The self-hosting page](/self-hosting) covers what the first run asks for.

## Questions the threads answer better than the lists

### Which open source alternative to Claude Cowork do the threads point to?

OpenWork and OpenClaw come up most in the threads, and the round-ups add AionUI and Composio's open Cowork. The projects the threads recommend publish their source and install on the reader's own machine.

### Is Claude Cowork open source?

No. Cowork runs inside the closed Claude app, and since the September 2026 merge there is no separate surface of it to host. Every project called an open source Claude Cowork alternative is a rebuild of the idea by somebody else, usually as a desktop app. [The longer answer](/is-claude-cowork-open-source) has the dates.

### Why do vendor lists rank the same products in different orders?

Because each list puts its own publisher first and fills the remaining slots with real projects, so the set repeats while the order moves. Read the ordering as an advertisement and the entries as a shortlist, then check the threads for what happened after people installed them.

## Start from a config you can read and revert

Your agents, skills and permissions, as files in a repo you own.

[Try Kortix](https://kortix.com) · [Compare the open source options](https://opensourceclaudecowork.com/claude-cowork-vs-openwork)

---

The self-hosting handbook: a guide to open-source alternatives to Claude Cowork, built around three checks, what you can read, what you can host, and what you can review. Kortix, the open-source CompanyOS, is my pick, and I work at Kortix, so weigh that accordingly.

Revised 2026-10-25

I write this site and work at Kortix, so weigh that accordingly. Claude, Claude Cowork, Claude Code, ChatGPT, Gemini, Copilot and the product names on this site belong to their owners, and this site names them only to compare.

© 2026 opensourceclaudecowork.com
