@braid-cloud/cli 0.1.10 → 0.1.13

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 CHANGED
@@ -199,6 +199,37 @@ braid mcp --remove --tool claude-code # Remove braid MCP entry
199
199
  | `-y, --yes` | Skip confirmation prompts |
200
200
  | `-s, --server <url>` | Set `BRAID_MCP_URL` (full MCP endpoint URL, e.g. `https://custom.braid.cloud/api/mcp`) |
201
201
 
202
+ ### `braid workflows`
203
+
204
+ Manage local workflow execution lifecycle state (CLI-first contract used by MCP passthrough tools).
205
+
206
+ ```bash
207
+ # List control flows available to your token context
208
+ braid workflows list --json
209
+
210
+ # Start execution tracking for a session
211
+ braid workflows start --session-id cli_sess_123 --flow-id flow_123 --current-step-label input --json
212
+
213
+ # Update progress
214
+ braid workflows progress --execution-id exec_123 --current-node-id node_2 --current-step-label prompt --json
215
+
216
+ # Read active run
217
+ braid workflows active --session-id cli_sess_123 --json
218
+
219
+ # Mark terminal states
220
+ braid workflows complete --execution-id exec_123 --json
221
+ braid workflows fail --execution-id exec_123 --error-message "Node timeout" --json
222
+ braid workflows cancel --execution-id exec_123 --json
223
+ ```
224
+
225
+ Notes:
226
+
227
+ - These commands track execution state for local/MCP workflows (not cloud execution runtime).
228
+ - `--metadata` accepts JSON for `start` and `progress`.
229
+ - `active` can be used to recover context after long model turns.
230
+
231
+ Reference: `docs/workflows/local-execution-session-state.md`.
232
+
202
233
  ## Configuration
203
234
 
204
235
  ### Token Resolution