@koda-sl/baker-cli 0.121.0-dev.4a71225ab → 0.121.0-dev.6fedecad2
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 +0 -21
- package/dist/cli.js +810 -1020
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2502,27 +2502,6 @@ Rules:
|
|
|
2502
2502
|
|
|
2503
2503
|
---
|
|
2504
2504
|
|
|
2505
|
-
### Marketing Tags (`baker tags`)
|
|
2506
|
-
|
|
2507
|
-
Read the client's marketing/analytics tags (Meta pixel, GA4, Google Ads, GTM, Clarity, Hotjar, PostHog, …) — production tags overlaid with the changes staged in this chat.
|
|
2508
|
-
|
|
2509
|
-
**The CLI is read-only.** Every tag change (create, edit, delete) goes through the `request_tag_input` tool (`baker_ui` MCP server): the agent proposes one or more changes — each becomes a tab in one blocking approval form — pre-filling the non-secret fields it knows; the user reviews, edits, fills secret fields, and approves or skips each tab. Approved changes stage on the chat and apply when the chat is published; discarding the chat drops them.
|
|
2510
|
-
|
|
2511
|
-
`BAKER_CHAT_ID` must be set.
|
|
2512
|
-
|
|
2513
|
-
```bash
|
|
2514
|
-
baker tags list # effective view: production + staged, with secret status
|
|
2515
|
-
baker tags draft # review the staged changes awaiting publish
|
|
2516
|
-
```
|
|
2517
|
-
|
|
2518
|
-
Notes:
|
|
2519
|
-
|
|
2520
|
-
- **Secrets never travel through this CLI or the chat.** Secret fields (`accessToken`, `apiSecret`, `authorizationToken`, `apiKey`, `conversionToken`, `oauthProviderId`) are entered only in the dashboard's secure tag form and flow straight into the staged draft; tool responses only ever name which secret fields are set/pending.
|
|
2521
|
-
- Staged creates get a server-generated `tag_temp_*` ref (returned in the tool result and printed by `list`). Use it (or a real tag id) as flow side-effect `tagIds` — the published tag keeps resolving under the temp ref.
|
|
2522
|
-
- Proposing a delete on a `tag_temp_*` ref drops the staged create instead.
|
|
2523
|
-
- Single-instance types (`code`, `posthog`, `datafast`) reject a second instance against the chat's effective view.
|
|
2524
|
-
- Conflicts at publish (tag deleted in the dashboard, config invalid) skip the op with a recorded reason — they never block the publish.
|
|
2525
|
-
|
|
2526
2505
|
### Action Items (`baker actions`)
|
|
2527
2506
|
|
|
2528
2507
|
Manage action items for the current chat. Most write operations stage on the chat's draft and apply atomically when the chat is published. Claim/release run live so other chats can see who's working on what.
|