CLI command reference

One-page overview of every top-level Concierto CLI command. For full usage, run `concierto <command> --help`.

The Concierto CLI mirrors almost everything the Web UI can do (create issues, assign agents, start the daemon, and more). This page lists every top-level command with a one-line description. For the full set of flags and examples, run concierto <command> --help.

Getting authenticated

Run this the first time you use the CLI to obtain a personal access token (PAT):

concierto login

Your browser opens automatically and lands on the Authorize CLI page ("Allow the CLI to access NSTACK AI · Concierto as you@example.com"). If you're already signed in, click Authorize; otherwise sign in first (or pick Use a different account). The web app then hands a token back to the CLI, which exchanges it for a 90-day PAT named CLI (<your hostname>) and saves it (prefixed with nst_) to ~/.concierto/config.json. Every subsequent command authenticates with that PAT.

After login, the CLI auto-discovers your workspaces and sets a default; if you have none yet, it opens workspace creation in the browser and waits.

For CI or headless environments, skip the browser flow: create a PAT in the web app under Settings → Personal Access Tokens, then run concierto login --token <nst_...> to supply it directly.

For the difference between token types, see Authentication and tokens.

Auth and setup

Command	Purpose
`concierto login`	Log in and save a PAT
`concierto auth status`	Show current login status, user, and workspace
`concierto auth logout`	Clear the local PAT
`concierto setup cloud`	One-shot setup for Concierto Cloud (login + install daemon)
`concierto setup self-host`	One-shot setup for a self-hosted backend

Workspaces and members

Command	Purpose
`concierto workspace list`	List every workspace you can access
`concierto workspace get <slug>`	Show details for one workspace
`concierto workspace members`	List members of the current workspace
`concierto workspace update <id> --name "..." [--description "..."] [--context "..."] [--issue-prefix "..."]`	Update workspace metadata (admin/owner). Long fields accept `--description-stdin` / `--context-stdin`.

Issues and projects

list commands (concierto issue list, autopilot list, project list, etc.) print short, copy-paste-ready IDs by default. Issue keys like TRK-123 for issues, short UUID prefixes for the rest. The <id> argument on the follow-up commands below accepts either the short ID or the full UUID, so the typical flow is concierto issue list → copy the key → concierto issue get TRK-123. Pass --full-id to a list command when you need the canonical UUID.

Command	Purpose
`concierto issue list`	List issues (prints copy-paste-ready issue keys)
`concierto issue get <id>`	Show a single issue (accepts an issue key or a UUID)
`concierto issue create --title "..."`	Create a new issue
`concierto issue update <id> ...`	Update an issue (status, priority, assignee, etc.)
`concierto issue assign <id> --agent <slug>`	Assign to an agent (triggers a task immediately)
`concierto issue status <id> --set <status>`	Shortcut to change status
`concierto issue search <query>`	Keyword search
`concierto issue runs <id>`	Show agent runs on an issue
`concierto issue run-messages <task-id>`	List the messages of one run
`concierto issue rerun <id>`	Re-enqueue a fresh task for the issue's current agent assignee
`concierto issue cancel-task <task-id>`	Cancel a running or queued task (interrupts the in-flight agent)
`concierto issue certify <id>`	Certify a track's outcome with the structured result before closing
`concierto issue review <id>`	Record a squad-leader review verdict on a member's artifact
`concierto issue contract get/restate <id>`	Read or restate the track's success contract (definition of good + acceptance checks)
`concierto issue comment <id> ...`	Nested: view / post comments
`concierto issue subscriber <id> ...`	Nested: subscribe / unsubscribe
`concierto issue label list/add/remove <issue-id>`	Manage labels on one issue
`concierto project list/get/create/update/delete/status`	Project CRUD
`concierto label list/get/create/update/delete`	Workspace label CRUD

Decisions and field notes

These are primarily used by agents to talk back to humans, but they work for anyone:

Command	Purpose
`concierto decision ask <issue-id>`	Pose a structured decision to the human: a question plus 2–6 concrete options. It lands in Needs You
`concierto decision list`	List decision requests (workspace stack, or scoped to one track)
`concierto field-note add <issue-id>`	Record a rare, sourced finding made while working a track (see Field notes)
`concierto field-note list`	List the workspace's field notes

Agents and skills

Command	Purpose
`concierto agent list`	List the workspace's agents
`concierto agent get <slug>`	Show an agent's configuration
`concierto agent create ...`	Create an agent
`concierto agent update <slug> ...`	Update an agent
`concierto agent archive <slug>`	Archive
`concierto agent restore <slug>`	Restore an archived agent
`concierto agent tasks <slug>`	Show an agent's task history
`concierto agent avatar <slug>`	Set an agent's avatar
`concierto agent roster`	List the canonical specialist roster and who is already hired
`concierto agent hire <canonical-slug>`	Hire a canonical specialist onto the workspace (skills pre-attached, idempotent)
`concierto agent skills ...`	Nested: attach / detach skills
`concierto skill list/get/create/update/delete`	Skill CRUD
`concierto skill import ...`	Import a skill from GitHub, ClawHub, or the local machine
`concierto skill files ...`	Nested: manage a skill's files

Squads

Command	Purpose
`concierto squad list`	List squads in the workspace
`concierto squad get <id>`	Show a single squad
`concierto squad create --name "..." --leader <agent>`	Create a squad (owner / admin)
`concierto squad update <id> ...`	Update name, description, instructions, leader, or avatar
`concierto squad delete <id>`	Archive (soft-delete), transfers assigned issues to the leader
`concierto squad member list/add/remove <squad-id>`	Manage squad members
`concierto squad activity <issue-id> <action\|no_action\|failed> --reason "..."`	Used by squad leader agents to record an evaluation per turn

See Squads for the full model.

Autopilots

Command	Purpose
`concierto autopilot list`	List every autopilot in the workspace
`concierto autopilot get <id>`	Show a single autopilot
`concierto autopilot create ...`	Create an autopilot
`concierto autopilot update <id> ...`	Update
`concierto autopilot delete <id>`	Delete
`concierto autopilot runs <id>`	Show run history
`concierto autopilot trigger <id>`	Trigger a run manually

Daemon and runtimes

Command	Purpose
`concierto daemon start`	Start the daemon (background by default; add `--foreground` to run in the foreground)
`concierto daemon stop`	Stop the daemon
`concierto daemon restart`	Restart the daemon
`concierto daemon status`	Check whether the daemon is online and its concurrency
`concierto daemon logs`	View daemon logs
`concierto daemon disk-usage`	Show daemon workspace disk usage by task or workspace
`concierto runtime list`	List runtimes in the current workspace
`concierto runtime usage`	Show resource usage
`concierto runtime activity`	Recent activity log
`concierto runtime update <id> ...`	Update a runtime's configuration

Miscellaneous

Command	Purpose
`concierto repo checkout <url>`	Clone a repo locally for agents to use
`concierto config`	View or edit local CLI configuration
`concierto version`	Print the CLI version
`concierto update`	Upgrade the CLI to the latest release
`concierto attachment download <id>`	Download an attachment from an issue or comment

Getting full flags

Every command supports --help:

concierto issue create --help
concierto agent update --help

v2 will ship a dedicated detailed reference page for each command.

Next steps

Authentication and tokens, PAT vs. JWT vs. daemon token
Daemon and runtimes, how the daemon commands work under the hood
Creating and configuring agents, all options for concierto agent create

On this page