different-ai / openwork

OpenWork OpenWork is a free, open-source desktop app made for sharing AI workflows. It is an open-source alternative to Claude Cowork and Codex for macOS, Windows, and Linux. Add one OpenWork MCP to Codex, Claude Code, Cursor, or another compatible agent and reuse the same skills, MCPs, and connected services across your tools, teammates, and machines. Create something once, share it with coworkers or friends, or keep it for yourself. The desktop app is there when you want a dedicated workspace, but it is not required. You can use OpenWork from the agent you already have. For larger organizations, the admin interface lets you publish capabilities, manage access, and configure shared or per-user connections.

OpenWork 是一款免费的开源桌面应用程序，旨在共享 AI 工作流。它是 macOS、Windows 和 Linux 上 Claude Cowork 和 Codex 的开源替代方案。只需将一个 OpenWork MCP 添加到 Codex、Claude Code、Cursor 或其他兼容的智能体中，即可在你的工具、团队成员和机器之间复用相同的技能、MCP 和连接的服务。你可以一次性创建内容，将其分享给同事或朋友，也可以仅供自己使用。桌面应用程序为你提供了一个专属的工作空间，但它并非必需品。你完全可以直接通过现有的智能体使用 OpenWork。对于大型组织，管理界面允许你发布功能、管理访问权限并配置共享或个人连接。

Download OpenWork Install with your AI agent. Already use an AI agent? Copy this prompt and paste it into Claude Code, Cursor, Codex, ChatGPT, or any agent that can run commands on your computer: “Install OpenWork on my computer, set up my first workspace, and open it ready to use.” Follow the steps in https://openworklabs.com/start.md?v=hero. Installs OpenWork, creates your workspace, and opens it ready to run.

下载 OpenWork 通过你的 AI 智能体进行安装。已经在用 AI 智能体了？复制以下提示词并粘贴到 Claude Code、Cursor、Codex、ChatGPT 或任何可以在你电脑上运行命令的智能体中：“Install OpenWork on my computer, set up my first workspace, and open it ready to use.” 按照 https://openworklabs.com/start.md?v=hero 中的步骤操作。它将安装 OpenWork，创建你的工作空间，并将其打开以供使用。

Use OpenWork from any agent The OpenWork MCP brings your assigned skills, plugins, MCP connections, Google Workspace, and Microsoft 365 capabilities into any compatible agent. It exposes two tools: search_capabilities finds what you can use, and execute_capability runs it. After adding the MCP, your client opens a browser so you can sign in and choose your OpenWork organization.

从任何智能体使用 OpenWork OpenWork MCP 将你分配的技能、插件、MCP 连接、Google Workspace 和 Microsoft 365 功能引入到任何兼容的智能体中。它提供了两个工具：search_capabilities 用于查找你可以使用的功能，execute_capability 用于运行该功能。添加 MCP 后，你的客户端会打开浏览器，以便你登录并选择你的 OpenWork 组织。

(Configuration snippets omitted for brevity)

OpenWork Den OpenWork Den is the control plane for managing OpenWork across a team or organization. Provision inference at scale and control which members and teams can use each model provider. Invite teammates, create teams, and manage access from one place. Set desktop policies, restrict local model access, and control which app versions your organization can use. Publish skills and plugins through marketplaces, then assign them to the organization, a team, or specific people. Import Anthropic-compatible plugins and make their supported skills and remote MCPs available through the OpenWork MCP.

OpenWork Den OpenWork Den 是用于在团队或组织内管理 OpenWork 的控制平面。它可以大规模配置推理资源，并控制哪些成员和团队可以使用特定的模型提供商。你可以在一个地方邀请队友、创建团队并管理访问权限。设置桌面策略、限制本地模型访问，并控制你的组织可以使用哪些应用程序版本。通过市场发布技能和插件，然后将其分配给组织、团队或特定人员。导入兼容 Anthropic 的插件，并通过 OpenWork MCP 使其支持的技能和远程 MCP 可用。

Documentation Read the OpenWork docs.

文档 阅读 OpenWork 文档。

Local development For one checkout, keep using pnpm dev; with no extra environment variables it reuses the existing shared dev profile. To run multiple git worktrees at once, use: pnpm dev:worktree. That sets OPENWORK_DEV_PROFILE=auto, derives a stable profile name from the worktree path, lets Electron choose a free CDP port, and asks Vite for a free dev-server port. You can also choose a named profile, for example OPENWORK_DEV_PROFILE=my-feature OPENWORK_ELECTRON_REMOTE_DEBUG_PORT=0 PORT=0 pnpm dev. dev:worktree also defaults OPENWORK_ELECTRON_USE_MOCK_KEYCHAIN=1. A brand-new profile has no stored credentials, so on macOS the real keychain prompts as soon as Chromium persists an authenticated cookie, and that modal blocks Electron’s main loop until it is dismissed. Set OPENWORK_ELECTRON_USE_MOCK_KEYCHAIN=0 if you specifically want the system keychain in an isolated profile. Dev startup prints a banner like [openwork] dev profile=... cdp=http://127.0.0.1:9223; use it to find the profile directory and pass the CDP URL to local tooling. If a second instance cannot get the profile lock it now says so and exits, instead of lingering with an open CDP port and no window.

本地开发 对于单个检出（checkout），请继续使用 pnpm dev；在没有额外环境变量的情况下，它会复用现有的共享开发配置文件。若要同时运行多个 git 工作树（worktrees），请使用：pnpm dev:worktree。这会设置 OPENWORK_DEV_PROFILE=auto，从工作树路径派生出一个稳定的配置文件名称，让 Electron 选择一个空闲的 CDP 端口，并要求 Vite 提供一个空闲的开发服务器端口。你也可以选择一个命名的配置文件，例如 OPENWORK_DEV_PROFILE=my-feature OPENWORK_ELECTRON_REMOTE_DEBUG_PORT=0 PORT=0 pnpm dev。dev:worktree 默认还会设置 OPENWORK_ELECTRON_USE_MOCK_KEYCHAIN=1。全新的配置文件没有存储凭据，因此在 macOS 上，一旦 Chromium 持久化了身份验证 Cookie，真实的钥匙串（keychain）就会弹出提示，该模态框会阻塞 Electron 的主循环直到被关闭。如果你特别希望在隔离的配置文件中使用系统钥匙串，请设置 OPENWORK_ELECTRON_USE_MOCK_KEYCHAIN=0。开发启动时会打印类似 [openwork] dev profile=... cdp=http://127.0.0.1:9223 的横幅；使用它来查找配置文件目录并将 CDP URL 传递给本地工具。如果第二个实例无法获取配置文件锁，它现在会提示并退出，而不是在没有窗口的情况下挂起并占用 CDP 端口。