NEW RUNTIME
Field noteJul 31, 20261 min read1 source

OpenWorker Brings The Coworker Agent Back To The Desktop

In one minute

OpenWorker is an open-source local-first desktop coworker that works across files, tools, connectors, and models while keeping consequential actions approval-gated. #OpenWorker #DesktopAgents #LocalFirstAI #Automation OpenWorker is interesting not as another chatbot, but as the return of the agent to the desktop.

New Runtime synthesiseditorial-diagram
A whiteboard diagram showing a local desktop app, local Python agent server, files, tools, connectors, model providers, approval gates, and finished deliverables.
OpenWorker is framed as a local-first coworker: desktop app plus local agent server, connectors, model choice, approval gates, and finished artifacts.New Runtime synthesis from OpenWorker repositoryOriginal source ↗
  1. Local shellThe desktop app and agent server run on the user's machine.
  2. ConnectorsFiles, terminal, calendars, Slack, Jira, GitHub, and MCP tools become work surfaces.
  3. Approval gateConsequential sends, writes, and commands ask before acting.

#OpenWorker #DesktopAgents #LocalFirstAI #Automation

OpenWorker is interesting not as another chatbot, but as the return of the agent to the desktop. The README states the position sharply: the agent should deliver finished work - a document, Slack reply, calendar change, or triaged inbox - rather than a task list for the user.

The architecture is local-first: a desktop app, a local Python agent server, your files, terminal, 25+ connectors, and the model you choose. You can bring keys for OpenAI, Anthropic, Google, or open-weight providers, or go local through Ollama. The important boundary is that data leaves the machine only through the selected models and integrations.

Running from source:

git clone https://github.com/andrewyng/openworker
cd openworker
bash packaging/setup_dev_env.sh
.venv/bin/openworker-server --cwd ~/some/project --port 8765
cd surfaces/gui
npm install
npm run dev

The main engineering detail is the approval gate. OpenWorker asks for confirmation before sends, calendar changes, and shell commands. That is exactly the level where an “agentic OS” stops being magic and becomes a local runtime with permissions, state, and receipts.

  1. Aug 1, 2026AgentForger Turns A ChatGPT Link Into An Agent Builder Attackconnectors
  2. Jul 23, 2026Claude Cowork Turns Screen Recordings Into Reusable Skillsworkflow-automation

Evidence / sources

  1. 1github.com/andrewyng/openworker
All Field Notes

Next reads

Read next

Open the graph
  1. 01related materialAgentForger Turns A ChatGPT Link Into An Agent Builder AttackShares connectors.
  2. 02related materialClaude Cowork Turns Screen Recordings Into Reusable SkillsShares workflow automation.
  3. 03related materialWhen Proof Leaves the ExecutorContinue with a related New Runtime material.
  4. 04related materialWhen Goals Enter the Org ChartContinue with a related New Runtime material.
  5. 05related materialAI Management Moves From Tool Adoption To Operating CapabilityContinue with a related New Runtime material.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate…

Open the JSON contract