Set up OpenWork for a team - sign up for OpenWork Cloud, create the organization, invite teammates, share models through the AI Gateway, and share a skill. Use when a team or company wants OpenWork with shared skills, models, or policies.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
OpenWork Cloud is the team control plane: members, shared models (AI Gateway), shared skills and plugins, and the MCP Gateway. The first 5 seats are free; then $10 per seat per month. Pricing: https://openworklabs.com/pricing
The human creates the account. Don't invent passwords or create accounts for the user without asking.
Members > Add member, enter an email, pick a role (usually Member), Send invite. Group people under Teams > Create Team.AI Gateway > AI Providers > Add provider, pick a provider, paste the org key, and choose who can use it. Members never handle keys.Collections > New collection), then Plugin Directory > Create plugin > + Skill. Write a name, a "use when..." description, and markdown instructions. Share it to the Collection and grant the Collection to a team.Joining a team? Sign in. Shared skills appear under Settings > Library.Walkthrough with screenshots: https://openworklabs.com/docs/cloud/team-quickstart
When the user wants the agent to do the setup from a terminal, follow https://openworklabs.com/start.md. It installs the openwork-bootstrap CLI (needs Node.js 20+; it is not on npm) and creates a provisional workspace with a first skill. The human claims ownership later in the browser, so no password is created by the agent.
curl -fsSLo /tmp/openwork-install.sh https://openworklabs.com/install.sh
less /tmp/openwork-install.sh # inspect before running
sh /tmp/openwork-install.sh
openwork-bootstrap doctor --json
Then run openwork-bootstrap cloud bootstrap-workspace exactly as start.md describes. Teammate emails passed with --teammate-emails are invited once a human claims the workspace.
To keep building in that workspace before anyone claims it (adding skills and connections through the MCP gateway), or to sign the CLI in as an existing user without a password, follow https://openworklabs.com/auth.md.
Each member can connect their coding agent to the organization with the connect-openwork-mcp skill: https://openworklabs.com/.well-known/agent-skills/connect-openwork-mcp/SKILL.md
Send the user to https://openworklabs.com/enterprise.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new feature, put work behind a feature flag, roll something out (per organization, for everyone, cloud or self-hosted), revert or kill a feature, or make a big change to existing behavior such as a new engine. Use BEFORE writing the feature code, and when finishing or removing a rollout.
日本語の概要は準備中です。原文の説明を表示しています。
Local OpenWork Electron browser automation with CDP. Use when driving a local Electron dev app, browser_list, browser_snapshot, browser_eval, composer automation, or local UI smoke tests.
日本語の概要は準備中です。原文の説明を表示しています。
Flag customer, prospect, partner, or outside-person identities in the diff. Reported in the Warden security summary.
日本語の概要は準備中です。原文の説明を表示しています。
Connect the OpenWork MCP Gateway (https://api.openworklabs.com/mcp/agent) to Claude Code, Codex, Gemini CLI, Cursor, VS Code, Claude Desktop, or ChatGPT so the agent can use the user's OpenWork organization skills, plugins, and connections.
日本語の概要は準備中です。原文の説明を表示しています。
Screen a pull request from an outside contributor for hidden, obfuscated, or supply-chain-risky changes before any of its code runs.
日本語の概要は準備中です。原文の説明を表示しています。
Create an OpenCode plugin for OpenWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
日本語の概要は準備中です。原文の説明を表示しています。