Open Source Apache 2.0 v0.14.2

Turn Desktop AI Work
into Reusable Workflows

OpenCowork is a local-first desktop AI Agent Runtime for teams that need real execution, not another chatbot. It operates browsers and local tools, connects MCP and skills, records auditable task runs, and turns successful sessions into reusable templates.

Latest: v0.14.2 Save completed session work as workflow templates, rerun templates with cleaner UI, uninstall skills safely, and keep long results contained in reviewable surfaces.
Agent Runtime One lifecycle for Electron, Scheduler, IM, MCP, and future clients
MCP Native Connect external tools and expose OpenCowork capabilities
Session Templates Save completed session work as reusable workflow templates

Built for Work That Must Finish

OpenCowork focuses on repeatable business outcomes: local execution, observable runs, and workflow reuse across browser-heavy and tool-connected tasks.

02

Works beyond chat

Execute browser actions, CLI steps, MCP tools, skills, IM file workflows, and scheduled jobs through one approval-aware task lifecycle.

03

Turns success into a system

Review the result, artifacts, screenshots, traces, and diffs, then save successful runs or whole sessions as templates that can be rerun and scheduled.

Built to Turn Execution into Reuse

OpenCowork is designed for builders, researchers, product teams, and early enterprise pilots that want local execution, browser-first automation, MCP interoperability, workflow templates, and auditable task infrastructure in one open-source system.

๐Ÿ–ฅ๏ธ

From Chat to Local Execution

Run multi-step work on a desktop agent that can operate websites, call local tools, use installed skills, and produce files or structured outputs.

๐Ÿงพ

From Execution to Result Record

Persist task state, results, screenshots, artifacts, run links, runtime traces, and reusable context so useful work remains inspectable after the live run ends.

โฑ๏ธ

From Successful Run to Reuse

Save proven runs or completed session workflows as templates, trigger them from chat, scheduler, IM, or MCP-oriented flows, and repeat work without rebuilding the process.

High-Value Workflows Ready for Local AI

OpenCowork is strongest where a team repeatedly opens websites, processes files, connects internal tools, and needs a result that can be audited or reused.

Research

Market and Sales Research

Collect public information, compare competitors, monitor pricing, and generate lead lists or research briefs.

Output: brief, spreadsheet, PPT outline
Operations

File and Screenshot Processing

Receive files through IM, run OCR or image analysis, apply repeatable rules, and return generated result files.

Output: cleaned file, OCR result, report
Back Office

Browser Console Workflows

Operate non-standard dashboards, forms, approval consoles, and long-tail browser workflows with human oversight.

Output: completed operation, audit trace
Platform

MCP-Connected Internal Tools

Connect local scripts, internal services, MCP servers, and skills into reusable private workflow packages.

Output: template, run record, artifacts

Everything You Need for Real Desktop AI Work

OpenCowork combines browser execution, Hybrid CUA, desktop workflows, MCP tools, reusable templates, session management, IM intake, skills, and human oversight so one system can finish work and make it repeatable.

Browser-First Automation

Navigate, click, type, wait, search, and extract in a headed browser for workflows that need real interaction instead of simulated demos.

Hybrid CUA and Visual Recovery

Use DOM-first browser automation with visual execution fallback, approval-aware recovery, takeover paths, and persisted visual traces.

Result-First Runs and Traces

Preserve final summaries, structured data, generated files, screenshots, artifact links, runtime trace status, run details, and follow-up actions in a reviewable result surface.

Templates, Scheduler, and IM

Convert successful runs or active sessions into templates, schedule recurring work, and receive or deliver file-driven tasks through Feishu messaging workflows.

Skills and Local Outputs

Install, update, uninstall, and run reusable capability modules, call local commands, handle files, and generate assets that remain useful outside the chat session.

MCP Client and Server

Connect local stdio or remote streamable-http MCP servers, and expose selected OpenCowork capabilities through a standard MCP endpoint.

How OpenCowork Works

The product now includes the first shared local Agent Runtime baseline used by Electron, Scheduler, IM, MCP, and future clients through one task lifecycle.

๐ŸŒ
Browser + Desktop
๐Ÿ—‚๏ธ
Hybrid CUA
๐Ÿงฉ
MCP Tools
๐Ÿ“…
Templates + Runs
Step 1
Submit work from chat, session, IM, scheduler, or MCP Provide a concrete goal, files, target sites, desired output, and approval boundaries.
โ†“
Step 2
Run through the local Agent Runtime Coordinate browser, desktop, visual, CLI, MCP, skill, workspace rules, and approval-aware execution.
โ†“
Step 3
Review result, artifacts, and trace Inspect summaries, structured outputs, files, screenshots, trace artifacts, diffs, and run metadata.
โ†“
Step 4
Rerun Use stored task context
Template Save successful runs or sessions
Extend Skills and MCP

Run Your First Workflow in Minutes

Install Node.js, npm, Python, Playwright Chromium, configure your model locally, and launch the desktop app.

Terminal
# Install requirements
# macOS
brew install node python

# Ubuntu / Debian
sudo apt update
sudo apt install -y nodejs npm python3 python3-pip

# Windows PowerShell
winget install OpenJS.NodeJS.LTS
winget install Python.Python.3.12

# Verify requirements
node -v
npm -v
python3 --version

# Clone the repository
git clone https://github.com/LeonGaoHaining/opencowork.git
cd opencowork

# Install dependencies
npm install
npx playwright install chromium

# Configure your model
# Create config/llm.json
# Keep config/ local and never commit credentials

# Start the desktop app
npm run electron:dev

Treat OpenCowork as Trusted Automation

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 it can perform real actions in a local desktop environment, use it as a trusted automation tool with operating privileges, not as a sandboxed chatbot.

To reduce accidental operations, credential exposure, and data leakage, run OpenCowork on a dedicated AI automation device, virtual machine, or isolated system account whenever possible.

01

Use trusted machines, networks, and operating system accounts.

02

Review agent actions before allowing access to sensitive websites, files, credentials, or production environments.

03

Keep `config/llm.json`, `config/feishu.json`, API keys, tokens, cookies, databases, and private artifacts local.

04

Verify scheduled tasks and reusable templates before running them unattended.

05

Report sensitive findings through GitHub Security Advisories instead of public issues.

Built in the Open for Builders

OpenCowork is an Apache 2.0 open-source desktop AI work system with public releases, refreshed docs, issue templates, contributor guidance, and an active local Agent Runtime for real automation instead of demo-only agent experiences.

Stars Forks Issues License
๐Ÿง 
๐ŸŒ
๐Ÿ‘๏ธ
๐Ÿงฉ
๐Ÿ”Œ
๐Ÿ”“