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.
$ npm install -g @weavz-io/cli$ weavz login$ weavz agent context --json{ "workspace": "Acme Agent Workspace", "apps": [ "customer_slack", "files", "state", "browser" ], "pendingApprovals": 0}Four ways to put weavz on the path.
brew install weavz/tap/weavzcurl -fsSL https://get.weavz.io/cli | shnpx -y @weavz-io/cli loginnpm install -g @weavz-io/cliA 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
Give an agent context
Manage workspace apps
Run actions and workflows
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.