The Command Surface Shipped
A short list of reserved builtins, a registry for managing teams, a sessions group for past runs, and six commands every run-producing team gets for free.
Almost everything you type is a team command. The reserved top-level surface is deliberately small — the front door manages teams and past runs, and gets out of the way. Version 0.6.0 retired the old team management subcommand entirely; its verbs live under registry now.
The whole surface, from the front door
myteams with nothing after it prints the surface as it exists on your machine — your installed teams, and none of the disabled ones. This screen is assembled from the registry at run time, which is why no team name appears in the help text as written.registry — manage installed teams
| Command | Does |
|---|---|
| myteams registry list | Installed teams, with attribution and enabled state |
| myteams registry add <path> | Install a team from a directory |
| myteams registry remove <name> | Uninstall it |
| myteams registry describe <team> | The team, its specialists, and their specialties |
| myteams registry enable <team> | Turn it back on |
| myteams registry disable <team> | Leave it installed, take it off the surface |
sessions — every past run
| Command | Does |
|---|---|
| myteams sessions list | Runs across every team |
| myteams sessions log <run> | Replay that run's dispatch and finding timeline |
| myteams sessions findings <run> | The findings it produced |
| myteams sessions insights | Cross-run specialist digest |
| myteams sessions clear-cache <run> | Drop a run's cached state |
| myteams sessions prune | Retention — clear out what you no longer need |
config — the machine-wide settings
| Command | Does |
|---|---|
| myteams default-llms | Which models a review dispatches to by default |
| myteams set-default-llms <list> | Change them — a comma list, e.g. claude,codex |
| myteams config auth <verb> <provider> | Provider tokens, held in the OS keychain |
| myteams config mcp <verb> | The MCP server registry, and worker consent |
| myteams config quota <show|set|tap> | The auto-pause gate the pause and resume commands obey |
Six Shared Team Commands
myteams <team> report— write a field report for a run: measured facts plus a driver-filled reflection.myteams <team> pause— wait out the run's quota pause, then resume it.myteams <team> resume— resume the paused run now.myteams <team> log— replay that run's dispatch and finding timeline.myteams <team> findings— show the run's findings, filterable by minimum confidence.myteams <team> insights— a cross-run digest for that team, filterable by specialist.
How a team earns them
A team gets all six exactly when it declares a command named report — that is the whole test. Five of the six are pure CLI plumbing and appear in no team's definition; they are routed without ever invoking the team's planner. Each defaults to that team's latest run when you omit the run id, which is what makes myteams devteam findings a thing you can type from memory. A purely interactive team like brainstormteam declares no report, and so gets none of them.
In practice
myteams devteam findings --min-confidence 70
myteams devteam log
myteams researchteam insights --specialist verification-researcher
myteams sessions list