OpenWorker: Andrew Ng's open-source "AI coworker" passes 10k stars in 9 days on the strength of his name

OpenWorker is an open-source desktop AI coworker. You install it on your Mac or Windows PC, use your own model key, complete work in your files and office apps, and deliver output you can use directly. It was released in Jul 23, passed 10k stars in 9 days, and by Nov 6 18,906 had 2,690 forks and stars in total. Below is what it is, how the stars came about, who it competes with, and what you can and can't learn from it if you want to build a project that gets similar stars.

One tweet: "We want an open option"

On Jul 23 2026, at 16:45 PM UTC, Andrew Ng posted on X:

Announcing OpenWorker! An open-source agent that doesn't just chat with you, but delivers finished work -- like hand you a polished document, send a slack message, or update a calendar entry.

The second half states the stance: it isn't tied to any one model provider. GPT, Claude, Gemini, Kimi, GLM, and DeepSeek all work, and you can run everything locally with Ollama. "@rohitcprasad and I built OpenWorker because AI coworkers are an important way to get work done, and we want an open, privacy-respecting option that isn't tied to a specific model."

When the tweet went out, Andrew Ng had about 1.88M followers on X. MarkTechPost published "Andrew Ng Just Released OpenWorker" the same day, Enterprise DNA followed the next day, and Medium, a Japanese note.com post, Reddit's r/LocalLLaMA and r/AIDeveloperNews, and YouTube breakdown videos came out one after another, with headlines almost all of the form "Andrew Ng released...". Around Jul 27 it hit #1 on GitHub's daily trending list (someone on LinkedIn posted a screenshot), and by Jul 29 it had 10,347 stars.

What it actually does

In one line: an open, model-neutral version of Claude Cowork.

• It delivers finished output, not chat. Say "prepare a client briefing", "sort out my calendar", or "check how far this release has progressed in Jira and GitHub", and it breaks the task into steps, works across your files and apps, and hands back a document, spreadsheet, web page, or a Slack reply.
• Connects to 25+ office tools. GitHub, Slack, Jira, Notion, Linear, HubSpot, Gmail, Google Calendar, and more. Any MCP tool can also be connected. Mention @OpenWorker in Slack, or open a session on the desktop, and results return to the original thread.
• Pick any model. The README lists more than twenty model vendors and aggregation platforms, plus local options such as Ollama, llama.cpp, vLLM, and LM Studio. You can also log in with an OpenRouter account or a ChatGPT subscription.
• Asks before acting. It requires your approval before sending messages, changing your calendar, or running commands. A set of dangerous operations can only be triggered by a human. Every tool call is logged for audit. Commands can run inside an NVIDIA OpenShell container sandbox, and on Mac it uses the built-in system sandbox.

Technically, it's a desktop shell plus a local Python agent service, built on Andrew Ng's other open-source project aisuite (16k stars).

The Aug 25 release shifted the focus: "early users found it especially well suited to cybersecurity," so it added three ready-made "security coworkers" for code vulnerability scanning, dependency supply-chain checks, and cloud configuration auditing. That post drew 274k views, 3,564 likes, and 3,142 bookmarks (X, 11-06). The README's first paragraph now reads "the first security expert coworkers are now available."

Where the stars came from

(GitHub stars; there are no daily counts before 10-09, and the rows in between only show events, not star counts.)

First, Andrew Ng himself. He is the main engine, full stop. He is one of the biggest names in AI education (Coursera, DeepLearning.AI), and his GitHub repos together have 55k stars. One post pushed the repo onto the trending page on day one, and trending brought a second wave of exposure.

Second, media and creators came to it on their own. No pitching needed. "What Andrew Ng just released" was news in itself.

Third, "Claude Cowork alternatives" listicles. Composio's "Best Claude Cowork Alternatives" says: if you want privacy and model freedom, try OpenWorker or OpenWork. Much of the long-tail traffic probably comes from comparison posts like this (inferred).

What didn't take off: The repo was submitted to Hacker News 3 times, peaking at 5 points. The only comment asked: "How is it different from literally any other wrapper?" August's security pivot and September's NVIDIA tie-in did not bring a clear second wave of stars.

Who it's competing with

This slot is very crowded, and OpenWorker arrived late.

The most telling case is OpenWork: no big name, it did the same thing half a year earlier and reached 24k stars. That shows the "open-source Cowork" category alone can reach tens of thousands of stars. Andrew Ng's name let a latecomer reach the same range half a year later.

What it still gets wrong

• Differentiation came after the traction. At launch the selling points were "open, private, model-neutral," and OpenWork and others already had those. The approval ladder, audit, sandbox, and security coworker were added after August. So far there's no evidence those additions brought in many more users.
• The community couldn't keep up. At the end of July someone counted: 159 open PRs, only 8 merged. There are still 202 open issues and PRs (GitHub, 11-06).
• The Windows build is still unsigned. The README says SmartScreen will warn users and that signing is "in progress."
• How many people actually use it is unknown. The website publishes no download or active-user numbers. 19k stars doesn't mean 19k people are using it.

If it were you

Bottom line: Don't build "yet another open-source Cowork." Its stars came from Andrew Ng's name, which you won't get. The category already has OpenWork, eigent, goose, and other projects with over ten thousand stars, and without a famous name a latecomer will likely stall at a few hundred. What's worth learning is the formula, and the part it didn't finish.

Who it suits: developers who already work in a specific industry (security, ops, sales, finance, legal) and can clearly define what finished product an agent should hand over. Or people who already have tens of thousands of followers on X or GitHub and want to launch a flagship project.

Who it doesn't suit: people hoping to ride the "open-source Claude Cowork" title without a large audience, and people trying to build a general desktop agent that competes feature-for-feature with the dozen-plus existing projects.

How to do it:

1. Use the formula, but pick a category nobody has built yet. "A paid feature a big company just launched + open source, local, model-neutral" is the most reliable way to get stars on GitHub. Watch for agent features big companies release as subscriptions, and build the open-source version in the first few weeks after they launch. OpenWork got 24k stars that way: it shipped first and didn't rely on a name.
2. Build a vertical "expert colleague," not a general assistant. OpenWorker only moved into security coworker after users started using it for security work. It took just the first step: one specific role, a fixed toolset, and a fixed deliverable format (for example, "a weekly cloud billing anomaly report for small companies" or "automatic triage of issues and PRs for open-source maintainers"). A role done well is easier to remember than a hundred connectors (inferred).
3. Fill the gap it didn't close. Build an "approval and audit layer" that plugs into hosts like OpenWorker, OpenWork, and goose, or a security scanning plugin for these desktop agents. The more hosts you support, the more readers you reach.

How to get stars: Tie the launch tweet to a feature a big company just released, and state in one line "the open-source version of it / the part it can't do." Pair it with a screen recording of the agent finishing a real task, not a feature list. In launch week, go to r/LocalLLaMA on Reddit and to the authors of "X alternatives" comparison posts. "Local, not tied to a model" is what this crowd buys into most. Respond to PRs and issues. OpenWorker was shamed on LinkedIn for "159 PRs, only 8 merged," and that hurts a nameless project far more.

When it's too late: The "open-source Cowork" slot is already closed. The strategy of open-sourcing a big company's paid agent feature still works, but each new feature's window is usually only a few weeks after launch, and whoever ships first gets the stars.

Signs you picked wrong: Searching GitHub for your category already turns up open-source alternatives with thousands of stars. Or your launch tweet, with a recording, hasn't passed ten thousand views in a week and the repo is stuck in double-digit stars. Either the category isn't hot enough, or your version isn't clearly better than what exists. Switch directions.