@lobehub/cli 0.0.65 → 0.0.66

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 (4) hide show
  1. package/README.md +21 -0
  2. package/dist/index.js +45269 -43175
  3. package/man/man1/lh.1 +1 -1
  4. package/package.json +27 -28
package/README.md CHANGED
@@ -123,3 +123,24 @@ Signal and VFS tests additionally require their documented Agent ID variables.
123
123
  Search fixtures wait up to 60 seconds for asynchronous indexing; a timeout fails
124
124
  the suite rather than accepting empty results. The command above supplies a live
125
125
  network budget explicitly; this does not change unit-test timeouts or enable retries.
126
+
127
+ ### Native Codex app-server on a connected device
128
+
129
+ A current CLI advertises `codex-app-server-v1` only after its resolved Codex binary
130
+ completes a native app-server handshake. The probe runs once per gateway connection
131
+ (and again after 10 minutes), not once per system-info request. `lh connect capabilities`
132
+ reports that same capability as JSON without logging in, connecting a device, or creating
133
+ a conversation. Desktop gateway connections invoke this command through their bundled
134
+ CLI, so an unrelated global CLI cannot determine support. Missing, incompatible, or
135
+ timed-out binaries do not advertise native support.
136
+
137
+ Codex topics run through `codex exec` unless the user enables the
138
+ **Codex App Server Runtime** Lab. With the Lab on and a capable connection, the server
139
+ runs them through app-server and persists each message's native session and turn IDs.
140
+ These topics keep the `codex exec` recovery: a missing native session is retried fresh
141
+ with the topic transcript.
142
+
143
+ The internal `lh hetero exec --codex-app-server` transport uses a per-operation process
144
+ that owns cancellation and shell identity. This transport rejects unsupported approval
145
+ or sandbox arguments instead of weakening permissions. The richer permission bridge is
146
+ maintained separately.