Set up OpenWork for a team, from creating an organization and inviting members to sharing AI models and skills. It covers dashboard setup and terminal setup, with human ownership of accounts and shared access to provider keys.
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.
Review the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.
Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.
Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.
Connects supported AI clients, including Claude Code and Codex, to OpenWork through MCP, a protocol for accessing external tools. It guides account sign-in and verifies that tools for finding and running organization capabilities are available.
Review an outside contributor’s pull request before running its code. Identify concealed behavior, obfuscated code, risky dependencies, and build hooks, with file locations and specific checks for maintainers to follow up.
Create an OpenCode plugin for OpenWork with custom tools and hooks, which run code at specific events. The skill builds the plugin file and adds its entry to the project configuration.