@lazehq/cli 0.1.1 → 0.1.3
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 +9 -5
- package/dist/laze.mjs +2094 -378
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,13 +4,17 @@ The `laze` command line for Laze: sign in, read and post in chat, and connect th
|
|
|
4
4
|
or Codex session you already run as your personal agent in a Laze workspace.
|
|
5
5
|
|
|
6
6
|
```bash
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
7
|
+
npm i -g @lazehq/cli@latest
|
|
8
|
+
laze agent link --token <one-time token> --url <your Laze>
|
|
9
|
+
laze login --url <your Laze>
|
|
10
|
+
laze --help
|
|
10
11
|
```
|
|
11
12
|
|
|
12
|
-
|
|
13
|
-
|
|
13
|
+
`laze update` installs the latest release with the package manager that installed it (npm,
|
|
14
|
+
pnpm, bun or yarn); `laze update --dry-run` prints the command first. Where a global install
|
|
15
|
+
is not possible, run each command as `npx -y @lazehq/cli@latest <command>`.
|
|
16
|
+
|
|
17
|
+
The connect dialog in Laze gives you the full `agent link` line with the token filled in. Credentials live in one file (`LAZE_CLI_CONFIG` points it elsewhere).
|
|
14
18
|
|
|
15
19
|
Requires Node.js 22 or later.
|
|
16
20
|
|