@brainbase-labs/cli 0.16.4 → 0.17.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -5
- package/dist/index.js +1810 -1178
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -18,6 +18,8 @@ brainbase template pack # bundle the current agent into a template
|
|
|
18
18
|
brainbase template publish # upload to the registry
|
|
19
19
|
brainbase template search # find templates published by your team
|
|
20
20
|
brainbase template onboard <creator/slug> # install or refresh a template
|
|
21
|
+
brainbase agent create # claim a local brainbase.agent.yaml
|
|
22
|
+
brainbase task create --message "Review this project and propose next steps"
|
|
21
23
|
```
|
|
22
24
|
|
|
23
25
|
Run `brainbase help` to see every command.
|
|
@@ -74,7 +76,7 @@ Playbook files carry a small YAML frontmatter (`title`, `description`) — the C
|
|
|
74
76
|
|
|
75
77
|
| Variable | Purpose |
|
|
76
78
|
|-|-|
|
|
77
|
-
| `BRAINBASE_CONTROL_PLANE_URL` | Override the MAS
|
|
79
|
+
| `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`. |
|
|
78
80
|
| `BRAINBASE_API_URL` | Legacy KLS host override. Control requests use `/api/cli`; it is also the fallback for model-proxy and registry traffic. |
|
|
79
81
|
| `BRAINBASE_PROXY_URL` | Override the model-proxy host used when enabling harness tracking. |
|
|
80
82
|
| `BRAINBASE_REGISTRY_URL` | Override the registry API host. |
|
|
@@ -86,12 +88,14 @@ the server captured at login, and finally `https://api.v1.brainbaselabs.com`.
|
|
|
86
88
|
|
|
87
89
|
## Auth
|
|
88
90
|
|
|
89
|
-
|
|
91
|
+
Managed task creation uses this authentication precedence:
|
|
90
92
|
|
|
91
|
-
1. `
|
|
92
|
-
2. `brainbase
|
|
93
|
+
1. `BRAINBASE_TOKEN` — an explicit PAT from the environment.
|
|
94
|
+
2. `brainbase login` — a Supabase session stored in `~/.brainbase/auth.json`.
|
|
95
|
+
3. `brainbase token create --scopes read,publish` — a PAT stored in `~/.brainbase/token.json` when no login session is configured.
|
|
93
96
|
|
|
94
|
-
|
|
97
|
+
An explicit PAT does not inherit routing from a stored login. Set
|
|
98
|
+
`BRAINBASE_CONTROL_PLANE_URL` when using a PAT against a non-default MAS host.
|
|
95
99
|
|
|
96
100
|
## License
|
|
97
101
|
|