CLI commands
Global flags on mutating / listing commands:
| Flag | Meaning |
|---|---|
--json |
Print the API payload |
--plain |
No stickman |
--project, -p |
Project key or slug |
sprrint --help
sprrint tasks --help
Auth and you
sprrint login --email you@studio.com
sprrint logout
sprrint whoami
sprrint me update --display-name "Ejas" --timezone Asia/Dubai
sprrint keys list
sprrint keys create --name "Laptop" --source cli
sprrint keys revoke 12
Workspaces
Use X-Workspace-Slug automatically when workspace is set in config or SPRRINT_WORKSPACE. sprrint projects list follows that workspace. sprrint projects list --all lists every workspace you can see. Each project includes its workspace slug.
MCP does this without a config change. sprrint_projects_list returns every visible project unless the call passes workspace. See MCP tools.
sprrint workspaces list
sprrint workspaces create --name "Nova Studio" --slug nova
sprrint workspaces use acme
sprrint config set workspace acme
Workspace settings
sprrint workspace get
sprrint workspace update --description "Make things."
sprrint workspace invite maya@studio.com --role admin
sprrint workspace role 42 member
sprrint workspace remove 42
sprrint workspace leave
sprrint workspace delete --confirm "Acme Studio"
Projects
sprrint projects list
sprrint projects list --all
sprrint projects get BR
sprrint projects create --name "Ops Desk" --key OD
sprrint projects update BR --visibility workspace
sprrint projects archive BR
sprrint projects restore 7
sprrint projects delete BR --confirm "Brand Refresh"
sprrint projects add-member BR maya --role member
sprrint projects remove-member BR 18
The board
sprrint now
sprrint now --assigned me --due overdue
sprrint now --assigned none
sprrint overview
sprrint search "login"
sprrint activity --tab you --range 7
Tasks
sprrint tasks list --sprint launch-week
sprrint tasks get BR-12
sprrint tasks create --title "Ship the CLI" --priority high --tags "cli,mcp" --parent BR-9
sprrint tasks update BR-12 --status progress --assignee maya
sprrint tasks move BR-12 done
sprrint tasks move BR-12 blocked --blocked-note "Waiting on API access"
sprrint tasks move BR-12 done --confirm-complete
sprrint tasks comment BR-12 "Landed."
sprrint tasks git-link BR-12 feature/br-12-auth
sprrint tasks git-link BR-12 https://github.com/acme/app/pull/128
sprrint tasks git-unlink BR-12 42
sprrint tasks attach BR-12 ./brief.pdf
Statuses: todo, progress, blocked, qa_ready, qa_progress, qa_failed, done. QA transitions use tasks qa.
Priority: none, low, medium, high.
Assigned filter: me, any, none (unassigned), or a username.
Sprints
sprrint sprints list --status active
sprrint sprints get launch-week
sprrint sprints create --name "Launch Week" --starts-on 2026-09-01 --ends-on 2026-09-14 --status active --take BR-9,BR-10
sprrint sprints update launch-week --status done
sprrint sprints start launch-week
sprrint sprints pause launch-week
sprrint sprints complete launch-week
sprrint sprints delete launch-week --move free
Black Hole
sprrint blackhole list
sprrint blackhole pull BR-9
sprrint blackhole drop BR-9
pull sends the task to the landing sprint (an active sprint if one exists, otherwise the next planned one).
Categories and files
sprrint categories list
sprrint categories create task Infra
sprrint categories delete 22
sprrint files ./shot.png
Uploaded files return an id. For a task description, embed an image as  and any other file as [name](media:id). MCP clients send the bytes with sprrint_files_upload instead of a local path. Comment attachments still use sprrint tasks attach.
MCP
Agents connect at https://mcp.sprrint.run/mcp with Authorization: Bearer spr_live_…. Setup: ../mcp/setup.md.
sprrint mcp
That command is the local stdio process. New clients use the hosted URL.
QA rounds and findings
Task stages include qa_ready, qa_progress, and qa_failed. Normal moves and status edits use the QA round service. The first move to Ready for QA needs no message or owner. Starting testing assigns the person moving the task when no QA owner is set. Configure a different owner with tasks qa KEY configure --owner ID.
Each round has one editable testing note and one editable engineer response. The QA owner uses round_notes to save or edit all testing notes together, including inline media. Moving to QA Failed uses the saved notes; supply --qa-body if no testing notes exist. After a failed round, moving back to Ready for QA requires --qa-body, saved as the engineer response on the failed round. This creates the next round. There is no per-finding response or verification requirement. Completion requires the QA owner, testing notes, and completed subtasks.
sprrint projects update BR --qa-required
sprrint tasks move BR-12 qa_ready
sprrint tasks move BR-12 qa_progress
sprrint tasks qa BR-12 round_notes --body "Password feedback is missing"
sprrint tasks move BR-12 qa_failed
sprrint tasks move BR-12 progress
sprrint tasks move BR-12 qa_ready --qa-body "Fixed all issues from round 1"
sprrint tasks get BR-12 --json
sprrint tasks qa BR-12 round_response --round 18 --body "Updated fix explanation"
sprrint tasks move BR-12 qa_progress
sprrint tasks qa BR-12 round_notes --body "All checks passed"
sprrint tasks move BR-12 done
--round is the round ID returned in qa.rounds, not its display number. Omit it to edit the current round. --qa-owner on a move and --owner on configure take workspace user IDs. --file-ids on tasks qa attaches project files; inline  and [name](media:ID) are supported in notes and responses. enable and disable toggle the task's QA requirement at any time, preserving its owner, rounds, notes, and responses. The project default applies to newly created tasks. Legacy finding/reply/fix/verify/reopen actions remain available for existing clients and history.