@brainbase-labs/cli 0.16.5 → 0.18.0

package/README.md

@@ -14,10 +14,14 @@ The package installs a `brainbase` command on your PATH. Requires Node.js 18+.
 
 ```sh
 brainbase login                 # connect this device to brainbase
+brainbase team list             # which teams can I put agents in?
+brainbase agent list            # which agents are in a team, and what are their ids?
 brainbase template pack         # bundle the current agent into a template
 brainbase template publish      # upload to the registry
 brainbase template search       # find templates published by your team
 brainbase template onboard <creator/slug>   # install or refresh a template
+brainbase agent create          # claim a local brainbase.agent.yaml
+brainbase task create --message "Review this project and propose next steps"
 ```
 
 Run `brainbase help` to see every command.
@@ -74,7 +78,7 @@ Playbook files carry a small YAML frontmatter (`title`, `description`) — the C
 
 | Variable | Purpose |
 |-|-|
-| `BRAINBASE_CONTROL_PLANE_URL` | Override the MAS control-plane host. Requests use `/v2/cli`; the default is `https://api.brainbaselabs.com`. |
+| `BRAINBASE_CONTROL_PLANE_URL` | Override the MAS host. Agent/orchestration requests use `/v2/cli`; `task create` uses `/v2/tasks`. The default is `https://api.brainbaselabs.com`. |
 | `BRAINBASE_API_URL` | Legacy KLS host override. Control requests use `/api/cli`; it is also the fallback for model-proxy and registry traffic. |
 | `BRAINBASE_PROXY_URL` | Override the model-proxy host used when enabling harness tracking. |
 | `BRAINBASE_REGISTRY_URL` | Override the registry API host. |
@@ -86,12 +90,14 @@ the server captured at login, and finally `https://api.v1.brainbaselabs.com`.
 
 ## Auth
 
-Two ways to authenticate, in priority order:
+Managed task creation uses this authentication precedence:
 
-1. `brainbase login` — interactive Supabase OAuth, stored in `~/.brainbase/auth.json`. Carries full scopes.
-2. `brainbase token create --scope publish` — long-lived PAT (`bbpat_…`) for CI / unattended use.
+1. `BRAINBASE_TOKEN` — an explicit PAT from the environment.
+2. `brainbase login` — a Supabase session stored in `~/.brainbase/auth.json`.
+3. `brainbase token create --scopes read,publish` — a PAT stored in `~/.brainbase/token.json` when no login session is configured.
 
-`BRAINBASE_TOKEN` env var overrides both.
+An explicit PAT does not inherit routing from a stored login. Set
+`BRAINBASE_CONTROL_PLANE_URL` when using a PAT against a non-default MAS host.
 
 ## License