Runwork CLI
Your terminal interface to the work cloud
One CLI to connect your AI agents, manage workspace resources, and develop apps. Zero local dependencies. Full platform parity with the web dashboard.
Install Runwork CLI
No runtime dependencies. Works on macOS, Linux, and Windows.
Also available via
Then run
runwork login
to authenticate and
runwork setup
to connect your AI agents.
Get Started
Connect yourself and your AI agents to the workspace.
runwork login
Authenticate with the Runwork platform.
runwork setup
Auto-detects and configures 8 AI agents with your workspace skills and MCP servers: Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Copilot (VSCode + CLI), and Gemini.
AI Ecosystem
Manage skills, MCP servers, agents, and keep everything in sync.
runwork skills
List workspace skills or push new ones from local files.
runwork mcp
Add, remove, and list MCP servers in your workspace.
runwork agents
List agents, check status, and view execution history.
runwork sync
Refresh local agent configs with the latest workspace skills and MCP servers.
Workspace Resources
Create and manage work primitives from the terminal.
runwork entities
Full CRUD for workspace entity data. Create, read, update, delete records.
runwork workflows
List, trigger, and inspect workflow instances.
runwork schedules
Manage scheduled jobs: trigger, pause, resume, view history.
runwork integrations
Search the catalog, list connections, and call integration APIs directly.
runwork files
Upload, download, and manage files in workspace storage buckets.
runwork endpoints
List public endpoints and call them directly from the terminal.
Development
Build and ship vibe apps. Ideally your AI agent handles this for you.
runwork init
Create a new app. The platform provides CLAUDE.md + AGENTS.md on the fly, plus SKILL.md for your app.
runwork dev
Boots a remote sandbox with live preview and file watching. No Docker, no local runtime.
runwork deploy
One command to production. No build pipelines to configure.
Access from anywhere
Web Dashboard
Every CLI command has a dashboard equivalent. Use whichever you prefer, or both.
Open in dashboardCLI
Use Cases
Why It Matters
- Full platform parity. Every workspace feature has a CLI command.
- The same CLI powers agent sandboxes. Your agents get the same capabilities you have.
- Cross-platform: macOS (Apple Silicon + Intel), Linux (x64 + ARM), Windows.
- Zero local dependencies. No Docker, no Node, no runtime to install.
- Every command supports --json for machine-readable output. AI agents parse it natively.
How It Works
Connect your AI agents. Run runwork setup to auto-detect and configure up to 8 AI agents, including Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Copilot (VSCode and CLI), and Gemini, with your workspace's skills and MCP servers. Run runwork sync whenever your workspace changes. Your agents always have the latest context.
Manage workspace resources. Create entities, trigger workflows, pause schedules, upload files, call integrations, manage API keys. Every workspace feature is a CLI command. Lead with creation: runwork entities create, runwork workflows trigger, runwork schedules trigger.
Develop and deploy apps. runwork init creates a new app. runwork dev boots a remote sandbox with live preview and file watching. runwork deploy ships to production. During development, the platform provides CLAUDE.md + AGENTS.md on the fly, plus auto-generated SKILL.md per app. Claude Code, Cursor, and Codex understand your project from the moment you start.
Zero local dependencies. When you run runwork dev, your code executes in a remote sandbox. You edit files locally, the CLI syncs them via git protocol, and the sandbox handles builds, execution, and preview serving. No Docker, no Node, no runtime on your machine.
Ideally, your AI agent handles all of this for you. You say "build me a customer portal" and your agent runs init, dev, deploy under the hood. The CLI is also the bridge that powers agent sandboxes, giving your AI agents the same terminal capabilities you use during development.