The sbt command¶
sbt is how scripts and agents use SBT. Run it with no
arguments inside a repository to open SBT's terminal app.
sbt --help lists every command, and sbt <command> --help explains one.
The help is the reference: it is generated from the same code that runs.
Tasks¶
sbt create "Add a search filter" # prints the new ID, e.g. WEB-13
sbt list --ready # tasks with nothing blocking them
sbt view WEB-13 # one task in full
sbt edit WEB-13 --status "In Progress"
sbt edit WEB-13 --dod "Search works with an empty query"
sbt edit WEB-13 --append-notes "Filter added; tests pass."
sbt rank task WEB-13 --top # first in your order
A task ID works from any folder. Most commands take --json for output a
script can read.
Agents¶
An agent claims a task before it starts and releases it when it hands back. The claim is what shows you who is on what.
sbt skill install --agent all teaches Claude Code, Codex and Pi to do this
on their own. sbt mcp offers every command as a tool to any agent that
speaks the Model Context Protocol. It runs locally and opens no port.
Everything else¶
| Command | What it does |
|---|---|
sbt doctor |
Checks your setup and changes nothing |
sbt wiki |
Reads and edits the Library |
sbt form |
Publishes a question to the Inbox |
sbt pr |
Reads and merges pull requests |
sbt wait |
Waits for checks or for your answer, with a timeout |
sbt jobs |
Manages scheduled jobs |
sbt flags |
Lists flags and switches them off or on |
sbt share |
Exports and imports task lists |
sbt paths |
Prints where settings and logs live |
sbt stats |
Summarizes what you used, what was slow and what failed |