@koda-sl/baker-cli 0.367.0-dev.a5b15aee3 → 0.367.0-dev.e10535428
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 +3 -1
- package/dist/cli.js +2104 -2023
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -3292,7 +3292,9 @@ baker winning-ads patterns --winners a_1,a_2,a_3 --duds a_9,a_8 --top-n 10 --out
|
|
|
3292
3292
|
A Scheduled agent is a **trigger** and a **prompt**. When the trigger fires, a Session opens with that prompt and does the job — there is no Task in between. `create`, `update`, and `delete` stage draft ops on `BAKER_CHAT_ID` and apply when the chat is published. `unstage` takes back what this chat staged on one item before Publish (`--index <n>` for one change only, by its index in `list` → `draft.ops`). `list` and `get` include draft state when `BAKER_CHAT_ID` is set; `get` on a published item also returns `runsAs` — who each run acts as and which tools it loads. `run` fires a published item immediately and does not require a chat id. Publishing every run unreviewed is switched on by the user on the item, never through the CLI: `--auto-publish` is refused with an `ask_user` fix.
|
|
3293
3293
|
|
|
3294
3294
|
```bash
|
|
3295
|
-
baker scheduled-agents triggers # every trigger
|
|
3295
|
+
baker scheduled-agents triggers # every trigger kind, by group, compact
|
|
3296
|
+
baker scheduled-agents triggers --trigger experiment.decided # one kind (or a family: --trigger experiment) in full, with its payload fields
|
|
3297
|
+
baker scheduled-agents triggers --group tasks # one group in full; --full for the whole catalog
|
|
3296
3298
|
baker scheduled-agents list
|
|
3297
3299
|
baker scheduled-agents get <id-or-temp_agent_id>
|
|
3298
3300
|
|