@laburen/delta-cli 0.0.0-stage → 0.2.0-canary.11

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.
Files changed (160) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +33 -2
  3. package/dist/bin.d.ts +2 -0
  4. package/dist/bin.js +20 -0
  5. package/dist/bin.js.map +1 -0
  6. package/dist/commands/agent-checks.d.ts +5 -0
  7. package/dist/commands/agent-checks.js +69 -0
  8. package/dist/commands/agent-checks.js.map +1 -0
  9. package/dist/commands/agent-run/body.d.ts +22 -0
  10. package/dist/commands/agent-run/body.js +88 -0
  11. package/dist/commands/agent-run/body.js.map +1 -0
  12. package/dist/commands/agent-run/render.d.ts +50 -0
  13. package/dist/commands/agent-run/render.js +281 -0
  14. package/dist/commands/agent-run/render.js.map +1 -0
  15. package/dist/commands/agent-run.d.ts +10 -0
  16. package/dist/commands/agent-run.js +305 -0
  17. package/dist/commands/agent-run.js.map +1 -0
  18. package/dist/commands/agent-tools/add.d.ts +5 -0
  19. package/dist/commands/agent-tools/add.js +101 -0
  20. package/dist/commands/agent-tools/add.js.map +1 -0
  21. package/dist/commands/agent-tools/remove.d.ts +5 -0
  22. package/dist/commands/agent-tools/remove.js +126 -0
  23. package/dist/commands/agent-tools/remove.js.map +1 -0
  24. package/dist/commands/agent-tools/shared.d.ts +283 -0
  25. package/dist/commands/agent-tools/shared.js +107 -0
  26. package/dist/commands/agent-tools/shared.js.map +1 -0
  27. package/dist/commands/agent-tools.d.ts +5 -0
  28. package/dist/commands/agent-tools.js +11 -0
  29. package/dist/commands/agent-tools.js.map +1 -0
  30. package/dist/commands/auth.d.ts +14 -0
  31. package/dist/commands/auth.js +171 -0
  32. package/dist/commands/auth.js.map +1 -0
  33. package/dist/commands/completion.d.ts +4 -0
  34. package/dist/commands/completion.js +50 -0
  35. package/dist/commands/completion.js.map +1 -0
  36. package/dist/commands/config-sources.d.ts +22 -0
  37. package/dist/commands/config-sources.js +46 -0
  38. package/dist/commands/config-sources.js.map +1 -0
  39. package/dist/commands/config-wizard.d.ts +9 -0
  40. package/dist/commands/config-wizard.js +332 -0
  41. package/dist/commands/config-wizard.js.map +1 -0
  42. package/dist/commands/orgs.d.ts +11 -0
  43. package/dist/commands/orgs.js +193 -0
  44. package/dist/commands/orgs.js.map +1 -0
  45. package/dist/commands/skill-dir.d.ts +18 -0
  46. package/dist/commands/skill-dir.js +101 -0
  47. package/dist/commands/skill-dir.js.map +1 -0
  48. package/dist/commands/token-notice.d.ts +4 -0
  49. package/dist/commands/token-notice.js +13 -0
  50. package/dist/commands/token-notice.js.map +1 -0
  51. package/dist/commands/whoami.d.ts +8 -0
  52. package/dist/commands/whoami.js +38 -0
  53. package/dist/commands/whoami.js.map +1 -0
  54. package/dist/commands/wizards.d.ts +4 -0
  55. package/dist/commands/wizards.js +210 -0
  56. package/dist/commands/wizards.js.map +1 -0
  57. package/dist/completion/bash.d.ts +3 -0
  58. package/dist/completion/bash.js +60 -0
  59. package/dist/completion/bash.js.map +1 -0
  60. package/dist/completion/files.d.ts +35 -0
  61. package/dist/completion/files.js +178 -0
  62. package/dist/completion/files.js.map +1 -0
  63. package/dist/completion/powershell.d.ts +9 -0
  64. package/dist/completion/powershell.js +83 -0
  65. package/dist/completion/powershell.js.map +1 -0
  66. package/dist/completion/tree.d.ts +25 -0
  67. package/dist/completion/tree.js +53 -0
  68. package/dist/completion/tree.js.map +1 -0
  69. package/dist/completion/zsh.d.ts +3 -0
  70. package/dist/completion/zsh.js +76 -0
  71. package/dist/completion/zsh.js.map +1 -0
  72. package/dist/config/auth.d.ts +26 -0
  73. package/dist/config/auth.js +223 -0
  74. package/dist/config/auth.js.map +1 -0
  75. package/dist/config/link.d.ts +16 -0
  76. package/dist/config/link.js +93 -0
  77. package/dist/config/link.js.map +1 -0
  78. package/dist/config/paths.d.ts +3 -0
  79. package/dist/config/paths.js +20 -0
  80. package/dist/config/paths.js.map +1 -0
  81. package/dist/config/settings.d.ts +8 -0
  82. package/dist/config/settings.js +24 -0
  83. package/dist/config/settings.js.map +1 -0
  84. package/dist/confirm.d.ts +35 -0
  85. package/dist/confirm.js +51 -0
  86. package/dist/confirm.js.map +1 -0
  87. package/dist/context.d.ts +29 -0
  88. package/dist/context.js +16 -0
  89. package/dist/context.js.map +1 -0
  90. package/dist/errors.d.ts +56 -0
  91. package/dist/errors.js +452 -0
  92. package/dist/errors.js.map +1 -0
  93. package/dist/generated/commands.d.ts +49 -0
  94. package/dist/generated/commands.js +52 -0
  95. package/dist/generated/commands.js.map +1 -0
  96. package/dist/generated/schemas.d.ts +5 -0
  97. package/dist/generated/schemas.js +20 -0
  98. package/dist/generated/schemas.js.map +1 -0
  99. package/dist/invocation.d.ts +66 -0
  100. package/dist/invocation.js +343 -0
  101. package/dist/invocation.js.map +1 -0
  102. package/dist/mode.d.ts +17 -0
  103. package/dist/mode.js +22 -0
  104. package/dist/mode.js.map +1 -0
  105. package/dist/operations/call.d.ts +6 -0
  106. package/dist/operations/call.js +17 -0
  107. package/dist/operations/call.js.map +1 -0
  108. package/dist/operations/extensions.d.ts +46 -0
  109. package/dist/operations/extensions.js +29 -0
  110. package/dist/operations/extensions.js.map +1 -0
  111. package/dist/operations/json-input.d.ts +7 -0
  112. package/dist/operations/json-input.js +50 -0
  113. package/dist/operations/json-input.js.map +1 -0
  114. package/dist/operations/params.d.ts +17 -0
  115. package/dist/operations/params.js +106 -0
  116. package/dist/operations/params.js.map +1 -0
  117. package/dist/operations/register.d.ts +10 -0
  118. package/dist/operations/register.js +102 -0
  119. package/dist/operations/register.js.map +1 -0
  120. package/dist/operations/run-operation.d.ts +8 -0
  121. package/dist/operations/run-operation.js +148 -0
  122. package/dist/operations/run-operation.js.map +1 -0
  123. package/dist/operations/schema-flag.d.ts +8 -0
  124. package/dist/operations/schema-flag.js +12 -0
  125. package/dist/operations/schema-flag.js.map +1 -0
  126. package/dist/operations/skeleton.d.ts +16 -0
  127. package/dist/operations/skeleton.js +116 -0
  128. package/dist/operations/skeleton.js.map +1 -0
  129. package/dist/operations/tables.d.ts +7 -0
  130. package/dist/operations/tables.js +132 -0
  131. package/dist/operations/tables.js.map +1 -0
  132. package/dist/operations.d.ts +5 -0
  133. package/dist/operations.js +7 -0
  134. package/dist/operations.js.map +1 -0
  135. package/dist/output.d.ts +33 -0
  136. package/dist/output.js +452 -0
  137. package/dist/output.js.map +1 -0
  138. package/dist/pickers.d.ts +51 -0
  139. package/dist/pickers.js +283 -0
  140. package/dist/pickers.js.map +1 -0
  141. package/dist/program.d.ts +31 -0
  142. package/dist/program.js +260 -0
  143. package/dist/program.js.map +1 -0
  144. package/dist/prompter.d.ts +54 -0
  145. package/dist/prompter.js +129 -0
  146. package/dist/prompter.js.map +1 -0
  147. package/dist/session.d.ts +45 -0
  148. package/dist/session.js +178 -0
  149. package/dist/session.js.map +1 -0
  150. package/dist/stdout-policy.d.ts +4 -0
  151. package/dist/stdout-policy.js +11 -0
  152. package/dist/stdout-policy.js.map +1 -0
  153. package/dist/update-check.d.ts +4 -0
  154. package/dist/update-check.js +60 -0
  155. package/dist/update-check.js.map +1 -0
  156. package/docs/SKILL.md +187 -0
  157. package/docs/references/auth-and-organizations.md +72 -0
  158. package/docs/references/commands.md +247 -0
  159. package/docs/references/output-and-errors.md +105 -0
  160. package/package.json +39 -5
