Public Rust command line interface for Plane. Manage projects, work items, and pages from your terminal — and install an agent skill so Claude Code, Codex, and OpenCode can drive Plane too.
Unix / macOS:
curl -fsSL https://releases.plane.powerformer.net/manage.sh | shWindows PowerShell:
irm https://releases.plane.powerformer.net/manage.ps1 | pwshThis installs the latest stable plane to ~/.local/bin/plane (Unix) or
%USERPROFILE%\.local\bin\plane.cmd (Windows). If that directory is on your
PATH, you're ready; otherwise see More install options.
-
Get an API token: sign in to your Plane backend (default
https://plane.powerformer.net), then avatar → Settings → API Tokens → create one and copy it. -
Save it to
~/.plane/plane.toml. Setapi_base_urlonly if your backend is not the default;workspace_slugis the default workspace for theproject/work-item/pagecommands:api_key = "<PLANE_API_TOKEN>" workspace_slug = "<your-workspace-slug>"
-
Verify access and explore:
plane api me plane api project list plane api work-item create --project <PROJECT_ID> --name "Fix login" --data '{"priority":"high"}' plane api page create --project <PROJECT_ID> --name "Design Review" --from-file notes.md
plane --help and plane api <resource> --help are the source of truth for
every command and flag.
plane ships a managed skill so coding agents discover the CLI cold:
plane skill installIt installs into detected Claude Code, Codex, and OpenCode homes (or an explicit
--path <dir>/plane-cli). Manage installs with plane skill list,
plane skill upgrade, and plane skill uninstall.
plane resolves configuration at startup: the config path is --config, then
PLANE_CONFIG, then {PLANE_HOME:-~/.plane}/plane.toml. Individual runtime
values use arg > config file > env > default; managed skill state defaults to
~/.plane/state/skills.json.
curl -fsSL https://releases.plane.powerformer.net/manage.sh | sh -s -- upgradeplane upgrade checks the release channel for a newer binary and prints the
command to run (it never replaces the binary itself — the manager does that).
Beta channel, pinning, uninstall, and PATH setup
Install the latest beta, or pin an exact version:
curl -fsSL https://releases.plane.powerformer.net/manage.sh | sh -s -- install --channel beta
curl -fsSL https://releases.plane.powerformer.net/manage.sh | sh -s -- install --version v0.1.0 --channel stableUninstall:
curl -fsSL https://releases.plane.powerformer.net/manage.sh | sh -s -- uninstallThe manager only creates the user command entry; it does not edit your PATH
unless you ask. To persist PATH setup explicitly:
curl -fsSL https://releases.plane.powerformer.net/manage.sh | sh -s -- path setup
curl -fsSL https://releases.plane.powerformer.net/manage.sh | sh -s -- path clearPowerShell:
$manager = Join-Path $env:TEMP "plane-manage.ps1"
iwr https://releases.plane.powerformer.net/manage.ps1 -OutFile $manager
pwsh -File $manager path setup
pwsh -File $manager path clearpath clear removes only the fixed plane-cli path marker block written by
path setup; it does not touch user-authored PATH lines.
Building, testing, hooks, releases, and the repository layout are documented in AGENTS.md, which is also the entry brief for AI coding agents.
MIT.