CLI reference
Every pando command and option, as printed by --help. For a task-by-task guide, start with Try it in 5 minutes; for git equivalents, see Coming from git.
pando clone
Create a workspace and check out a ref (lazily, and sparsely with --path)
Usage: pando clone [OPTIONS] <SERVER> <DIR>
Arguments:
<SERVER>
<DIR>
Options:
--ref <REF_NAME> [default: main]
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--path <PATHS> Only materialise these paths (repeatable)
--objects <OBJECTS> Fetch objects through a node daemon or regional cache [env: PANDO_OBJECTS=]
-h, --help Print help
-V, --version Print version
pando status
Show working-copy changes
Usage: pando status [OPTIONS] [PATHS]...
Arguments:
[PATHS]...
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando commit
Create a changeset on the server from working-copy changes (all, or PATHS)
Usage: pando commit [OPTIONS] --message <MESSAGE> [PATHS]...
Arguments:
[PATHS]...
Options:
-m, --message <MESSAGE>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando land
Land the committed work on the ref (server-side rebase + atomic ref update)
Usage: pando land [OPTIONS]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando sync
Update the working copy to the ref head (or REV)
Usage: pando sync [OPTIONS] [REV]
Arguments:
[REV]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando checkout
Switch to a ref or changeset; -b creates a ref at the current base
Usage: pando checkout [OPTIONS] <TARGET>
Arguments:
<TARGET>
Options:
-b
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando log
Changeset history (server-side; no local history needed)
Usage: pando log [OPTIONS] [PATH]
Arguments:
[PATH] Limit to a path
Options:
--rev <REV>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-n, --limit <LIMIT> [default: 20]
--oneline
-h, --help Print help
-V, --version Print version
pando diff
Diff the working copy, or two revisions (`pando diff A B`)
Usage: pando diff [OPTIONS] [REVS]...
Arguments:
[REVS]...
Options:
--name-only
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando show
Show a changeset and its patch against its first parent
Usage: pando show [OPTIONS] [REV]
Arguments:
[REV]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cat
Print a file at a revision without checking anything out
Usage: pando cat [OPTIONS] <REV> <PATH>
Arguments:
<REV>
<PATH>
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando lock
Lock files for exclusive editing (for files that cannot be merged). Others cannot land changes to them until you unlock
Usage: pando lock [OPTIONS] <PATHS>...
Arguments:
<PATHS>...
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando unlock
Release your locks; --force releases someone else's (needs write access)
Usage: pando unlock [OPTIONS] <PATHS>...
Arguments:
<PATHS>...
Options:
--force
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando locks
List locks, optionally under a directory
Usage: pando locks [OPTIONS] [PREFIX]
Arguments:
[PREFIX] [default: ""]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando ls
List a directory at a revision without checking anything out
Usage: pando ls [OPTIONS] <REV> [PATH]
Arguments:
<REV>
[PATH] [default: ""]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando find
Find files by path substring at a revision (server-side)
Usage: pando find [OPTIONS] <PATTERN>
Arguments:
<PATTERN>
Options:
--rev <REV> [default: main]
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando blame
Show which changeset last changed each line of a file
Usage: pando blame [OPTIONS] <PATH>
Arguments:
<PATH>
Options:
--rev <REV> [default: main]
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando refs
List refs
Usage: pando refs [OPTIONS]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando merge-base
Best common ancestor of two revisions
Usage: pando merge-base [OPTIONS] <A> <B>
Arguments:
<A>
<B>
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando import-git
Import a git repository's history
Usage: pando import-git [OPTIONS] <GIT_DIR>
Arguments:
<GIT_DIR>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--git-ref <GIT_REF> [default: HEAD]
--ref <REF_NAME> [default: main]
--force
-h, --help Print help
-V, --version Print version
pando mount
Mount a revision read-only; files are fetched on first read (Linux, macOS, Windows)
Usage: pando mount [OPTIONS] <DIR>
Arguments:
<DIR>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--objects <OBJECTS> Daemon or cache serving objects
--rev <REV> [default: main]
--cache-mb <CACHE_MB> In-memory cache for file contents [default: 256]
--serve-only Serve the checkout over NFS on localhost and print the command that mounts it, instead of mounting (for machines where only an administrator may mount, or Linux machines without FUSE)
-h, --help Print help
-V, --version Print version
pando mcp
Serve Grovedock as MCP tools over stdio for AI agents (Claude Code, Codex, Cursor...)
Usage: pando mcp [OPTIONS]
Options:
--server <SERVER>
--token <TOKEN>
Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--http <ADDR>
Serve the whole server to remote agents over HTTP at this address (e.g. 0.0.0.0:7430), instead of one workspace over stdio. Each request's bearer token is passed through to the server
--allowed-host <ALLOWED_HOSTS>
Host names clients use to reach the HTTP endpoint (repeatable); default: loopback only, against DNS rebinding
--allowed-origin <ALLOWED_ORIGINS>
Browser origins allowed to call the HTTP endpoint (repeatable), e.g. https://app.example.com:443; default: none (requests with an Origin are refused)
-h, --help
Print help
-V, --version
Print version
pando login
Sign in to a server from the browser; the token is saved in ~/.config/pando/credentials.json
Usage: pando login [OPTIONS] [SERVER]
Arguments:
[SERVER] The server, e.g. https://pando.example.com; default $PANDO_SERVER or the workspace's
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando logout
Revoke the token `pando login` saved for a server, and forget it
Usage: pando logout [OPTIONS] [SERVER]
Arguments:
[SERVER]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando whoami
Show who you are signed in as
Usage: pando whoami [OPTIONS] [SERVER]
Arguments:
[SERVER]
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando repo
Create and list repositories on a server that hosts many (`pandod server --platform`)
Usage: pando repo [OPTIONS] <COMMAND>
Commands:
create Create OWNER/NAME. Then: `pando clone SERVER/OWNER/NAME`
list List repositories, optionally of one owner
grant Give a person, agent or team (ORG/TEAM) a role on a repository; `none` removes it. With only the repository, lists who has access
help Print this message or the help of the given subcommand(s)
Options:
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando repo create
Create OWNER/NAME. Then: `pando clone SERVER/OWNER/NAME`
Usage: pando repo create [OPTIONS] <NAME>
Arguments:
<NAME>
Options:
--description <DESCRIPTION> [default: ""]
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--server <SERVER>
-h, --help Print help
-V, --version Print version
pando repo list
List repositories, optionally of one owner
Usage: pando repo list [OPTIONS]
Options:
--owner <OWNER> [default: ""]
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--server <SERVER>
-h, --help Print help
-V, --version Print version
pando repo grant
Give a person, agent or team (ORG/TEAM) a role on a repository; `none` removes it. With only the repository, lists who has access
Usage: pando repo grant [OPTIONS] <REPO> [PRINCIPAL] [ROLE]
Arguments:
<REPO>
[PRINCIPAL]
[ROLE]
Possible values:
- read
- triage
- write
- maintain
- admin
- none: Removes the member or grant
Options:
--server <SERVER>
--token <TOKEN>
Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved
[env: PANDO_TOKEN]
-h, --help
Print help (see a summary with '-h')
-V, --version
Print version
pando org
Organisations and their members
Usage: pando org [OPTIONS] <COMMAND>
Commands:
list Organisations you belong to (all of them, for site administrators)
create Create an organisation; you become its administrator. Site administrators only
members List an organisation's members and their roles
member Add a member, change their role, or remove them with `none`
usage The organisation's plan, limits and use: active agents this month, people, storage. Organisation administrators
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando org list
Organisations you belong to (all of them, for site administrators)
Usage: pando org list [OPTIONS]
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando org create
Create an organisation; you become its administrator. Site administrators only
Usage: pando org create [OPTIONS] <NAME>
Arguments:
<NAME>
Options:
--description <DESCRIPTION> [default: ""]
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando org members
List an organisation's members and their roles
Usage: pando org members [OPTIONS] <ORG>
Arguments:
<ORG>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando org member
Add a member, change their role, or remove them with `none`
Usage: pando org member [OPTIONS] <ORG> <LOGIN> <ROLE>
Arguments:
<ORG>
<LOGIN>
<ROLE>
Possible values:
- read
- triage
- write
- maintain
- admin
- none: Removes the member or grant
Options:
--server <SERVER>
--token <TOKEN>
Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved
[env: PANDO_TOKEN]
-h, --help
Print help (see a summary with '-h')
-V, --version
Print version
pando org usage
The organisation's plan, limits and use: active agents this month, people, storage. Organisation administrators
Usage: pando org usage [OPTIONS] <ORG>
Arguments:
<ORG>
Options:
--month <MONTH> A past month, YYYY-MM (default: this month, UTC) [default: ""]
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando team
Teams within an organisation, for granting access to many people at once
Usage: pando team [OPTIONS] <COMMAND>
Commands:
list List an organisation's teams
set Create a team, or replace its members: `pando team set lumen/platform --member mira`
delete Delete a team and its grants
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando team list
List an organisation's teams
Usage: pando team list [OPTIONS] <ORG>
Arguments:
<ORG>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando team set
Create a team, or replace its members: `pando team set lumen/platform --member mira`
Usage: pando team set [OPTIONS] <TEAM>
Arguments:
<TEAM> ORG/TEAM
Options:
--member <MEMBERS> A member of the organisation (repeatable)
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--name <NAME> [default: ""]
-h, --help Print help
-V, --version Print version
pando team delete
Delete a team and its grants
Usage: pando team delete [OPTIONS] <TEAM>
Arguments:
<TEAM> ORG/TEAM
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cr
Change requests: propose a branch, review it, land it
Usage: pando cr [OPTIONS] <COMMAND>
Commands:
create Propose a branch for landing on another: `pando cr create --title "…"`
list List change requests
view Show one, with what still blocks it
comment Comment, on the change or on a line of a file
review Approve, request changes, or comment
check Report a CI check on the current version: `pando cr check 12 build passed --url …`
land Land it, once nothing blocks it
rebase Replay it on the target's tip
ready Mark a draft ready for review
close
reopen
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cr create
Propose a branch for landing on another: `pando cr create --title "…"`
Usage: pando cr create [OPTIONS] --title <TITLE>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--title <TITLE>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--body <BODY> [default: ""]
--source <SOURCE> The branch to land; defaults to the workspace's branch
--target <TARGET> Where to land it; defaults to the repository's default branch [default: ""]
--draft
--reviewer <REVIEWERS> Ask someone to review (repeatable)
-h, --help Print help
-V, --version Print version
pando cr list
List change requests
Usage: pando cr list [OPTIONS]
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--state <STATE> [default: open] [possible values: open, draft, landed, closed, all]
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--author <AUTHOR> Only this author; `agent/*` for every agent [default: ""]
-h, --help Print help
-V, --version Print version
pando cr view
Show one, with what still blocks it
Usage: pando cr view [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cr comment
Comment, on the change or on a line of a file
Usage: pando cr comment [OPTIONS] --message <MESSAGE> <NUMBER>
Arguments:
<NUMBER>
Options:
-m, --message <MESSAGE>
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--path <PATH>
--line <LINE>
-h, --help Print help
-V, --version Print version
pando cr review
Approve, request changes, or comment
Usage: pando cr review [OPTIONS] <NUMBER> <VERDICT>
Arguments:
<NUMBER>
<VERDICT>
Possible values:
- approve
- changes: Request changes
- comment
Options:
-m, --message <MESSAGE>
[default: ""]
--server <SERVER>
The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN>
Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved
[env: PANDO_TOKEN]
-h, --help
Print help (see a summary with '-h')
-V, --version
Print version
pando cr check
Report a CI check on the current version: `pando cr check 12 build passed --url …`
Usage: pando cr check [OPTIONS] <NUMBER> <NAME> <STATE>
Arguments:
<NUMBER>
<NAME>
<STATE> [possible values: pending, passed, failed, skipped]
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--url <URL> [default: ""]
--summary <SUMMARY> [default: ""]
-h, --help Print help
-V, --version Print version
pando cr land
Land it, once nothing blocks it
Usage: pando cr land [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cr rebase
Replay it on the target's tip
Usage: pando cr rebase [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cr ready
Mark a draft ready for review
Usage: pando cr ready [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cr close
Usage: pando cr close [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando cr reopen
Usage: pando cr reopen [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando issue
Issues: work to do, assigned to people or agents; "fixes #N" in a change request closes one when it lands
Usage: pando issue [OPTIONS] <COMMAND>
Commands:
create Open an issue
list
view
comment
assign Give an issue to people or agents (replaces the assignees)
close Close an issue as done (or `--not-planned`)
reopen
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando issue create
Open an issue
Usage: pando issue create [OPTIONS] --title <TITLE>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--title <TITLE>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--body <BODY> [default: ""]
--assignee <ASSIGNEES> Who should work on it, a person or an agent (repeatable)
--label <LABELS>
-h, --help Print help
-V, --version Print version
pando issue list
Usage: pando issue list [OPTIONS]
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--state <STATE> [default: open] [possible values: open, closed, all]
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--assignee <ASSIGNEE> [default: ""]
--label <LABEL> [default: ""]
-h, --help Print help
-V, --version Print version
pando issue view
Usage: pando issue view [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando issue comment
Usage: pando issue comment [OPTIONS] --message <MESSAGE> <NUMBER>
Arguments:
<NUMBER>
Options:
-m, --message <MESSAGE>
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando issue assign
Give an issue to people or agents (replaces the assignees)
Usage: pando issue assign [OPTIONS] <NUMBER> [ASSIGNEES]...
Arguments:
<NUMBER>
[ASSIGNEES]...
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando issue close
Close an issue as done (or `--not-planned`)
Usage: pando issue close [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--not-planned
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando issue reopen
Usage: pando issue reopen [OPTIONS] <NUMBER>
Arguments:
<NUMBER>
Options:
--server <SERVER> The repository, SERVER/OWNER/NAME; defaults to the workspace's
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando protect
Protected branches: changes land on them only through a reviewed change request
Usage: pando protect [OPTIONS] <COMMAND>
Commands:
list List protected branches
set Protect a branch or prefix (`main`, `release/*`)
remove Stop protecting a branch or prefix
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando protect list
List protected branches
Usage: pando protect list [OPTIONS]
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando protect set
Protect a branch or prefix (`main`, `release/*`)
Usage: pando protect set [OPTIONS] <PATTERN>
Arguments:
<PATTERN>
Options:
--approvals <APPROVALS> Approvals needed before a change request lands [default: 1]
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--check <CHECKS> A check that must pass (repeatable)
--keep-stale Keep approvals when the branch changes after them
--agents-direct Let agents land on it directly, without review
--bypass <BYPASS> Who may land without review: a login, a team `org/team`, or `admins` (repeatable)
-h, --help Print help
-V, --version Print version
pando protect remove
Stop protecting a branch or prefix
Usage: pando protect remove [OPTIONS] <PATTERN>
Arguments:
<PATTERN>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando webhook
Webhooks: call a URL (CI, chat, trackers) when something happens in a repository
Usage: pando webhook [OPTIONS] <COMMAND>
Commands:
list A repository's webhooks: `pando webhook list lumen/fleet`
add Call URL when something happens in the repository. Prints the signing secret once
ping Send a ping now and show how it went
log Recent deliveries and their answers
remove
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando webhook list
A repository's webhooks: `pando webhook list lumen/fleet`
Usage: pando webhook list [OPTIONS] <REPO>
Arguments:
<REPO>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando webhook add
Call URL when something happens in the repository. Prints the signing secret once
Usage: pando webhook add [OPTIONS] <REPO> <URL>
Arguments:
<REPO>
<URL>
Options:
--event <EVENTS> Only these events (repeatable): push, change_request, review, comment, check, issue
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando webhook ping
Send a ping now and show how it went
Usage: pando webhook ping [OPTIONS] <ID>
Arguments:
<ID>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando webhook log
Recent deliveries and their answers
Usage: pando webhook log [OPTIONS] <ID>
Arguments:
<ID>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando webhook remove
Usage: pando webhook remove [OPTIONS] <ID>
Arguments:
<ID>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando token
Access tokens for you and for agents you answer for
Usage: pando token [OPTIONS] <COMMAND>
Commands:
list Your tokens
create Create a token. Prints it once: store it as PANDO_TOKEN
revoke Revoke a token by its id
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando token list
Your tokens
Usage: pando token list [OPTIONS]
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando token create
Create a token. Prints it once: store it as PANDO_TOKEN
Usage: pando token create [OPTIONS] <NAME>
Arguments:
<NAME>
Options:
--as <ACTS_AS>
Act as an agent you answer for, e.g. `agent/refactor-07` (created if new)
--server <SERVER>
--token <TOKEN>
Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved
[env: PANDO_TOKEN]
--repo <REPOSITORIES>
Only these repositories, OWNER/NAME (repeatable); default: all you can reach
--role <ROLE>
Highest role the token may use
Possible values:
- read
- triage
- write
- maintain
- admin
- none: Removes the member or grant
[default: write]
--days <DAYS>
Days until it expires (1–366)
[default: 90]
-h, --help
Print help (see a summary with '-h')
-V, --version
Print version
pando token revoke
Revoke a token by its id
Usage: pando token revoke [OPTIONS] <ID>
Arguments:
<ID>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin
Server administration (site administrators only)
Usage: pando admin [OPTIONS] <COMMAND>
Commands:
signup Who may create an account by signing in (`pandod server --signup waitlist`)
identity Ways people sign in from a browser
limits Organisations' plans and limits (enforced with `pandod server --multi-tenant`)
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin signup
Who may create an account by signing in (`pandod server --signup waitlist`)
Usage: pando admin signup [OPTIONS] <COMMAND>
Commands:
allow Let an email address, or everyone at `@domain`, create an account
remove Take an entry off the list (accounts already created stay)
list
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin signup allow
Let an email address, or everyone at `@domain`, create an account
Usage: pando admin signup allow [OPTIONS] <ENTRY>
Arguments:
<ENTRY>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin signup remove
Take an entry off the list (accounts already created stay)
Usage: pando admin signup remove [OPTIONS] <ENTRY>
Arguments:
<ENTRY>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin signup list
Usage: pando admin signup list [OPTIONS]
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin identity
Ways people sign in from a browser
Usage: pando admin identity [OPTIONS] <COMMAND>
Commands:
link Let an identity sign in as an existing account, e.g. the first administrator: `pando admin identity link kabir --provider email --subject kabir@example.com`
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin identity link
Let an identity sign in as an existing account, e.g. the first administrator: `pando admin identity link kabir --provider email --subject kabir@example.com`
Usage: pando admin identity link [OPTIONS] --provider <PROVIDER> --subject <SUBJECT> <LOGIN>
Arguments:
<LOGIN>
Options:
--provider <PROVIDER> `email`, or a sign-in provider's id such as `google`
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--subject <SUBJECT> The email address, or the provider's `sub` for the person
-h, --help Print help
-V, --version Print version
pando admin limits
Organisations' plans and limits (enforced with `pandod server --multi-tenant`)
Usage: pando admin limits [OPTIONS] <COMMAND>
Commands:
show The limits that apply to an organisation and what it uses
set Change some limits; the others stay. A number, or `unlimited`
suspend Stop an organisation writing (it can still read)
restore Let a suspended organisation write again
help Print this message or the help of the given subcommand(s)
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin limits show
The limits that apply to an organisation and what it uses
Usage: pando admin limits show [OPTIONS] <ORG>
Arguments:
<ORG>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin limits set
Change some limits; the others stay. A number, or `unlimited`
Usage: pando admin limits set [OPTIONS] <ORG>
Arguments:
<ORG>
Options:
--seats <SEATS>
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--agents <AGENTS> Agents that land a change in a calendar month
--storage <STORAGE> e.g. 10GiB
--private-repos <PRIVATE_REPOS>
--plan <PLAN> The plan's name as people see it
-h, --help Print help
-V, --version Print version
pando admin limits suspend
Stop an organisation writing (it can still read)
Usage: pando admin limits suspend [OPTIONS] <ORG>
Arguments:
<ORG>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando admin limits restore
Let a suspended organisation write again
Usage: pando admin limits restore [OPTIONS] <ORG>
Arguments:
<ORG>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
-h, --help Print help
-V, --version Print version
pando migrate
Move a repository from any git host to Grovedock: full history, and from GitHub, open pull requests (as change requests) and issues with their comments
Usage: pando migrate [OPTIONS] --to <TO> <FROM>
Arguments:
<FROM> Where it is now: any URL git can clone
Options:
--to <TO>
Where it goes: SERVER/OWNER/NAME
--token <TOKEN>
Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--github-token <GITHUB_TOKEN>
For private GitHub repositories, and to avoid GitHub's rate limit. Prefer the PANDO_GITHUB_TOKEN (or GITHUB_TOKEN) environment variable or --github-token-file: a value given here is visible to other users of the machine (`ps`) [env: PANDO_GITHUB_TOKEN]
--github-token-file <GITHUB_TOKEN_FILE>
Read the GitHub token from this file
--no-issues
Skip issues
--no-pull-requests
Skip pull requests
--github-api <GITHUB_API>
GitHub Enterprise Server's API, e.g. https://github.example.com/api/v3
-h, --help
Print help
-V, --version
Print version
pando mirror
Keep a git repository (GitHub, GitLab, Bitbucket, any git remote) up to date with a branch: every landed change becomes the same git commit every time, pushed without force
Usage: pando mirror [OPTIONS] --to <TO>
Options:
--to <TO> Where to push: any URL git accepts. Credentials come from git (SSH keys or a credential helper)
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--server <SERVER>
--rev <REV> [default: main]
--git-ref <GIT_REF> [default: main]
--dir <DIR> The mirror's local copy (a bare git repository); defaults to the user cache
--every <SECONDS> Mirror again every SECONDS until interrupted; without it, mirror once and exit
-h, --help Print help
-V, --version Print version
pando export-git
Export first-parent history to a git repository
Usage: pando export-git [OPTIONS] <GIT_DIR>
Arguments:
<GIT_DIR>
Options:
--server <SERVER>
--token <TOKEN> Bearer token for the server ($PANDO_TOKEN); without one, the token `pando login` saved [env: PANDO_TOKEN]
--rev <REV> [default: main]
--git-ref <GIT_REF> [default: main]
-h, --help Print help
-V, --version Print version