OlyWork

Install flow

Install CLI

Run `npm install -g @olywork/cli` once on your machine.

Get access

Open a listing and choose secure install. OlyWork creates an entitlement and access token.

Open Library

Library shows the exact command for each package you can install.

Run install

Run `oly install <token>` inside the project where files should be written.

Protected cloud use flow

Get entitlement

Open a protected cloud listing and choose remote access.

Save token

Run `oly auth <token>` or pass `--token` directly.

Run remotely

Run `oly run <capability>` to use the protected capability through OlyWork.

Command reference

bash

npm install -g @olywork/cli

Install the OlyWork CLI globally from npm.

bash

oly install <token>

Friendly one-command install. The token is validated against purchase, user, product, and status.

bash

oly sync --token <token>

Canonical sync command for scripts and advanced usage.

bash

oly update

Refresh packages using saved local configuration after `oly auth`.

bash

oly run <capability>

Use a protected cloud capability. Private prompts, workflow logic, and source stay on OlyWork.

bash

oly configure claude <capability>

Generate connector config for Claude, Cursor, Codex, OpenClaw, MCP, or HTTP clients.

bash

oly mcp <capability> --setup cursor --write

Generate and safely merge MCP bridge config for a supported client.

bash

oly list

Show locally tracked packages and versions.

bash

oly auth <token>

Persist a local default endpoint/token intentionally. Tokens are not saved by default.

bash

oly doctor

Check endpoint, token, Node.js version, local state, and writable config.

bash

oly logout

Remove saved local auth state.

Install targets

Skills and rules

Installs can write `SKILL.md`, `AGENTS.md`, `.cursorrules`, or agent-specific config files.

Workflows

Workflow packages can write JSON imports for n8n, LangGraph, Flowise, CrewAI, or OpenAI Agents SDK.

MCP config

Local MCP packages install config payloads. Protected MCP access should use `oly mcp <capability> --setup <client> --write` for client config and `oly mcp <capability>` as the entitlement-checked stdio bridge.

Protected cloud use

Secure install protects delivery. Protected cloud use protects private logic. Use it when buyers should get results from a capability without downloading the creator's prompts, orchestration, repo files, or secrets.

HTTP

POST to `/api/v1/runtime/run` with a bearer access token, capability slug, and client name.

MCP

Connect MCP clients to `/api/mcp/runtime/[capability]` and pass the OlyWork access token as bearer auth.

CLI

`oly run` uses the same entitlement path and returns safe output without downloading private package source.

Runtime isolation

Production Cloud Run should use `HOSTED_RUNTIME_ENGINE=e2b` with `E2B_API_KEY` configured. Docker mode is reserved for a separate Docker-capable runtime worker.

Connector config

bash

oly mcp <capability> --setup cursor --write

Preferred MCP onboarding path. Writes client config, rollback backups, and a `.oly/connectors/<capability>/<client>-setup.md` checklist.

bash

oly configure cursor <capability> --write

Writes `.cursor/mcp.json` for the current project.

bash

oly configure windsurf <capability> --write

Writes `.windsurf/mcp_config.json` for the current project.

bash

oly configure codex <capability> --write

Writes a Codex plugin manifest that points to OlyWork runtime APIs.

bash

oly configure openclaw <capability> --write

Writes an OpenClaw HTTP tool connector.

bash

oly configure http <capability> --json

Returns the raw HTTP runtime connector contract.