CLI
The polylane command lets you use every part of Polylane from a terminal, a script or a coding agent. Output is a text table in a terminal and JSON when piped, every prompt can be turned off, and the full API is available for anything that is not a command yet.
What it does
Each command group wraps one part of the platform: issues, services and their logs, repositories, threads, memories, agent tools and more. Every command accepts the same non-interactive flags, so a script or an agent can run it without prompts; see Scripting.
Install
All four channels install the same command.
npm install -g @coreplane/polylane
brew install coreplanelabs/tap/polylane
curl -fsSL https://polylane.com/install.sh | bash
irm https://polylane.com/install.ps1 | iex
Sign in
polylane auth login
polylane auth login --no-browser
polylane auth login --api-key sk_xxxxx
The first form opens your browser, --no-browser prints a device code for SSH and headless machines, and --api-key stores an API key for scripts and agents. Authentication covers each method and where credentials are stored.
Command groups
| Group | Description |
|---|---|
feed | The workspace activity feed: recent events across the workspace |
issue | Detected issues, their timelines, notes and milestones |
service | Cloud infrastructure: nodes, logs, metrics, dependency graph |
repo | Repositories and code search |
tools | Run Polylane agent tools directly (tools search, tools run, tools code) |
memory | Persistent agent memory |
note | Daily and global workspace notes |
thread | Conversation threads (thread ask, thread continue, streaming supported) |
artifact | Per-thread artifacts: reports, diagrams, pull requests |
skill | Agent skills: catalog, list, show, docs, from-template |
autofix | Automated code fixes (read-only) |
integration | Integrations: code hosts, chat, observability, issue tracking, coding agents, MCP servers |
cloud | Cloud accounts for every provider in the catalog |
workspace | Create and switch workspaces |
auth | Login, status, logout |
setup | Wire the CLI into your coding agents: agent skill and MCP server |
config | CLI configuration |
telemetry | Anonymous usage telemetry: status, enable, disable |
api | Raw API access |
update | Check for CLI updates |
Discover commands
--help is the authoritative reference and always matches the version you have installed: run it on polylane, on a resource, or on a single command for its flags and examples. Anything not yet a first-class command is available under polylane api, whose list, describe and call subcommands reach every operation in the API reference.
Uninstall
curl -fsSL https://polylane.com/uninstall | sh
The uninstaller backs up ~/.polylane to a tarball in your home directory, then removes the CLI, the MCP servers and skills it registered in your coding agents, and the PATH entries it added; preview every step with sh -s -- --dry-run. Your account, workspace and integrations stay as they are, and if you installed with npm, run npm uninstall -g @coreplane/polylane as well.
Related
- Authentication: every sign-in method and where credentials are stored.
- Scripting: JSON output, exit codes and the flags for CI and agents.
- Configuration: environment variables, the config file and telemetry.
- Plugins: install the CLI skill and the MCP servers into your coding agent in one step.