Opencowork

Why OpenCowork

OpenCowork is for teams that want an AI agent to do real work on a local desktop, not only answer chat messages. It combines a headed browser, local execution, reusable skills, MCP integrations, task history, templates, scheduling, IM file workflows, and human-in-the-loop approval into one desktop-native agent system.

The core product idea is simple: describe a business outcome, let the agent operate local tools and websites, review the result, then turn the successful run into a reusable workflow. OpenCowork is not positioned as a generic chatbot or a traditional RPA recorder. It is a local AI automation layer for repeatable knowledge work where execution, traceability, privacy, and result reuse matter.

The product direction is result-first:

• finish useful tasks, not just stream reasoning,
• preserve task runs as inspectable records,
• turn successful runs into reusable templates,
• connect local desktop execution with IM, Scheduler, Skills, and MCP,
• make browser and desktop automation observable, recoverable, and repeatable.

Product Positioning

OpenCowork is currently best suited for builders, researchers, product teams, and early enterprise design partners who need local execution, BYO model configuration, browser automation, and private workflow delivery.

The strongest early fit is not low-price self-serve SaaS. It is high-value, scenario-driven automation where a team wants a local AI worker that can be deployed privately, connected to internal tools, and supported through repeatable workflow packages.

Good fit:

• technical or semi-technical teams evaluating local AI automation,
• privacy-sensitive teams that prefer local execution and BYO model keys,
• operations, research, sales, and consulting teams with repeated browser-heavy work,
• product and agent teams building on MCP, Hybrid CUA, task traces, and reusable runtime APIs,
• enterprise pilots that need private deployment, scenario delivery, templates, and annual support.

Not the current focus:

• a fully hosted multi-tenant SaaS platform,
• a generic personal chatbot,
• a no-code RPA replacement for every enterprise process,
• a production claims package with published commercial pricing.

Typical Scenarios

What You Can Build

OpenCowork is a practical foundation for:

• local AI automation pilots for research, operations, sales, and consulting teams,
• scenario-specific workflow packages that turn successful task runs into templates,
• private deployment and annual support offerings for teams that need local execution,
• MCP-native local agent workflows that connect internal tools and external services,
• Feishu-driven task intake, file analysis, progress updates, and result delivery,
• desktop computer-use experiments with approval, trace, and benchmark loops,
• open-source agent runtime research around protocol, trace, and multi-client reuse.

Current Release: v0.14.6

v0.14.6 is a stability-focused open-source release for teams evaluating OpenCowork as a local desktop AI Agent Runtime. It tightens long-running task behavior, process cleanup, MCP stdio lifecycle handling, visual automation cleanup, and renderer task-state isolation.

Highlights:

• stops unrecoverable task failures from continuing into later nodes and overwriting failed state,
• kills CLI child processes when action-level timeouts are reached,
• preserves history writes that arrive while SQLite flush is already in progress,
• cleans MCP stdio pending requests and processes on timeout, disconnect, or connection failure,
• ensures visual adapter sessions are destroyed even when computer cleanup fails,
• filters renderer task events by the active run or handle to avoid stale event updates.

Recent product milestones:

• v0.14.6: runtime stability, cleanup coverage, MCP stdio lifecycle hardening, and task UI event isolation.
• v0.14.5: i18n coverage and release polish.
• v0.14.4: Feishu follow-up context and browser visual/computer-use reliability.
• v0.14.2: session template save, template-run UI hardening, result overflow fixes, and immediate new-session switching.

Core Capabilities

Commercial Direction

OpenCowork remains an open-source project. The commercial direction is to use open-source distribution for adoption while productizing high-value local AI automation services around the runtime.

Current recommended commercialization path:

• design partner pilots around a small number of standard scenarios,
• scenario-based workflow delivery for market research, operations file processing, and MCP-connected internal tools,
• private deployment guidance and annual support for teams that need local-first AI automation,
• reusable industry template packs and workflow packs created from proven customer runs,
• training, implementation partners, and a lightweight team edition after installability, support, and template reuse are stronger.

This direction avoids premature dependence on a heavy multi-tenant cloud platform. It prioritizes high-ARPU design partners, repeatable templates, local deployment trust, and measurable business outputs before broader self-serve subscriptions.

Architecture Direction

OpenCowork is moving from a single Electron app with many entry points toward a reusable local Agent Runtime.

Electron UI / Scheduler / IM / MCP / Future CLI
  -> Agent Runtime API
  -> Shared Protocol Layer
  -> Runtime Services: lifecycle, approval, trace, config, rules, state
  -> Execution Adapters: browser, desktop, visual, CLI, MCP, skill
  -> Result, history, template, benchmark, and artifact surfaces

