icon of OpenWorker

OpenWorker

Open-source desktop coworker that turns a requested outcome into a finished deliverable across your files, apps, and everyday tools.

Community:

Product Overview

What is OpenWorker?

OpenWorker preview

OpenWorker is an open-source desktop agent created by Andrew Ng's team that aims to replace back-and-forth chat with completed work. Instead of prompting for an answer, users state an outcome — a renewal brief, an incident report, a rescheduled calendar, a triaged inbox — and OpenWorker breaks it into steps, pulls context from connected apps and local files, and hands back a document, message, or update ready to use. It runs locally on the user's own machine and is model-agnostic: bring your own API key for OpenAI, Anthropic, Google, or open-weight providers, or run entirely offline through Ollama. Every consequential action, such as sending a message or executing a command, pauses for explicit approval before it happens.


Key Features

  • Outcome-First Task Handling

    Users describe a desired result rather than a single instruction; OpenWorker plans and executes the multi-step work needed to produce it.

  • Model-Agnostic Engine

    Connects to OpenAI, Anthropic, Google Gemini, GLM, DeepSeek, Kimi, Qwen, MiniMax, Mistral, and Grok via your own keys, or runs fully offline through Ollama, with the option to switch models mid-task.

  • 25+ Native Integrations

    Works directly with Slack, Gmail, Outlook, Google Calendar, Notion, HubSpot, GitHub, Jira, Linear, Asana, Dropbox, Box, and more, plus local files, terminal access, and any MCP-compatible tool.

  • Approval-Gated Actions

    Sends, writes, and shell commands pause for user sign-off before execution; unattended runs collect pending requests in an inbox instead of acting alone.

  • Scheduled Automations

    Recurring jobs such as morning briefings, weekly reports, or standing channel monitoring run on a set schedule and leave a full transcript in the app.

  • Local-First Privacy

    Conversations, connector tokens, and model keys stay in a local secret store on the user's device; only OAuth handshakes touch an optional cloud broker.


Use Cases

  • Sales Meeting Prep : Pulls account history from CRM, email, and calendar tools to draft renewal briefs and follow-up messages in the rep's own voice.
  • Executive Assistant Work : Manages calendars, triages inbound email, and rebuilds a disrupted schedule while flagging changes for approval.
  • Incident and Ops Triage : Investigates alerts across Slack, GitHub, and runbooks, then drafts an incident timeline and proposed rollback path.
  • Marketing Performance Reporting : Compiles spend and attribution data from HubSpot and analytics tools into a recurring status report.
  • Sprint and Roadmap Planning : Synthesizes customer feedback across tools into prioritized themes for engineering standups.

FAQs

OpenWorker Alternatives

🚀

Analytics of OpenWorker Website