How does OpenWork work with OpenCode?

OpenWork runs on OpenCode, the open-source coding agent. The desktop app gives anyone a point-and-click OpenCode, and the opencode-openwork plugin brings your organization's models, skills, and connections into OpenCode in a terminal.

Updated

  • Engine: OpenCode, on macOS, Windows, and Linux
  • Plugin: opencode-openwork, for OpenCode 2
  • Refreshes models and connections every 5 minutes
  • License: open source, free desktop app

OpenWork is built on OpenCode

Every OpenWork chat runs on the OpenCode engine. OpenWork adds a desktop app for people who don't use a terminal, plus team features: shared skills, shared connections, models from your company, and admin controls.

Anything OpenCode can do already works in OpenWork, even before it has its own button. Skills, MCP servers, providers, and opencode.json config files work the same way in both.

  • Same engine: OpenWork runs OpenCode under the hood on macOS, Windows, and Linux.
  • Same files: SKILL.md skills, MCP servers, and opencode.json or opencode.jsonc config work in both.
  • Same models: any of the 50+ providers OpenCode supports, including local models.
  • Shared access: the plugin exposes only the organization models and connections granted to the signed-in member.

The OpenWork plugin for OpenCode

Engineers who prefer the terminal don't need the desktop app. The opencode-openwork plugin connects a normal OpenCode 2 install to your OpenWork organization. You sign in once, and OpenCode loads your organization's setup each time it starts.

  1. Install the plugin

    Add the plugin to OpenCode 2.

    opencode plugin add opencode-openwork
  2. Sign in

    Choose Browser, sign in to OpenWork, and pick your organization. On a machine without a browser, add --method code and confirm the code on any device.

    opencode auth login openwork
  3. Check what you got

    Your company's AI Gateway models are listed with ipr_ names. The openwork-cloud MCP server gives the agent your organization's skills, plugins, and connections.

    opencode models | grep ipr_
    opencode mcp list

What the plugin adds to OpenCode

Self-hosting OpenWork? Set apiBaseUrl in the plugin options to your own OpenWork API. To load only models or only MCP, set providers or mcp to false.

What the opencode-openwork plugin loads into OpenCode
WhatWhat it means
AI Gateway modelsThe models your admin gave you, through your company's gateway. Provider keys stay on the server.
openwork-cloud MCPYour organization's skills, plugins, saved workflows, and connections, found with search_capabilities.
Direct connectionsTools your admin shared, such as Slack or Google Workspace, listed as openwork-direct-<name>.
Automatic refreshNew models and connections appear within minutes, with no restart.
Clean sign-outopencode auth logout openwork removes everything the plugin added.

OpenWork app or OpenCode with the plugin?

Choosing between the OpenWork app and OpenCode with the plugin
OpenWork desktop appOpenCode + opencode-openwork
Best forBusiness teams and anyone who prefers a windowEngineers who live in the terminal
EngineOpenCodeOpenCode
Company models and connectionsYesYes
Skills shared by your teamYes, installed in one clickYes, through openwork-cloud MCP
Browser automation, scheduled tasks, file previewsYesUse OpenCode's own tools
Sign-inJoining a team? Sign inopencode auth login openwork

Next steps

Frequently asked questions

Is OpenWork a fork of OpenCode?
No. OpenWork runs the OpenCode engine and adds a desktop app, team sharing, and admin controls. OpenCode features work in OpenWork as they are.
Do I need the OpenWork app to use the OpenCode plugin?
No. The opencode-openwork plugin works in plain OpenCode 2. Install it, sign in once, and OpenCode loads your organization's models and MCP connections.
Which OpenCode version does the plugin need?
OpenCode 2. OpenCode 1 is not supported by the plugin; use the OpenWork MCP URL instead.
Does the plugin work with self-hosted OpenWork?
Yes. Set apiBaseUrl in the plugin options in ~/.config/opencode/opencode.json to your OpenWork API address.
Are my existing OpenCode skills and config used by OpenWork?
Yes. OpenWork reads the same SKILL.md skills, MCP servers, and opencode.json files, so you can open an existing folder and keep working.

One engine for the whole company.

Engineers keep OpenCode. Everyone else gets the OpenWork app.

Free and open source. macOS, Windows, and Linux.