Security Notice

OpenCowork is a local-first desktop AI agent runtime. It can operate a headed browser, call local tools, connect to MCP servers, process files, run scheduled workflows, and integrate with IM systems such as Feishu. Because the agent can perform real actions in a local desktop environment, users should treat it as a trusted automation tool with operating privileges, not as a sandboxed chatbot.

To reduce the risk of accidental operations, credential exposure, and data leakage, we recommend running OpenCowork on a dedicated AI automation device, virtual machine, or isolated system account. Avoid mixing it with personal daily-use environments, production administrator accounts, or high-sensitivity data workspaces.

Recommended usage:

• Run OpenCowork on a dedicated AI device, virtual machine, or isolated system account whenever possible.
• Use OpenCowork only on machines, networks, and operating system accounts you trust.
• Review agent actions before allowing access to sensitive websites, internal systems, credentials, private files, or production environments.
• Keep model and integration configuration local. Do not commit config/llm.json, config/feishu.json, API keys, tokens, cookies, generated databases, or private task artifacts.
• Use placeholder credentials in examples, documentation, issues, and pull requests.
• Be careful when connecting external MCP servers or installing third-party skills, because they may extend what the agent can access or execute.
• For scheduled tasks and reusable templates, verify the workflow behavior before running it unattended.
• Report sensitive security findings through GitHub Security Advisories instead of public issues.

OpenCowork is commonly used in trusted single-user desktop deployments. This reduces some multi-tenant web risks, but credential leakage, unsafe remote access, uncontrolled task execution, data loss, persistent crashes, and resource leaks remain important security concerns and should be reported responsibly.

See SECURITY.md for the vulnerability reporting policy.

Quick Start

Requirements

• Node.js 18+
• npm 9+
• Python 3.8+
• A valid LLM API configuration in config/llm.json

Install Prerequisites

macOS:

brew install node python
node -v
npm -v
python3 --version

Ubuntu / Debian:

sudo apt update
sudo apt install -y nodejs npm python3 python3-pip
node -v
npm -v
python3 --version

Windows:

winget install OpenJS.NodeJS.LTS
winget install Python.Python.3.12
node -v
npm -v
python --version

Install

git clone https://github.com/LeonGaoHaining/opencowork.git
cd opencowork
npm install
npx playwright install chromium

Configure Your Model

Create config/llm.json:

{
  "provider": "openai",
  "model": "gpt-5.4-mini",
  "apiKey": "your-api-key",
  "baseUrl": "https://api.openai.com/v1",
  "timeout": 60000,
  "maxRetries": 3
}

Keep config/ local. It is git-ignored and must not be committed.

Run the Desktop App

npm run electron:dev

Build and Test

npm run build
npm run test:run
npm run lint

Example Prompts

Open a company website, summarize what it does, and save a reusable research summary.
Search for competitor pricing changes and turn the result into a structured report.
Use a connected MCP server to fetch documentation examples and explain them.
Analyze this Feishu-uploaded image and send the result file back to the chat.
Turn the successful workflow into a template and schedule it weekly.

MCP Support

OpenCowork supports both sides of MCP:

• as an MCP client, it connects to local stdio servers and remote streamable-http endpoints,
• as an MCP server, it exposes selected OpenCowork capabilities through a standard /mcp endpoint.

Try connecting a remote MCP endpoint from the MCP panel, then ask the agent what tools are available.

Documentation

• USER_GUIDE.md — practical usage guide
• docs/ARCHITECTURE.md — architecture overview
• docs/ROADMAP.md — near-term and strategic roadmap
• docs/RELEASE_v0.14.6.md — current release notes
• CHANGELOG.md — release history
• CONTRIBUTING.md — contribution workflow
• SECURITY.md — vulnerability reporting policy

Open Source Status

OpenCowork is actively evolving. The current release line is best suited for builders, researchers, and product teams who want to evaluate or contribute to a local desktop agent stack with real browser automation, MCP interoperability, and reusable task infrastructure.

Good contribution areas:

• browser and desktop workflow reliability,
• MCP client/server interoperability,
• task trace and result UX,
• templates and workflow packs,
• skills and reusable capability packaging,
• release quality, tests, and docs.

Community

• Issues: https://github.com/LeonGaoHaining/opencowork/issues
• Discussions: https://github.com/LeonGaoHaining/opencowork/discussions
• Releases: https://github.com/LeonGaoHaining/opencowork/releases
• Website: https://opencowork.me

License

Apache-2.0. See LICENSE.