@@ -0,0 +1,105 @@
1
+ # Output and errors
2
+
3
+ ## stdout and stderr
4
+
5
+ - stdout: the data, and the error JSON (see below).
6
+ - stderr: notices, the login URL, the version notice, and errors for humans. `agents run` without `--json` writes all its errors to stderr (as JSON in non-interactive mode), including usage errors such as a missing `<agent_id>`, so stdout keeps only the text of the turn.
7
+ - `Warning: <message>` on stderr for each item of `warnings` in an API response, read from the top-level `warnings` and from a nested `version.warnings` (as in `agents create` and `agents update`) (also with `--json`, where stdout stays the untouched JSON). Without `--json`, the card on stdout does not repeat those `warnings`: each one is shown once, on stderr; use `--json` to read their other fields (such as `code`).
8
+
9
+ Without `--json`, lists print as a table and single items as `key: value` lines (an empty `changed_fields` shows as `changed_fields: []`; an empty `warnings` list and empty objects are hidden). Lists of agents, versions, skills and the like show a few columns and cut long text to the width of a terminal (the ID column is never cut, and piped output is not cut); `get` or `--json` shows every field. In a `get` card, nested objects are indented under their key; in a table cell they are one-line JSON. Lists of strings appear as `a,b` in a table cell; in a card they go one `- item` per line under their key, also with a single item, so a list never looks like a single value. `versions compare` prints one difference per line with one rule for every resource: a string longer than 120 characters, or a list of only text blocks (the prompt), shows its first 60 characters: `"<first 60 chars>…" (N chars)`; any other list or object is summarized as `<list, N items>` or `<object, N keys>` only when its JSON is longer than 120 characters, and a shorter one is printed whole (`[{"skill_id":"…","strategy":"pin"}] → […"latest"]`). When both values are objects and one of them is that long, the line names the top-level keys that changed instead (`tree: changed SKILL.md; added references/b.md; removed references/a.md`), up to 5 keys per group and then `(+N more)`. When both values are non-empty lists and one of them is that long, the line names the items that changed, were added or were removed (`tools: changed tool_b, tool_d; added tool_x`), with the same limit: each item is named by its `id` (or `skill_id`, `connection_id`, `name`, `type`) when every item has one and none repeats, and by its position otherwise (`changed [1]; added [2]`); same items in another order show as `same items, reordered`. Use `--json` for the full values. `--json` is never changed by any of this. Table columns follow the order in which keys appear, including columns that are `null` in every row. Control characters in values from the server (`\n`, `\t`, `ESC`...) are printed escaped (`\n`, `\x1b`), never raw: in tables, cards, errors, `next` lines and the labels of the questions. An empty list prints `No results.`
10
+
11
+ If stdout is closed early (for example `laburen agents list | head -2`), the CLI exits quietly. The exception is `agents run`: it keeps going and still writes the footer and the `continue:` line on stderr (a closed stderr also stops it quietly).
12
+
13
+ ## `--json`
14
+
15
+ Prints the API response as JSON on stdout, nothing else. When the response is empty it prints `null`. `login`, `logout`, `link`, `unlink` and `orgs switch` print `{ "status": "ok" }` (`link` and `orgs switch` add `organization_id`, `login` adds `api_url`). Their human messages still go to stderr.
16
+
17
+ `orgs list --json` returns an array of `{ id, name, role, current }`.
18
+
19
+ ## `--paginate`
20
+
21
+ List commands return one page by default (`--limit`, `--after-id`, `--before-id`). When there are more, stderr says `More results: use --paginate or --after-id <last_id>`. With `--paginate` the CLI fetches all pages. With `--json` it prints `{ "data": [ ... ] }`. `models list` always fetches all pages (with `--json` too, as one `{ "data": [ ... ] }`, no "More results" notice).
22
+
23
+ ## Errors
24
+
25
+ For humans (stderr):
26
+
27
+ ```
28
+ Error: <message>
29
+ - <field>: <message> (one line per issue, when the API sends issues)
30
+ - <name> (<id>) (one line per choice, when an id is missing)
31
+ code: <reason>
32
+ request_id: <id>
33
+ next: <command> (<when>)
34
+ ```
35
+
36
+ With `--json` or in non-interactive mode, the error goes to stdout as JSON:
37
+
38
+ ```json
39
+ {
40
+ "status": "error",
41
+ "reason": "login_required",
42
+ "message": "No saved credentials for https://dashboard.laburen.com/api/platform/v1.",
43
+ "next": [{ "command": "laburen login", "when": "to sign in and save credentials" }]
44
+ }
45
+ ```
46
+
47
+ - `reason`: the API `code` when the API failed, otherwise one of the CLI reasons below. `request_id` is only present for API errors (the key is omitted otherwise).
48
+ - `issues`: a validation error that names a field (`details.field`) has them too, as the API sends them: `[{ "field": "...", "message": "..." }]`. `field` is the exact place, for example `config.tools[3].url`; an unknown key gets one issue per key, with the key's name in `field` (`harness_type`).
49
+ - `choices`: only when an id is missing and the CLI cannot ask: up to 20 `[{ "id": "...", "name": "..." }]`, with one `next` per choice. The current one (the active version, the organization in use) also has `"current": true`.
50
+ - `details`: only when there are any: the API `details`, or for `network_error` the `cause` reported by the SDK.
51
+ - `next`: commands that fix the error, each with `command` and `when`. They are the real command you ran (path, ids and flags) with what is missing added, so you can run them as they are once the placeholders are filled in. A placeholder is a word in angle brackets: `<value>` is a value you type (a required flag that was missing, or a secret that was not copied), and `<id>`, `<version_id>` or `<agent_id>` is an id you get from a `list` or from the user. The value of a secret flag (`--token`, `-t`, `--refresh-token`, `--data`, `--headers`, `--config`, `--tool`, `--files`, `--value`, `--secret`, `--password`) is never copied, in any `next` or notice: it becomes `<value>` (for example `--headers <value>`), so fill it back in before running the command. In `--url` only the user and password and the values of the query and the fragment become `<value>` (`https://u:<value>@host/path?key=<value>#tok=<value>`); the rest stays so the command still points to the right server. When `npx` runs the CLI (`npx @laburen/delta-cli ...`), commands in `next`, and a `run laburen ...` inside `when`, start with `npx @laburen/delta-cli` instead of `laburen`. A `laburen` installed globally keeps `laburen` even when the program that runs it was started with npx. Every suggested command (in `next` and in notices) keeps the global flags you passed (`--org`, `--api-url`, `--global-config`, `--json`) unless it already has them, so it runs against the same API, folder and organization; a `--help` command does not get them, the `Created version <n> (not active)` notice leaves `--json` out (it only changes how this run printed), and the `next` that reruns a command without `--org` (after `organization_mismatch`) leaves `--org` out on purpose.
52
+
53
+ A usage error from the argument parser (`unknown option ...`) never repeats a flag value, secret or not: `--any-flag=x` is shown as `--any-flag=<value>`.
54
+
55
+ CLI reasons: `login_required`, `login_cancelled`, `cancelled`, `missing_arguments`, `invalid_arguments`, `missing_required`, `invalid_flag_value`, `config_required`, `agent_has_no_version`, `invalid_shell`, `invalid_link`, `invalid_token`, `organization_mismatch`, `organization_not_found`, `tool_not_found`, `confirmation_required`, `no_results`, `auth_lock_timeout`, `network_error`, `unexpected_error`.
56
+
57
+ - `login_required`: no saved session for this API URL, or the session expired. `next` keeps the `--api-url` and `--global-config` you used.
58
+ - `invalid_token`: `LABUREN_TOKEN` was rejected; `next` is `unset LABUREN_TOKEN`.
59
+ - `cancelled`: Ctrl-C, Esc or Ctrl-D at a question, or No at a confirmation (exit 1). Nothing was changed and there is no `next`.
60
+ - `login_cancelled`: Ctrl-C while `laburen login` waits for the approval in the browser (exit 1). It is a reason of its own, not `cancelled`: nothing was saved, and the next step is to run `laburen login` again.
61
+ - `confirmation_required`: a delete or revoke needs approval and the CLI cannot ask (exit 2). The JSON also has `"userActionRequired": true`; `next` is the same command with `--yes`. Ask the user and run it only if they approve; never add `--yes` on your own.
62
+ - `missing_arguments`: an id is missing. When the CLI could list them, the JSON has `"userActionRequired": true` and `choices`; ask the user which one and run its `next`. If the API rejects the list (no organization, no permission) you get that API error instead, with its `next`. Do not choose yourself. In a delete or revoke, those `next` have no `--yes`: running one asks for (or fails with) `confirmation_required`.
63
+ - `no_results`: an id was missing and there is nothing to pick from (exit 1); `next` creates one, with the required flags of the `create` as `<value>`.
64
+ - `missing_required`: lists every required option that is missing. A missing id in the same command shows up in `next` as a placeholder (`<agent_id>`).
65
+ - `config_required`: `agents create` got `skills`, `mcp_connections` or `activate` without `config` (exit 2). Nothing is created; `next` is your command plus `--config <value>`.
66
+ - `agent_has_no_version` (exit 1): `agents tools add` on an agent with no versions; there is no config to add the tool to. `next` is `agents versions create <agent_id> --config @config.json` (a file name to create; the CLI does not mask it as `<value>`).
67
+ - `invalid_link`: `.laburen/link.json` is broken, or `.laburen` exists and is not a folder (in that case no command falls back to the `link.json` of a parent folder).
68
+ - `auth_lock_timeout`: another `laburen` held the credentials lock too long; `next` is `rm "<lock file>"`.
69
+ - `network_error`: the API could not be reached (or did not answer in time). The network timeout is fixed: there is no flag or environment variable to change it. Each request waits 30 seconds per attempt; a GET, or a call that carries an `Idempotency-Key`, is retried up to 2 times. `agents run` waits up to 630 seconds (10.5 minutes) for the API to answer, and without `--json` it also fails if the live stream sends nothing for 45 seconds.
70
+
71
+ Other reasons you may meet (API codes):
72
+
73
+ - `invalid_skill`: the skill does not follow the format; `details.reason` is `forbidden_path` (only `SKILL.md` and `references/**`), `invalid_character`, `invalid_frontmatter`, `missing_skill_md` (no `SKILL.md` among the files), `name_mismatch` (frontmatter `name` differs from the skill name), `limit_exceeded` or `no_active_version`.
74
+ - `conversation_not_found`: the `memory.thread` does not exist or belongs to another organization or agent.
75
+ - `thread_resource_mismatch`: `memory.resource` is not the one that owns the `memory.thread`; send the same resource the thread started with.
76
+ - `ai_disabled_for_conversation`: a human took over the conversation, so the turn does not run. `next` is the same command without `--thread`: start a new conversation.
77
+ - `invalid_request`/`invalid_agent_config` on `config.knowledge.project_ids`: a project id does not exist in this organization; `next` is `laburen knowledge projects list`.
78
+ - An attachment that could not be downloaded says the HTTP status or network error and the host; the url must be public and downloadable without logging in.
79
+ - `mcp_server_unreachable` (400): the API could not connect to the MCP server when listing its tools; `details.connection_id` says which connection. Saving an agent `tools` filter with a MCP that is down does not fail with it: it saves and returns a `mcp_tools_unverified` warning. It is not retried automatically; check the URL and headers and run it again. It is raised only by the management API: a turn with a MCP that is down does not fail with it. `next` is `mcp connections versions list <connection_id>` (its HOST column shows where each version points).
80
+ - `resource_in_use`: a skill or MCP connection that agent versions still assign (or pin a version of); `details.agent_versions` lists them as `[{ agent_id, version_id, is_active }]` (no repeats), `details.agent_ids` the agents and `details.versions_count` how many versions. Versions are immutable: update the agent so the active version stops using it, delete the inactive versions that still assign it (never the active one), then retry (recipe in SKILL.md).
81
+ - `idempotency_key_in_progress`: the CLI only gets it on its own retry: the first attempt failed or took too long (a timeout), the CLI retried it with the same key, and the server is still processing that first request, which may finish and apply. The message says so. Do not rerun the command as it is: a rerun sends a new request (a new key) and can duplicate what the first one does. Wait, then check with `list`/`get` that it did not apply, and only then run it again. The `next` is that `list` (for a create or update); `agents run` has none, because the CLI cannot show a turn in progress.
82
+ - `model_provider_auth_failed`: the model provider rejected the platform's credentials, even after the platform tried its fallback models; not retryable and not caused by your request. If it persists, contact support.
83
+ - `internal_invariant_violation` (500): a bug on the server; keep the `request_id` and report it.
84
+ - In the SDK, an error that arrives inside the `agents.stream` stream carries its HTTP `status` and `shouldRetry`, like any `LaburenApiError`. The CLI error JSON has no HTTP status and no `retryable` (`agents run --json` uses `generate`, not the stream).
85
+ - `insufficient_permissions`: the token lacks a permission. They are independent (`query`, `read`, `write`, `admin`); deleting agents, skills and MCP connections needs `admin`.
86
+ - `invalid_shell` (CLI, exit 2): `laburen completion` got a shell it does not support; the message lists them.
87
+
88
+ Some API errors come with `next` too: `organization_access_denied` → `laburen orgs list` (without the bad `--org`); `insufficient_permissions` → `laburen whoami` (shows the permissions of the token you used); `idempotency_key_in_progress` → the `list` of the resource the command creates or edits, to check before running again (none for `agents run`); a model or reasoning level the API does not offer (`invalid_request`/`invalid_agent_config` on `model`, `config.model.id` or `reasoning`, with a message that says it is not offered) → `laburen models list`; a run where the version has the `thinking` tool and the model reasons (`invalid_request`, `model_settings.reasoning`) → the same command with `--reasoning off` (only if the model can turn it off) and `laburen agents versions list <agent_id>` (run a version without the tool with `--version-id`); `skill_name_taken` → `laburen skills list`; `mcp_connection_name_taken` → `laburen mcp connections list --search <name>` (the `--name` you passed); `resource_in_use` → with `details.agent_versions`, one `laburen agents versions delete <agent_id> <version_id>` per inactive version and one `agents versions get` per active one (never a delete of the active version); without it, one `laburen agents versions list <agent_id>` per id in `details.agent_ids`; `*_not_found` → the `list` of that resource (with the parent id filled in); `version_in_use` → `versions activate` of another version; a missing organization header (`invalid_request`) → `laburen orgs list` and the command you ran with `--org <id>`. Any other request the API rejects as invalid (`invalid_request_error`, such as `invalid_agent_config` or `invalid_request` with `issues`) without its own `next` gets the command you ran, with your ids and values (secrets as `<value>`), to fix the fields in `issues` and run again, plus `laburen <command> --schema` when the command has a request body (`--help` when it does not).
89
+
90
+ ## Exit codes
91
+
92
+ | Code | Meaning |
93
+ |---|---|
94
+ | `0` | ok (also `--help` and `--version`) |
95
+ | `1` | the API or the network failed, login or a question cancelled, a resource that does not exist (as in the API: `*_not_found` from the API, `tool_not_found`, `organization_not_found`), nothing to pick from (`no_results`), an agent with no version to add a tool to (`agent_has_no_version`) |
96
+ | `2` | wrong usage: missing argument, unknown command, invalid flag value (also an empty `--org`, reason `invalid_flag_value`), `--data` that is not a JSON object or a missing `@file`, a `--dir` with a file that is not UTF-8 text (no request is sent), organization mismatch, broken `link.json` |
97
+ | `130` | Ctrl+C during `agents run` (the turn keeps running on the server) |
98
+
99
+ ## Non-interactive mode
100
+
101
+ On when you pass `--non-interactive`, or when an AI agent runs the CLI and stdin is not a terminal. Questions are also off with `--json`, with `CI` set to any non-empty value (also `0`), or when stdin or stderr is not a terminal; then a missing id, a confirmation or a `create` field fails with its error instead of asking. `--no-non-interactive` (or `--non-interactive=false`) turns it off. Running `laburen` or a group such as `laburen orgs`, `laburen agents` or `laburen agents versions` without a subcommand prints its help on stderr and exits 2; an unknown subcommand (`laburen agents nope`) fails with `unknown command` and exits 2. In this mode the CLI asks no questions (a missing value fails with `next`), prints no colors and no version notice, and ignores the saved organization.
102
+
103
+ ## Colors and the version notice
104
+
105
+ Colors are off with `NO_COLOR`, `FORCE_COLOR=0`, `TERM=dumb`, `--no-color`, or in non-interactive mode. stdout and stderr are decided separately: tables are colored only when stdout is a terminal, and errors only when stderr is a terminal (so `2>file` never gets color codes). The CLI checks npm for a newer version once a day and tells you on stderr; never with `--json`, in non-interactive mode, or when `CI` is set.
package/package.json CHANGED
@@ -1,6 +1,40 @@
1
1
  {
2
- "name": "@laburen/delta-cli",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
2
+ "name": "@laburen/delta-cli",
3
+ "version": "0.2.0-canary.11",
4
+ "description": "Laburen CLI to manage agents from the terminal",
5
+ "type": "module",
6
+ "license": "MIT",
7
+ "bin": {
8
+ "laburen": "./dist/bin.js"
9
+ },
10
+ "engines": {
11
+ "node": ">=22"
12
+ },
13
+ "files": [
14
+ "dist",
15
+ "docs",
16
+ "README.md",
17
+ "LICENSE"
18
+ ],
19
+ "scripts": {
20
+ "prepack": "npm run build",
21
+ "build": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.build.json && node -e \"require('node:fs').chmodSync('dist/bin.js', 0o755)\"",
22
+ "generate": "node scripts/generate-commands.mjs",
23
+ "check:generated": "npm run generate && node scripts/check-generated.mjs",
24
+ "typecheck": "tsc --noEmit",
25
+ "version:check": "node scripts/check-version.mjs",
26
+ "test": "vitest run"
27
+ },
28
+ "dependencies": {
29
+ "@clack/prompts": "1.8.1",
30
+ "@laburen/delta-sdk": "1.5.0-canary.11",
31
+ "@vercel/detect-agent": "1.2.7",
32
+ "commander": "14.0.3",
33
+ "picocolors": "1.1.1"
34
+ },
35
+ "devDependencies": {
36
+ "@types/node": "^22.0.0",
37
+ "typescript": "^5.9.3",
38
+ "vitest": "~3.2.0"
39
+ }
40
+ }