Skip to content
Weavz
Menu
Weavz CLI

Bring a governed agent workspace to any terminal.

Install the CLI, sign in with a browser code, inspect the active workspace, manage apps, run single actions, and execute Code Mode workflows from local shells, SSH sessions, containers, and agent runtimes. Local agents can use the same governed workspace with 1,000+ app integrations and 12,000+ agent tools.

1,000+ app integrations12,000+ agent toolsMCP + local shells
terminal
$ npm install -g @weavz-io/cli$ weavz login$ weavz agent context --json{  "workspace": "Acme Agent Workspace",  "apps": [    "customer_slack",    "files",    "state",    "browser"  ],  "pendingApprovals": 0}
Install

Four ways to put weavz on the path.

Homebrew
brew install weavz/tap/weavz
curl
curl -fsSL https://get.weavz.io/cli | sh
npx
npx -y @weavz-io/cli login
npm
npm install -g @weavz-io/cli
Command surface

A terminal control plane for the same workspace.

The CLI is useful for operators, coding agents, and developers who need a stable shell surface for the apps and actions already configured in Weavz.

Sign in and inspect

weavz login
weavz status
weavz whoami --json

Give an agent context

weavz agent context --json
weavz agent skill --format codex

Manage workspace apps

weavz apps search slack
weavz apps add slack --alias customer_slack
weavz apps connect customer_slack

Run actions and workflows

weavz actions search "send gmail email"
weavz run customer_gmail.send_email --json
weavz exec --json
Token boundary
The CLI uses OAuth device login, so it works from SSH sessions, containers, cloud IDEs, and local terminals.
Stored CLI credentials are scoped MCP OAuth tokens for the hosted Weavz MCP connector.
REST API and SDK calls still use a wvz_ API key. Do not pass CLI tokens to public API routes.

Connect a terminal to your workspace

Use the same app access from a local shell, coding agent or remote development environment.

How do I install the Weavz CLI?

Install @weavz-io/cli with npm, use npx, or follow the documented installation options. Run the login flow and choose the workspace the terminal should access.

Can a coding agent use the CLI?

Yes. A coding agent with terminal access can use CLI commands to discover tools and run actions in the connected workspace. The same account scopes, enabled actions and approval policies apply.

Does CLI login give access to every organization?

No. CLI access is scoped to the workspace selected during authorization. Confirm the active context before running a command that reads or changes external app data.