@bendyline/gezel-cli 1.0.2 → 1.0.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 +23 -8
- package/dist/bin/gezel.js +847 -223
- package/dist/tui/index.js +884 -364
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -13,8 +13,9 @@ gezel
|
|
|
13
13
|
```
|
|
14
14
|
|
|
15
15
|
On a clean machine, the TUI stays in first-time setup until you decide what to
|
|
16
|
-
install. It offers the verified native toolkit first,
|
|
17
|
-
|
|
16
|
+
install. It offers the verified Gezel native toolkit first, downloaded from
|
|
17
|
+
the [Gezel GitHub Releases](https://github.com/bendyline/gezel/releases/), then
|
|
18
|
+
device-ranked model choices:
|
|
18
19
|
|
|
19
20
|
1. The best chat model plus every recommended image, speech, reading, and video
|
|
20
21
|
helper that fits this device.
|
|
@@ -24,6 +25,11 @@ choices:
|
|
|
24
25
|
Downloads show live progress and activate inside the running daemon, so setup
|
|
25
26
|
continues directly into the TUI without a restart.
|
|
26
27
|
|
|
28
|
+
If the per-user or machine-shared store already has the configured model, the
|
|
29
|
+
TUI uses it without downloading another copy. A stale recommendation never
|
|
30
|
+
counts merely because some other shared model exists: setup asks you to use an
|
|
31
|
+
available model or download the recommendation instead.
|
|
32
|
+
|
|
27
33
|
## Which Gezel service the CLI uses
|
|
28
34
|
|
|
29
35
|
With no connection flags, the CLI follows this order:
|
|
@@ -32,10 +38,12 @@ With no connection flags, the CLI follows this order:
|
|
|
32
38
|
machine service when one is present. A modern machine service on port
|
|
33
39
|
`6228` is an engine broker, not a product API, so the CLI never sends it
|
|
34
40
|
projects, credentials, tools, or terminal requests.
|
|
35
|
-
2. Discover the logged-in user's product daemon through the
|
|
36
|
-
Its actual dynamic port and
|
|
37
|
-
`~/.gezel/runtime`; management commands
|
|
38
|
-
when it is absent.
|
|
41
|
+
2. Discover the logged-in user's product daemon through the same pinned
|
|
42
|
+
runtime discovery used by the Gezel app SDK. Its actual dynamic port and
|
|
43
|
+
pinned TLS certificate come from `~/.gezel/runtime`; management commands
|
|
44
|
+
may start that user-role daemon when it is absent. The interactive TUI
|
|
45
|
+
retains ownership when it starts a daemon itself, so exiting the TUI runs
|
|
46
|
+
the daemon's complete shutdown path and cleans up its local engine children.
|
|
39
47
|
3. On first use, the terminal waits while the Gezel app asks you to approve
|
|
40
48
|
**Gezel CLI**. The terminal shows a six-character code that you enter in
|
|
41
49
|
the app to confirm that you initiated the request. The resulting revocable,
|
|
@@ -131,7 +139,7 @@ Run `gezel --help` for the full list. The most-used ones:
|
|
|
131
139
|
|---|---|
|
|
132
140
|
| `gezel` | Launch the interactive TUI |
|
|
133
141
|
| `gezel run [prompt…]` | One-shot prompt in the current directory's project, using its voorman by default; optionally `--gezel <id>` / `--project <folder>` |
|
|
134
|
-
| `gezel start` / `stop` / `status` | Use or inspect the selected service
|
|
142
|
+
| `gezel start` / `stop` / `status` | Use or inspect the selected service. `stop` is the same hard stop as the desktop UX: cancel work, unload local engines, and switch to Reactive. `stop --daemon` shuts down a user-owned daemon process itself. `start --web` serves the browser UI. On hosts without a Gezel machine service, a started daemon prefers the canonical port 6228 (ephemeral fallback) so third-party OpenAI clients get a stable `https://127.0.0.1:6228/v1` base URL; with a machine service installed, the service owns 6228 and started daemons use an ephemeral port (`--port` pins one explicitly). |
|
|
135
143
|
| `gezel doctor` | Report on the local install |
|
|
136
144
|
| `gezel mode [read-only\|reactive\|reactive+tasks\|full-play]` | Show or change how much AI activity is allowed |
|
|
137
145
|
| `gezel agent list\|create\|show` | Manage your gezels |
|
|
@@ -148,7 +156,14 @@ gezel-owned active tasks for the current project. Night Shift is managed with
|
|
|
148
156
|
`/nightshift start`, `/nightshift stop`, and `/nightshift list`; the command
|
|
149
157
|
wordwheel exposes all three subcommands. `/mode` opens a picker for the same
|
|
150
158
|
four activity levels as the one-shot command; `/mode reactive+tasks` (for
|
|
151
|
-
example) switches directly.
|
|
159
|
+
example) switches directly. `/model` lists every installed user/shared model
|
|
160
|
+
and includes **Download a new model**; `/model download` opens that device-ranked
|
|
161
|
+
download list directly. A completed download is selected for the active gezel
|
|
162
|
+
and starts a fresh chat. Project edit permissions are available through
|
|
163
|
+
`/allow` and `/disallow`: use `edits` for built-in tools and background work,
|
|
164
|
+
`codexedits` for Codex sessions, or `claudeedits` for Claude sessions. For
|
|
165
|
+
example, `/disallow edits` makes Gezel-managed access to the current project
|
|
166
|
+
read-only, while `/allow codexedits` puts Codex in project-scoped edit mode.
|
|
152
167
|
|
|
153
168
|
## Stability
|
|
154
169
|
|