@laburen/delta-cli 0.0.0-stage → 0.2.0-canary.9
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/LICENSE +21 -0
- package/README.md +33 -2
- package/dist/bin.d.ts +2 -0
- package/dist/bin.js +16 -0
- package/dist/bin.js.map +1 -0
- package/dist/commands/agent-checks.d.ts +3 -0
- package/dist/commands/agent-checks.js +36 -0
- package/dist/commands/agent-checks.js.map +1 -0
- package/dist/commands/agent-run/body.d.ts +22 -0
- package/dist/commands/agent-run/body.js +88 -0
- package/dist/commands/agent-run/body.js.map +1 -0
- package/dist/commands/agent-run/render.d.ts +40 -0
- package/dist/commands/agent-run/render.js +271 -0
- package/dist/commands/agent-run/render.js.map +1 -0
- package/dist/commands/agent-run.d.ts +10 -0
- package/dist/commands/agent-run.js +205 -0
- package/dist/commands/agent-run.js.map +1 -0
- package/dist/commands/agent-tools/add.d.ts +5 -0
- package/dist/commands/agent-tools/add.js +80 -0
- package/dist/commands/agent-tools/add.js.map +1 -0
- package/dist/commands/agent-tools/remove.d.ts +5 -0
- package/dist/commands/agent-tools/remove.js +126 -0
- package/dist/commands/agent-tools/remove.js.map +1 -0
- package/dist/commands/agent-tools/shared.d.ts +276 -0
- package/dist/commands/agent-tools/shared.js +94 -0
- package/dist/commands/agent-tools/shared.js.map +1 -0
- package/dist/commands/agent-tools.d.ts +5 -0
- package/dist/commands/agent-tools.js +11 -0
- package/dist/commands/agent-tools.js.map +1 -0
- package/dist/commands/auth.d.ts +14 -0
- package/dist/commands/auth.js +161 -0
- package/dist/commands/auth.js.map +1 -0
- package/dist/commands/completion.d.ts +4 -0
- package/dist/commands/completion.js +50 -0
- package/dist/commands/completion.js.map +1 -0
- package/dist/commands/config-sources.d.ts +22 -0
- package/dist/commands/config-sources.js +46 -0
- package/dist/commands/config-sources.js.map +1 -0
- package/dist/commands/config-wizard.d.ts +9 -0
- package/dist/commands/config-wizard.js +332 -0
- package/dist/commands/config-wizard.js.map +1 -0
- package/dist/commands/orgs.d.ts +11 -0
- package/dist/commands/orgs.js +179 -0
- package/dist/commands/orgs.js.map +1 -0
- package/dist/commands/skill-dir.d.ts +18 -0
- package/dist/commands/skill-dir.js +97 -0
- package/dist/commands/skill-dir.js.map +1 -0
- package/dist/commands/token-notice.d.ts +4 -0
- package/dist/commands/token-notice.js +13 -0
- package/dist/commands/token-notice.js.map +1 -0
- package/dist/commands/whoami.d.ts +8 -0
- package/dist/commands/whoami.js +38 -0
- package/dist/commands/whoami.js.map +1 -0
- package/dist/commands/wizards.d.ts +4 -0
- package/dist/commands/wizards.js +210 -0
- package/dist/commands/wizards.js.map +1 -0
- package/dist/completion/bash.d.ts +3 -0
- package/dist/completion/bash.js +60 -0
- package/dist/completion/bash.js.map +1 -0
- package/dist/completion/files.d.ts +33 -0
- package/dist/completion/files.js +171 -0
- package/dist/completion/files.js.map +1 -0
- package/dist/completion/powershell.d.ts +9 -0
- package/dist/completion/powershell.js +83 -0
- package/dist/completion/powershell.js.map +1 -0
- package/dist/completion/tree.d.ts +25 -0
- package/dist/completion/tree.js +53 -0
- package/dist/completion/tree.js.map +1 -0
- package/dist/completion/zsh.d.ts +3 -0
- package/dist/completion/zsh.js +76 -0
- package/dist/completion/zsh.js.map +1 -0
- package/dist/config/auth.d.ts +26 -0
- package/dist/config/auth.js +223 -0
- package/dist/config/auth.js.map +1 -0
- package/dist/config/link.d.ts +16 -0
- package/dist/config/link.js +74 -0
- package/dist/config/link.js.map +1 -0
- package/dist/config/paths.d.ts +3 -0
- package/dist/config/paths.js +20 -0
- package/dist/config/paths.js.map +1 -0
- package/dist/config/settings.d.ts +8 -0
- package/dist/config/settings.js +24 -0
- package/dist/config/settings.js.map +1 -0
- package/dist/confirm.d.ts +35 -0
- package/dist/confirm.js +51 -0
- package/dist/confirm.js.map +1 -0
- package/dist/context.d.ts +27 -0
- package/dist/context.js +15 -0
- package/dist/context.js.map +1 -0
- package/dist/errors.d.ts +54 -0
- package/dist/errors.js +184 -0
- package/dist/errors.js.map +1 -0
- package/dist/generated/commands.d.ts +47 -0
- package/dist/generated/commands.js +52 -0
- package/dist/generated/commands.js.map +1 -0
- package/dist/generated/schemas.d.ts +5 -0
- package/dist/generated/schemas.js +18 -0
- package/dist/generated/schemas.js.map +1 -0
- package/dist/invocation.d.ts +64 -0
- package/dist/invocation.js +325 -0
- package/dist/invocation.js.map +1 -0
- package/dist/mode.d.ts +17 -0
- package/dist/mode.js +22 -0
- package/dist/mode.js.map +1 -0
- package/dist/operations/call.d.ts +6 -0
- package/dist/operations/call.js +14 -0
- package/dist/operations/call.js.map +1 -0
- package/dist/operations/extensions.d.ts +46 -0
- package/dist/operations/extensions.js +29 -0
- package/dist/operations/extensions.js.map +1 -0
- package/dist/operations/json-input.d.ts +7 -0
- package/dist/operations/json-input.js +50 -0
- package/dist/operations/json-input.js.map +1 -0
- package/dist/operations/params.d.ts +17 -0
- package/dist/operations/params.js +95 -0
- package/dist/operations/params.js.map +1 -0
- package/dist/operations/register.d.ts +10 -0
- package/dist/operations/register.js +102 -0
- package/dist/operations/register.js.map +1 -0
- package/dist/operations/run-operation.d.ts +8 -0
- package/dist/operations/run-operation.js +146 -0
- package/dist/operations/run-operation.js.map +1 -0
- package/dist/operations/schema-flag.d.ts +8 -0
- package/dist/operations/schema-flag.js +12 -0
- package/dist/operations/schema-flag.js.map +1 -0
- package/dist/operations/skeleton.d.ts +16 -0
- package/dist/operations/skeleton.js +116 -0
- package/dist/operations/skeleton.js.map +1 -0
- package/dist/operations/tables.d.ts +3 -0
- package/dist/operations/tables.js +52 -0
- package/dist/operations/tables.js.map +1 -0
- package/dist/operations.d.ts +5 -0
- package/dist/operations.js +7 -0
- package/dist/operations.js.map +1 -0
- package/dist/output.d.ts +22 -0
- package/dist/output.js +169 -0
- package/dist/output.js.map +1 -0
- package/dist/pickers.d.ts +51 -0
- package/dist/pickers.js +277 -0
- package/dist/pickers.js.map +1 -0
- package/dist/program.d.ts +31 -0
- package/dist/program.js +251 -0
- package/dist/program.js.map +1 -0
- package/dist/prompter.d.ts +54 -0
- package/dist/prompter.js +129 -0
- package/dist/prompter.js.map +1 -0
- package/dist/session.d.ts +45 -0
- package/dist/session.js +170 -0
- package/dist/session.js.map +1 -0
- package/dist/update-check.d.ts +4 -0
- package/dist/update-check.js +60 -0
- package/dist/update-check.js.map +1 -0
- package/docs/SKILL.md +108 -0
- package/docs/references/auth-and-organizations.md +72 -0
- package/docs/references/commands.md +186 -0
- package/docs/references/output-and-errors.md +87 -0
- package/package.json +39 -5
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
# Auth and organizations
|
|
2
|
+
|
|
3
|
+
## Login
|
|
4
|
+
|
|
5
|
+
```sh
|
|
6
|
+
laburen login
|
|
7
|
+
```
|
|
8
|
+
|
|
9
|
+
Prints a URL and a confirmation code on stderr, tries to open the browser (it does not when `CI` is set), and waits for the person to approve. If you are an AI agent in non-interactive mode, it always adds "Please ask the user to visit the URL above and approve the login." (opening the browser does not prove anyone can see it). Show the URL to the user. Ctrl-C cancels (exit 1).
|
|
10
|
+
|
|
11
|
+
On success it saves `auth.json` and prints "You are now signed in." Network errors while waiting do not cancel the login.
|
|
12
|
+
|
|
13
|
+
`laburen logout` revokes the saved tokens (both at once, waiting at most 5 seconds) and deletes `auth.json`. If the server does not answer, it still deletes the file.
|
|
14
|
+
|
|
15
|
+
## Where credentials live
|
|
16
|
+
|
|
17
|
+
`auth.json` (`token`, `refresh_token`, `expires_at`, `api_url`; mode `600`, folder `700`) and `config.json` (the saved organization) are in:
|
|
18
|
+
|
|
19
|
+
- Linux: `$XDG_DATA_HOME/laburen` or `~/.local/share/laburen`
|
|
20
|
+
- macOS: `~/Library/Application Support/laburen`
|
|
21
|
+
- Windows: `%APPDATA%\laburen`
|
|
22
|
+
|
|
23
|
+
Change the folder with `--global-config <dir>` or `LABUREN_CONFIG_DIR`. Different folders are separate sessions. The flag wins over the variable. An empty `HOME`, `XDG_DATA_HOME` or `APPDATA` counts as not set.
|
|
24
|
+
|
|
25
|
+
The token renews itself when it is about to expire. Parallel commands do not spend the refresh twice. If the API rejects the saved token because another command renewed it in the meantime, the CLI notices that `auth.json` changed and retries once with the new token (also the list it reads to offer `choices` when it cannot ask); ids already picked are not asked again. While a command waits for another one that is renewing, it says so on stderr after one second. A lock left by a process that no longer exists on this machine is taken right away (the lock records host, pid and a random id). A lock written from another host (a config folder shared over the network or mounted into a container) is only taken once it is older than 60 seconds. If another command holds the renewal lock for more than 70 seconds the CLI fails with `auth_lock_timeout`; `next` gives the lock file to delete if no other `laburen` is running. Known limits: an owner that is still alive but holds the lock for more than 60 seconds (for example a suspended laptop) can lose it to another command; and when a lock is taken by mistake (its owner released it and a new one appeared just then), the CLI puts it back with a rename followed by a link, so for an instant the lock file does not exist and a third command could take it. Only a rejected refresh token (`invalid_grant`, `invalid_token` or `expired_token`) asks you to log in again; a server error leaves your credentials untouched. A broken or half-written `auth.json` counts as "not signed in" (`login_required`).
|
|
26
|
+
|
|
27
|
+
## `LABUREN_TOKEN`
|
|
28
|
+
|
|
29
|
+
With `LABUREN_TOKEN` set, the CLI uses it as the token and does not read or write any credential file. `laburen login` still works but warns that the variable overrides saved credentials; `laburen logout` does nothing and tells you to unset the variable. If the API rejects the token, the error has reason `invalid_token` and `next` is `unset LABUREN_TOKEN` (logging in would not help, the variable wins).
|
|
30
|
+
|
|
31
|
+
## API URL
|
|
32
|
+
|
|
33
|
+
`--api-url`, then `LABUREN_API_URL`, then `https://dashboard.laburen.com/api/platform/v1`.
|
|
34
|
+
|
|
35
|
+
Saved credentials are bound to the URL they were created for. If the current URL is different, the CLI does not send the token and fails with `login_required`. Log in again for that URL: the `next` login command already carries `--api-url` (and `--global-config` if you used one). A trailing `/` in the URL is ignored. `LABUREN_TOKEN` is sent to whatever URL is configured.
|
|
36
|
+
|
|
37
|
+
## Which organization is used
|
|
38
|
+
|
|
39
|
+
First match wins:
|
|
40
|
+
|
|
41
|
+
1. `--org <id>`
|
|
42
|
+
2. `LABUREN_ORG`
|
|
43
|
+
3. `.laburen/link.json`, found in the current folder or any parent
|
|
44
|
+
4. the organization saved with `laburen orgs switch`
|
|
45
|
+
|
|
46
|
+
If `--org` or `LABUREN_ORG` differs from `link.json`, the command fails with `organization_mismatch` (exit 2). For `LABUREN_ORG`, `next` is `unset LABUREN_ORG` or `laburen link --org <that id>`; for `--org`, the same command without `--org` or `laburen link --org <that id>`. An empty `--org` fails with exit 2.
|
|
47
|
+
|
|
48
|
+
In non-interactive mode (and in any script or CI), set the organization with `--org <id>` or `LABUREN_ORG=<id>`: `laburen orgs switch <id>` saves it but the saved one is ignored there.
|
|
49
|
+
|
|
50
|
+
In non-interactive mode, the saved organization (4) is ignored. If 1 to 3 give nothing, the request goes without an organization header and the API decides: a token that belongs to one organization needs none; a token for all organizations fails with `invalid_request`, and the error's `next` says to pass `--org <id>`.
|
|
51
|
+
|
|
52
|
+
`laburen orgs list` and `laburen me organizations list` never send an organization header. They and `laburen orgs switch` keep working with a broken `link.json` or a mismatch: they only use the organization to mark the current one. The current one is the organization resolved by the rules above or, if there is none, the saved one; in non-interactive mode the saved one is also marked, only as information (requests still do not send it).
|
|
53
|
+
|
|
54
|
+
`laburen orgs switch` without an id asks you to pick one from a list (with search when there are more than 15); the current one is preselected and marked `(current)`. If you only have one organization it is picked for you and named on stderr. Ctrl-C, Esc or Ctrl-D cancels (`cancelled`, exit 1). It only asks when stdin and stderr are terminals and there is no `--non-interactive`, `--json` or `CI`; otherwise it fails with `missing_arguments` (exit 2) with `choices` (the current one with `current: true`) and one `next` per organization; ask the user which one. In non-interactive mode it saves the organization and says on stderr `Saved <name> (<id>). Non-interactive runs ignore the saved organization: use --org <id> or laburen link --org <id>.` (no "Now using": that mode does not send it).
|
|
55
|
+
|
|
56
|
+
## `link.json`
|
|
57
|
+
|
|
58
|
+
`laburen link --org <id>` writes `.laburen/link.json` with `{ "organization_id": "..." }`. It checks you are a member first (`organization_not_found` otherwise). Without `--org` it uses the organization already resolved by the rules above (a healthy `link.json` in the folder wins over the saved organization; a broken one fails with `invalid_link`). With `--org` the existing file is replaced without being read; if the `link.json` the CLI would use is broken and lives in a parent folder, that one is rewritten (not a new one in the current folder), and stderr prints its path. The file holds only the id, so commit it: whoever clones the repo works against that organization. `laburen unlink` deletes the `link.json` the CLI would use (the one in the current folder or the nearest parent), and the `.laburen` folder if it is left empty, and prints its path; with none it prints "No linked folder found." and exits 0. A `link.json` that exists but is not valid fails with `invalid_link` (exit 2) instead of being skipped; `laburen link --org <id>` rewrites it and `laburen unlink` removes it. If `.laburen` is a file, `laburen link` fails with `invalid_link` (exit 2) and `next` says which file to remove.
|
|
59
|
+
|
|
60
|
+
## Test against a local dashboard
|
|
61
|
+
|
|
62
|
+
From the repo root, without publishing:
|
|
63
|
+
|
|
64
|
+
```sh
|
|
65
|
+
npm run build -w @laburen/delta-sdk # the CLI imports the SDK build; or build the whole workspace: npm run build
|
|
66
|
+
npm run build -w @laburen/delta-cli
|
|
67
|
+
npm link -w @laburen/delta-cli # or: cd packages/delta-cli && npm link
|
|
68
|
+
LABUREN_API_URL=http://localhost:3000/api/platform/v1 laburen login
|
|
69
|
+
LABUREN_API_URL=http://localhost:3000/api/platform/v1 laburen agents list
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
The approval link comes from the server, so with the local dashboard it points to `localhost:3000/device`. To keep local and production sessions apart, add `LABUREN_CONFIG_DIR=/tmp/laburen-local` (or `--global-config`).
|
|
@@ -0,0 +1,186 @@
|
|
|
1
|
+
# Commands
|
|
2
|
+
|
|
3
|
+
Every command accepts the global flags `--json`, `--org <id>`, `--api-url <url>`, `--global-config <dir>`, `--non-interactive`, `--no-non-interactive` and `--no-color`. Commands that create or edit also accept `--data <json|@file|->` with the whole body; individual flags override `--data`. JSON flags take a JSON string or `@file`.
|
|
4
|
+
|
|
5
|
+
## Confirmation before deleting
|
|
6
|
+
|
|
7
|
+
Every `delete`, `tokens revoke` and `agents tools remove` asks before it changes anything: `Delete agent <id>?`, `Revoke token <id>?`, `Remove tool <id> of agent <id>?`. `agents tools remove` first reads the latest version, so a tool that does not exist fails with `tool_not_found` without asking; that read needs a session, so without one it fails with `login_required` before asking or failing with `confirmation_required`. The default answer is No; answering No (or Ctrl-C, Esc, Ctrl-D) cancels with `cancelled` (exit 1) and changes nothing. `--yes` (`-y`) skips the question, except when the id was picked from a list (see below): then the CLI always asks. `logout` and `unlink` do not ask.
|
|
8
|
+
|
|
9
|
+
If the CLI cannot ask (`--non-interactive`, `--json`, `CI`, or stdin or stderr is not a terminal) and there is no `--yes`, it fails with `confirmation_required` (exit 2). The error has `userActionRequired: true`, and `next` is the command you ran plus `--yes`, with `when` like `Only after the user approves deleting agent <id>` (`revoking token <id>`, `removing tool <id> of agent <id>`). **If you are an AI agent: ask the user first; run the `next` command only after they say yes.** Secrets are not copied into that command: the value of `--token`, `-t`, `--refresh-token`, `--data`, `--headers`, `--config`, `--tool`, `--files`, `--value`, `--secret` and `--password` becomes `<value>` (for example `--data <value>`), also when the value starts with `-` (`--data -`) or is glued to `-t` (`-tVALUE`); fill it back in before running it. In `--url` only the user and password and the values of the query and the fragment become `<value>`.
|
|
10
|
+
|
|
11
|
+
## Picking a missing id
|
|
12
|
+
|
|
13
|
+
The ids in the commands below are optional, also in `agents tools add` and `agents tools remove`. If one is missing and the CLI can ask (a terminal, no `--json`, no `--non-interactive`, no `CI`), it lists the first 100 items and asks you to pick one: the name is the label, the id is shown next to it (an item without a name shows only its id), and the active version is preselected and marked `(current)`. Versions are shown as `v<number> · <date>`. Several missing ids are asked in order: `laburen agents versions activate` asks for the agent and then for the version.
|
|
14
|
+
|
|
15
|
+
- Revoked and expired tokens are left out of the list (and of `choices`). The token of your own CLI session is not marked: the API does not say which one it is. Two items with the same name show the id in the label too (`ci (tok_1)`).
|
|
16
|
+
- In a delete, the active version is still marked `(current)` but the first one that is not active is preselected (the active one cannot be deleted).
|
|
17
|
+
- One item: it is picked for you and stderr says which one. Delete, revoke and remove still ask, even with one item.
|
|
18
|
+
- No items: fails with `no_results` (exit 1) and `next` is the command that creates one, with its required flags as `<value>` (`laburen mcp connections versions create <connection_id> --url <value>`).
|
|
19
|
+
- More than 100: stderr says so and shows the command you ran with `<id>` placeholders; pass the id to use one that is not in the list.
|
|
20
|
+
- `agents versions compare` (and the skills and MCP connections ones) without `--from` or `--to` always asks for the missing versions, even with only two; the second list leaves out the first one. With fewer than two versions it fails with `no_results`.
|
|
21
|
+
|
|
22
|
+
If the CLI cannot ask, a missing id fails with `missing_arguments` (exit 2), `userActionRequired: true` and `choices` with up to 20 `{ id, name }` (the active version also has `current: true`), plus one `next` per choice: the command you ran with that id (secret values as `<value>`), `when` "Ask the user which one; do not choose yourself". In delete, revoke and remove those commands drop `--yes`, so choosing one still needs the user's approval of the delete. **If you are an AI agent: ask the user which one; never pick it yourself.** If you are not logged in, the error is `login_required` with its `next`. If the list cannot be fetched for another reason, it is the plain `missing_arguments` error. A missing id is checked after the flags: if a required flag is missing too, the error is `missing_required` and its `next` has the id as a placeholder (`laburen agents versions compare <agent_id> --from v1 --to <value>`).
|
|
23
|
+
|
|
24
|
+
## Questions in create
|
|
25
|
+
|
|
26
|
+
If the CLI can ask (same rules as above), these `create` commands ask only for what did not come by flag or `--data`. A flag never turns the questions off: `--name` skips the name question and the rest are still asked. A required field with a single possible value (`harness_type: mastra`) is filled in without asking, also when the CLI cannot ask. `agents create` and `agents versions create` also ask the whole `config` (see below); other JSON fields (`files`...) are not asked: if one is required and missing, it fails with `missing_required` as usual. Ctrl-C, Esc or Ctrl-D cancels with `cancelled` (exit 1) and nothing is created. If the CLI cannot ask, missing required fields fail with `missing_required` (exit 2). With `--data -` stdin is used for the body, so nothing is asked in that run: missing fields fail with `missing_required`.
|
|
27
|
+
|
|
28
|
+
| Command | Question | Flag that replaces it |
|
|
29
|
+
|---|---|---|
|
|
30
|
+
| `agents create` | Agent name (text) | `--name` |
|
|
31
|
+
| | Configure the first version now? (default Yes; not asked if `--config`, `--skills`, `--mcp-connections` or `--activate` came by flag or `--data`) | `--config` |
|
|
32
|
+
| | The config: model (from `models list`), then the optional fields you choose to set, down to each tool; headers of http tools are not asked | `--config` |
|
|
33
|
+
| | Skills for the agent (pick several from `skills list`; skipped if there are none) | `--skills` |
|
|
34
|
+
| | MCP connections for the agent (pick several from `mcp connections list`; skipped if there are none) | `--mcp-connections` |
|
|
35
|
+
| | Activate the first version now? (default Yes) | `--activate` / `--no-activate` |
|
|
36
|
+
| `agents versions create` | The config (as in `agents create`), then skills and MCP connections (same questions); the new version is not activated | `--config`, `--skills`, `--mcp-connections` |
|
|
37
|
+
| `tokens create` | Token name (text) | `--name` |
|
|
38
|
+
| | Token kind (`personal` or `organization`) | `--kind` |
|
|
39
|
+
| | Token permissions (pick at least one of `query`, `read`, `write`, `admin`) | `--permissions` |
|
|
40
|
+
| `skills create` | Skill name (text) | `--name` |
|
|
41
|
+
| | Folder with the skill files (text; read like `--dir`; a folder that cannot be read, is empty or has a binary file is asked again, with the reason on stderr) | `--dir` or `--files` |
|
|
42
|
+
| `mcp connections create` | Connection name (text) | `--name` |
|
|
43
|
+
| | MCP server URL (text) | `--url` |
|
|
44
|
+
|
|
45
|
+
- Answering No to `Configure the first version now?` creates the agent without a version, so it does not ask for skills, MCP connections or activate. Add them later with `laburen agents update <agent_id> --config @config.json` or `laburen agents versions create <agent_id> --config @config.json`.
|
|
46
|
+
- `agents create` with `--skills`, `--mcp-connections` or `--activate` (by flag or in `--data`) and without `--config` fails with `config_required` (exit 2) and nothing is created, because the API would drop them without a version. `next` is your command plus `--config <value>`. If the CLI can ask, it does not fail: it goes straight to the config questions.
|
|
47
|
+
- An optional text left blank in the config questions is not sent.
|
|
48
|
+
- Headers of an http tool are not asked because they are secrets; stderr says to set them with `laburen agents tools add --tool @tool.json`.
|
|
49
|
+
- Picked skills and connections are sent as `{ "skill_id": ... }` and `{ "connection_id": ... }`. Picking none sends nothing.
|
|
50
|
+
- `mcp connections create` never asks for headers because they are secrets. Pass them with `--headers @headers.json`; stderr reminds you when they are missing.
|
|
51
|
+
|
|
52
|
+
Ids and values below are placeholders. Run `laburen <command> --help` for the exact flags: it marks the required ones with `(required)` and lists the accepted values (`one of: ...`) when the contract defines them. A required field with only one accepted value shows `(default: <value>)` (for example `--harness-type`, `(default: mastra)`) and is filled in for you. A value outside the accepted list (by flag or in `--data`) fails with `invalid_flag_value` (exit 2) before calling the API, and the message lists the accepted values. `--data -` reads the body from stdin; if stdin is a terminal it says so on stderr (end the input with Ctrl-D).
|
|
53
|
+
|
|
54
|
+
## Agents
|
|
55
|
+
|
|
56
|
+
```sh
|
|
57
|
+
laburen agents list # --limit, --after-id, --before-id, --paginate
|
|
58
|
+
laburen agents get <agent_id>
|
|
59
|
+
laburen agents create --name Support --harness-type mastra
|
|
60
|
+
laburen agents create --data @agent.json # name, harness_type, config...
|
|
61
|
+
laburen agents update <agent_id> --name "Support v2"
|
|
62
|
+
laburen agents update <agent_id> --config @config.json --change-message "new prompt"
|
|
63
|
+
laburen agents delete <agent_id>
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
`agents update` creates a new version only with `--config`, `--skills` or `--mcp-connections`; without them it only edits the name and description, and `--change-message` is not saved (it says so on stderr and goes on). The new version is not activated unless you pass `--activate`.
|
|
67
|
+
|
|
68
|
+
Versions:
|
|
69
|
+
|
|
70
|
+
```sh
|
|
71
|
+
laburen agents versions list <agent_id>
|
|
72
|
+
laburen agents versions get <agent_id> <version_id>
|
|
73
|
+
laburen agents versions create <agent_id> --config @config.json --change-message "new prompt"
|
|
74
|
+
laburen agents versions activate <agent_id> <version_id>
|
|
75
|
+
laburen agents versions restore <agent_id> <version_id>
|
|
76
|
+
laburen agents versions delete <agent_id> <version_id>
|
|
77
|
+
laburen agents versions compare <agent_id> --from <version_id> --to <version_id>
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
Tools (reads the latest version, changes `config.tools`, and creates a new version; the new version is not active unless you pass `--activate`):
|
|
81
|
+
|
|
82
|
+
```sh
|
|
83
|
+
laburen agents tools add <agent_id> --tool '{"type":"send_files"}'
|
|
84
|
+
laburen agents tools add <agent_id> --tool @tool.json
|
|
85
|
+
laburen agents tools remove <agent_id> <tool_id>
|
|
86
|
+
laburen agents tools add <agent_id> --tool @tool.json --activate
|
|
87
|
+
laburen agents tools add --schema # JSON Schema of a tool and of the response; no login, no API call
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
`--tool` is required: without it `tools add` fails with `missing_required` and `next` is your command plus `--tool <value>`. `laburen agents tools add --help` shows the tool types and an example `http` tool with `headers`, `body` and `query_parameters` (lists of `{ key, value?, is_user_provided?, description?, required? }`). `--activate` activates the new version (it sends `activate: true`); without it the version stays inactive and stderr says `Created version <n> (not active). Activate it with: laburen agents versions activate <agent_id> <version_id>`. If the CLI can ask and you passed neither `--activate` nor `--no-activate`, it asks "Activate the new version?" (default No), after the delete confirmation in `tools remove`; `--yes` does not answer it. Without `<agent_id>` both commands pick the agent from `agents list` (see "Picking a missing id"). Without `<tool_id>`, `tools remove` picks from the tools of the latest version (name, or type if it has none, with the id next to it); if it has none it fails with `no_results` and `next` is `tools add`. When the CLI cannot ask, the missing tool fails with `missing_arguments` and `choices` like any other id. A tool or agent picked from a list is always confirmed, even with `--yes`. `tools remove` matches the tool by its `id`. If no tool has it, it fails with `tool_not_found` (exit 1, like any resource that does not exist). Redacted header values (`[REDACTED]`) are sent back as they came; the server keeps the stored secret.
|
|
91
|
+
|
|
92
|
+
## Run an agent
|
|
93
|
+
|
|
94
|
+
```sh
|
|
95
|
+
laburen agents run <agent_id> "Do you have the XR 150 in stock?"
|
|
96
|
+
echo "Hello" | laburen agents run <agent_id> # no message argument: reads stdin when it is not a terminal
|
|
97
|
+
laburen agents run <agent_id> --thread <thread_id> "And in red?"
|
|
98
|
+
laburen agents run <agent_id> --file https://example.com/menu.pdf "Summarize this"
|
|
99
|
+
laburen agents run <agent_id> --version-id <version_id> --context "The user is a VIP" "Hi"
|
|
100
|
+
laburen agents run <agent_id> "Hi" --json # waits for the end and prints the final JSON
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
Runs one turn and shows it live. stdout gets only the text of the answer; reasoning, tool calls and results, sources and the footer go to stderr, so `laburen agents run ... > answer.txt` saves just the answer. The footer has the `thread`, tokens, credits (when the API reports a cost), the duration and the command to continue (`continue: laburen agents run <agent_id> --thread <thread_id> "…"`). If the agent handed the conversation to a human, a line says so.
|
|
104
|
+
|
|
105
|
+
| Flag | Body field | Note |
|
|
106
|
+
|---|---|---|
|
|
107
|
+
| `[message]` or stdin | `messages` | With `--file`, the message has a text part and one `file` part per URL; with only `--file` the message is just the files |
|
|
108
|
+
| `--thread <id>` | `memory.thread` | Continues a previous conversation |
|
|
109
|
+
| `--resource <id>` | `memory.resource` | Your own id for the end user |
|
|
110
|
+
| `--file <url>` (repeatable) | `messages[0].parts[]` | The media type comes from the URL extension; if it is unknown it fails with `invalid_flag_value` and you send the part with `--data` |
|
|
111
|
+
| `--instructions <text\|@file>` | `instructions` | Replaces the prompt for this run. Needs `write` permission (the API rejects it otherwise) |
|
|
112
|
+
| `--model <id>` | `model` | Same permission |
|
|
113
|
+
| `--reasoning <level>` | `model_settings.reasoning` | `off`, `low`, `medium`, `high` or `max`; same permission |
|
|
114
|
+
| `--max-steps <n>` | `max_steps` | Same permission |
|
|
115
|
+
| `--version-id <version_id>` | `versions.agents[<agent_id>].version_id` | Runs that version instead of the active one |
|
|
116
|
+
| `--context <text>` (repeatable) | `context[]` | Extra text for the model |
|
|
117
|
+
| `--data <json\|@file\|->` | the whole body | Flags override what `--data` brings; `--file` replaces its `messages` and warns on stderr (`Warning: --file replaces the messages of --data.`) |
|
|
118
|
+
| `--verbose` | | Shows the result of each tool in full instead of cut to one line |
|
|
119
|
+
| `--json` | | Uses `/generate`: prints the final JSON on stdout and nothing else |
|
|
120
|
+
|
|
121
|
+
The message comes from the argument; if there is none, from `--file` or the `messages` of `--data`; only if none of those exist and stdin is not a terminal is stdin read. Without any message it fails with `missing_required` (exit 2).
|
|
122
|
+
|
|
123
|
+
Ctrl+C stops reading and exits with `130`: the turn keeps running on the server and is billed. stderr says so and, if the thread was already known, prints the `continue:` command. If the turn fails midway, what was already printed stays, and the error goes to stderr (exit 1); its `next` is the `continue:` command of the thread, not `--help`. If stdout is closed (`| head -1`) the CLI stops quietly and still prints the `continue:` line on stderr; a closed stderr also stops it quietly. A turn that takes more than 10 minutes fails with `turn_deadline_exceeded`.
|
|
124
|
+
|
|
125
|
+
## Skills
|
|
126
|
+
|
|
127
|
+
There is no `skills update`: to change a skill, create a version.
|
|
128
|
+
|
|
129
|
+
```sh
|
|
130
|
+
laburen skills list
|
|
131
|
+
laburen skills get <skill_id>
|
|
132
|
+
laburen skills create --name my-skill --dir ./my-skill
|
|
133
|
+
laburen skills delete <skill_id>
|
|
134
|
+
laburen skills versions create <skill_id> --dir ./my-skill --change-message "fix steps"
|
|
135
|
+
laburen skills versions list <skill_id>
|
|
136
|
+
laburen skills versions get <skill_id> <version_id>
|
|
137
|
+
laburen skills versions activate <skill_id> <version_id>
|
|
138
|
+
laburen skills versions restore <skill_id> <version_id>
|
|
139
|
+
laburen skills versions delete <skill_id> <version_id>
|
|
140
|
+
laburen skills versions compare <skill_id> --from <version_id> --to <version_id>
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
`--dir <folder>` reads every file under the folder (relative paths with `/`, skipping `.git` and `node_modules`) and sends them as `files`. Do not combine it with `--files` or with a `--data` that has `files`; a `--data` without `files` (for example `{"name":"my-skill"}`) is combined with the folder. Only UTF-8 text is sent: a file with a NUL byte or invalid UTF-8 fails with exit 2 naming the file, and nothing is sent. Hidden files and folders (`.env`, `.DS_Store`...) and symbolic links are skipped, with a notice on stderr for each one.
|
|
144
|
+
|
|
145
|
+
## MCP connections
|
|
146
|
+
|
|
147
|
+
```sh
|
|
148
|
+
laburen mcp connections list
|
|
149
|
+
laburen mcp connections get <connection_id>
|
|
150
|
+
laburen mcp connections create --name crm --url https://example.com/mcp --headers @headers.json
|
|
151
|
+
laburen mcp connections update <connection_id> --name crm-prod
|
|
152
|
+
laburen mcp connections delete <connection_id>
|
|
153
|
+
laburen mcp connections versions create <connection_id> --url https://example.com/mcp
|
|
154
|
+
laburen mcp connections versions list <connection_id>
|
|
155
|
+
laburen mcp connections versions get <connection_id> <version_id>
|
|
156
|
+
laburen mcp connections versions activate <connection_id> <version_id>
|
|
157
|
+
laburen mcp connections versions restore <connection_id> <version_id>
|
|
158
|
+
laburen mcp connections versions delete <connection_id> <version_id>
|
|
159
|
+
laburen mcp connections versions compare <connection_id> --from <version_id> --to <version_id>
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
## Tokens
|
|
163
|
+
|
|
164
|
+
```sh
|
|
165
|
+
laburen tokens list
|
|
166
|
+
laburen tokens create --name worker --data @token.json # token.json: kind, permissions...
|
|
167
|
+
laburen tokens update <token_id> --description "worker prod"
|
|
168
|
+
laburen tokens revoke <token_id>
|
|
169
|
+
```
|
|
170
|
+
|
|
171
|
+
`tokens create` prints the token `value` once. Without `--json` it also warns on stderr that the value will not be shown again.
|
|
172
|
+
|
|
173
|
+
## Account and organization
|
|
174
|
+
|
|
175
|
+
```sh
|
|
176
|
+
laburen login
|
|
177
|
+
laburen logout
|
|
178
|
+
laburen orgs list # marks the current one
|
|
179
|
+
laburen models list # table: NAME, ID, REASONING (levels and the default effort), IMAGES (native, described) and PDF (native, text + page image, transcribed), CACHE, CONTEXT, IN $/M, OUT $/M, CACHE READ $/M (all pages; --json keeps the API shape)
|
|
180
|
+
laburen orgs switch [<id>] # saves it; without id it asks (in a terminal) or fails with choices
|
|
181
|
+
laburen link --org <id> # writes .laburen/link.json
|
|
182
|
+
laburen unlink # deletes .laburen/link.json
|
|
183
|
+
laburen me organizations list # same data as `orgs list`, raw
|
|
184
|
+
```
|
|
185
|
+
|
|
186
|
+
See [auth-and-organizations.md](auth-and-organizations.md).
|
|
@@ -0,0 +1,87 @@
|
|
|
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).
|
|
8
|
+
|
|
9
|
+
Without `--json`, lists print as a table and single items as `key: value` lines. Nested objects appear as one-line JSON and lists of strings as `a,b`. 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.
|
|
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": [ ... ] }`.
|
|
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`: only when the API sent them, as it sent them: `[{ "field": "...", "message": "..." }]`.
|
|
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, 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`, `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`. 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
|
+
- `invalid_link`: `.laburen/link.json` is broken, or `.laburen` exists and is not a folder.
|
|
67
|
+
- `auth_lock_timeout`: another `laburen` held the credentials lock too long; `next` is `rm "<lock file>"`.
|
|
68
|
+
- `network_error`: the API could not be reached (or did not answer in time).
|
|
69
|
+
|
|
70
|
+
Some API errors come with `next` too: `organization_access_denied` → `laburen orgs list`; `insufficient_permissions` → `laburen tokens list` (the token you used lacks the permission); `skill_name_taken` → `laburen skills list`; `mcp_connection_name_taken` → `laburen mcp connections list --search <value>`; `resource_in_use` → `laburen <command> --help` (the API only says how many agent versions use the resource, not which); `*_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`) without its own `next` gets `laburen <command> --help`.
|
|
71
|
+
|
|
72
|
+
## Exit codes
|
|
73
|
+
|
|
74
|
+
| Code | Meaning |
|
|
75
|
+
|---|---|
|
|
76
|
+
| `0` | ok (also `--help` and `--version`) |
|
|
77
|
+
| `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`) |
|
|
78
|
+
| `2` | wrong usage: missing argument, unknown command, invalid flag value (also an empty `--org`), `--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` |
|
|
79
|
+
| `130` | Ctrl+C during `agents run` (the turn keeps running on the server) |
|
|
80
|
+
|
|
81
|
+
## Non-interactive mode
|
|
82
|
+
|
|
83
|
+
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.
|
|
84
|
+
|
|
85
|
+
## Colors and the version notice
|
|
86
|
+
|
|
87
|
+
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
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
2
|
+
"name": "@laburen/delta-cli",
|
|
3
|
+
"version": "0.2.0-canary.9",
|
|
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.9",
|
|
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
|
+
}
|