@brainbase-labs/cli 0.45.0 → 0.47.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 +10 -6
- package/dist/index.js +3167 -1650
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -53,8 +53,9 @@ brainbase task send <task-id> "Use the revised approach instead" --json
|
|
|
53
53
|
brainbase task stop <task-id>
|
|
54
54
|
```
|
|
55
55
|
|
|
56
|
-
`send`
|
|
57
|
-
|
|
56
|
+
`send` reports the input ID and delivery status in stdout. The input ID and
|
|
57
|
+
generation needed to recover a send are printed only when one did not finish:
|
|
58
|
+
on an error, on an unconfirmed receipt, or when it is interrupted. Initial acceptance can say **delivery pending** while the
|
|
58
59
|
server determines whether native steering is available. Native steering follows
|
|
59
60
|
the harness's own timing. A confirmed fallback says **queued for the next turn**.
|
|
60
61
|
`submitted` means the harness has received the input; it does not mean the agent
|
|
@@ -67,8 +68,8 @@ Resource-scoped keys can lack that read access when task-read enforcement is ena
|
|
|
67
68
|
If the read fails, no mutation is sent. Use `--generation <n>` to bypass the read only
|
|
68
69
|
with a trusted current cutoff for a new operation, or the original cutoff for a retry.
|
|
69
70
|
A concurrent Stop prevents a send from joining newer work with an older generation.
|
|
70
|
-
If the HTTP response is lost or you press Ctrl-C,
|
|
71
|
-
|
|
71
|
+
If the HTTP response is lost or you press Ctrl-C, the command prints the input ID and generation;
|
|
72
|
+
repeat the exact message with `--input-id <uuid> --generation <n>` to recover that request safely. Reusing an ID
|
|
72
73
|
does not replay an existing input. A **delivery unconfirmed** receipt means
|
|
73
74
|
the agent may already have received the instruction; deliberately resend
|
|
74
75
|
without `--input-id` only if you want to retry it as a new input.
|
|
@@ -97,15 +98,18 @@ this confirms admission or delivery, not task success.
|
|
|
97
98
|
|
|
98
99
|
## Renaming and labelling tasks
|
|
99
100
|
|
|
100
|
-
Change a task's title
|
|
101
|
+
Change a task's title, its metadata labels or its model, including while it runs:
|
|
101
102
|
|
|
102
103
|
```sh
|
|
103
104
|
brainbase task update <task-id> --title "Nightly smoke run" --metadata env=staging
|
|
104
105
|
brainbase task update <task-id> --unset-metadata env --json
|
|
106
|
+
brainbase task update <task-id> --model claude-sonnet-5-5
|
|
105
107
|
```
|
|
106
108
|
|
|
107
109
|
`--metadata` and `--unset-metadata` keep every label you do not name.
|
|
108
|
-
`--clear-metadata` removes them all, and `--clear-title` removes the title.
|
|
110
|
+
`--clear-metadata` removes them all, and `--clear-title` removes the title.
|
|
111
|
+
`--model` switches the model the task's next turn runs on; a turn already
|
|
112
|
+
running keeps its model. See
|
|
109
113
|
[the command reference](docs/reference/commands.mdx) for every flag.
|
|
110
114
|
|
|
111
115
|
## Benchmark management
|