What Reddit's Cowork threads ask for, and the open-source answer

The test these threads set

Someone who arrives from a Reddit thread about open-source Claude Cowork alternatives usually carries three demands: code they can read, an install that runs on their own machine or cloud account, and a model they pick rather than one the vendor routes to. Threads in r/claude and r/LocalLLaMA put it more bluntly still, and they come from people who have watched this category fill up with wrappers.

Most candidates fail the second demand. A desktop app whose agent calls a hosted API still sends the work outward, whatever its repository looks like. A project whose self-host option means a control plane the vendor operates has moved the dependency rather than dropped it. OpenWork, named in several of those threads, is plain about its shape: a desktop app for macOS, Windows and Linux that works on files in folders you authorize, with 50+ providers on keys you supply and a team control plane that runs on your own infrastructure.

The threads people post when Cowork stops fitting

People ask for a Cowork alternative in threads with no vendor behind them. In r/claude, Self hosted equivalent of cowork? comes from someone who runs Cowork as a live personal assistant and wants the same thing on hardware they hold, and the title carries the whole ask.

In r/claude, Any good alternatives to Claude Cowork? asks the plain version of the question, with no product named in the title. In r/ChatGPTCoding, Is there any real alternative to Claude Cowork + Computer Use? adds a demand the other threads leave out: computer use, an agent driving a desktop rather than only editing files.

Computer use is worth separating from the rest of that title. In Cowork it means Claude clicks, types and navigates the screen, and Anthropic's safety page draws the line: file operations go through permission checks and code execution runs in an isolated environment, while computer use has no sandbox between Claude and what is on your screen (Anthropic's safety page, checked November 2026). Of the projects these threads name, Eigent is the one whose own page says it can control the browser and desktop apps to automate real work (Eigent, checked November 2026). Agenta's browser is a panel in its workspace, and OpenWork and Kuse Cowork describe work on files. For a team, the demand lands on a machine per session rather than one person's screen, and the configuration that decides what runs there is in the repository.

Builders supply the other half. In r/ClaudeAI, I'm working on an open-source Claude Cowork alternative… names cost and a model-agnostic design as the motive. In r/LocalLLaMA, a member of the Agenta team introduces Agenta: an open-source Claude Cowork alternative where… as a self-hosted, more flexible alternative to Cowork, posted to the community that cares most about which model runs. In r/learnprogramming, I built an open-source, local-first alternative to Claude Cowork presents Kuse Cowork as a local-first workspace inspired by Cowork.

The pattern reaches past single threads. A catalog of open-source implementations lists five desktop projects built by unrelated developers, and a rival vendor keeps a top-five listicle of open-source alternatives on its blog (both checked October 2026). Neither site sells Kortix, and both exist because the question keeps coming up.

The three demands that repeat

Read the six threads together and the same three demands surface. Each names a different part of the system.

• Self-hosting. The r/claude thread asks for a self-hosted equivalent in its title. Agenta leads its introduction with self-hosted. Eigent's homepage says host it yourself, free, and Kuse Cowork calls itself local-first.
• Model choice. The r/ClaudeAI builder's stated motive is a model-agnostic design. The r/LocalLLaMA post lives in the subreddit it does for a reason: local-model people want alternatives that run the models they already host. OpenWork counts more than 50 providers; Kuse Cowork and Eigent both list local models.
• Data you hold. Local-first keeps files, settings and history on the machine in front of you, which is a data claim as much as a hosting one. Self-hosting is the same demand moved to the server.

All three come down to who holds a piece of the system: the hosting, the model, the files. A hosted product on somebody else's cloud can be excellent at the work and still miss all three.

What the thread-named projects are

The projects the threads trade back have a shape, and their own pages state it. Three of the four are desktop agents: software installed on one person's machine, working on that machine's files.

OpenWork is a desktop program for macOS, Windows and Linux, and its own repository names it the open-source alternative to Cowork. Agents work on the files of the machine it sits on, running on the OpenCode harness, with models from more than 50 providers on the keys you supply or a local model through Ollama. For teams there is a control plane for shared skills and policies that can be self-hosted at no cost for small teams. The desk is the product, and the team layer sits above it.

Kuse Cowork is a lightweight desktop agent written in Rust, and its feature page leads with local-first execution: bring-your-own-key models, connections to Anthropic, OpenAI and Gemini, and local models through Ollama. Like OpenWork, it lives on one machine.

Eigent calls itself an open-source cowork desktop that runs several agents as one coordinated workforce. You can run it on your machine or on infrastructure your team controls, connect your own API keys or local models, and pay $19.99 a month for its hosted plan after a trial (checked October 2026). The agents coordinate on one machine, with an optional server behind them.

Agenta is the exception. Its own pages describe an open-source workspace where a team builds persistent agents, each with its own instructions, files, skills, tools, permissions and schedule, sharing one workspace. Work happens in chat with a browser and a file panel beside it, and reviews come back through chat. The shape is closer to what a team needs than any desktop app in these threads.

For the person in the r/claude thread, a desktop agent is the right answer. The ask was one person's assistant on one machine, and a desktop app meets it. For one pair of projects in more detail, there is a Claude Cowork vs OpenWork comparison.

Where a team lands

A team's version of the three demands looks different. The memory is shared, so every agent reads what the last one learned. The configuration is one set of files the whole team can diff. Work passes a gate before it counts. The hosting outlives any laptop. A desktop app keeps all of that on one machine, and the shape that holds it at team scale is a system the company owns as files.

Kortix is built to that shape, and it is open source. Read it, fork it, audit it (Kortix on GitHub). Agent files, skill folders, shared memory and connector configuration sit in one git repository the whole team holds, which is the data demand answered at company scale.

The other two demands map the same way. Self-hosting is a supported path: run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free. Model choice is a setting: any model provider with your own keys. The desktop projects in the threads serve one machine well. When the team grows, the work needs a home that is shared, versioned and gated, and that home is a repo.