@eigenpal/cli 0.4.10 → 0.4.12

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/CHANGELOG.md CHANGED
@@ -34,6 +34,7 @@
34
34
 
35
35
  ### Minor Changes
36
36
 
37
+ - c15ce88: Add the `eigenpal agent` command tree for managing agents, triggers, datasets, executions, experiments, and sessions from the terminal.
37
38
  - c82a215: `eigenpal auth login` now shows an interactive server picker when no `--base-url` flag or `EIGENPAL_BASE_URL` env is set:
38
39
  - **Cloud** (`https://studio.eigenpal.com`) is the default highlighted option.
39
40
  - Any on-prem URLs already in your credentials file are surfaced as separate options labelled with the profile names that use them — re-login against an existing on-prem deployment without retyping the URL.
@@ -252,6 +253,36 @@ actual) { ... }` declaration around your statements. Parameter order is
252
253
  Document the CLI exit-code contract (0 = success, 1 = runtime error,
253
254
  2 = misuse / recoverable failure) in `packages/cli/CLAUDE.md`.
254
255
 
256
+ - 4b1f81c: `transform.script` now accepts a full function declaration via
257
+ `with.function:`, mirroring the custom-script evaluator. Parameter
258
+ names and order must equal `Object.keys(inputs)`:
259
+
260
+ ```yaml
261
+ - type: transform.script
262
+ with:
263
+ inputs:
264
+ items: '{{ steps.x.output }}'
265
+ taxRate: '{{ input.rate }}'
266
+ function: |
267
+ function script(items, taxRate) {
268
+ return items.length * taxRate;
269
+ }
270
+ ```
271
+
272
+ Authoring is now Monaco-backed in the dashboard, with input keys
273
+ surfaced as typed declarations so `items.` autocompletes against the
274
+ upstream step's output schema.
275
+
276
+ The legacy `with.code:` shape (a bare statement body, with input keys
277
+ leaking in as globals) still loads — the worker auto-wraps it via
278
+ `wrapBodyAsScriptFunction` at handler entry, and the dashboard
279
+ migrates `code:` to `function:` on the next save. New workflows
280
+ should use `function:`. The schema rejects:
281
+ - function names other than `script`
282
+ - parameter lists that don't match `Object.keys(inputs)` in order
283
+ - `async` / `import()` / `require()` (sandbox-incompatible)
284
+ - bodies with no `return` or `throw`
285
+
255
286
  - 3da0612: CLI: cleaner workflow command tree + matching `--json` shape.
256
287
 
257
288
  **Tree restructure** — the `workflow definition` namespace is gone. Its three verbs are core operations on the workflow itself, so they move up one level:
@@ -275,6 +306,7 @@ actual) { ... }` declaration around your statements. Parameter order is
275
306
 
276
307
  ### Patch Changes
277
308
 
309
+ - c15ce88: Rename agent API calls to `/v1/agents` and scope execution helpers under their owning workflow or agent.
278
310
  - 71361fd: `auth login`: simplified flow. Removed the dead localhost-callback server (the
279
311
  dashboard never POSTed to it — every login fell through to copy-paste anyway).
280
312
  The browser now opens to `/developers/api-keys?from=cli` with a clearer prompt