@agentknight/client 0.9.48 → 0.9.49

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 CHANGED
@@ -18,6 +18,8 @@ to verify recovery.
18
18
  The CLI depends on the SDK; both use the same release version. The SDK can be
19
19
  published independently through the [npm release workflow](../../.github/workflows/agentknight-npm-publish.yml).
20
20
  See the [SDK entry point](../../shared/sdk/src/index.ts) for the public API.
21
+ For configuration and onboarding without loading the runtime, use
22
+ [`@agentknight/sdk/configuration`](../../shared/sdk/src/configuration.ts).
21
23
 
22
24
  ## Run
23
25
 
@@ -124,6 +126,10 @@ HTTPS and WSS for the entire PC Agent connection. `AGENTKNIGHT_MACHINE_NAME`
124
126
  controls the PC name shown to mobile clients. The selection and pairing webpage
125
127
  listens only on loopback; `PAIRING_PAGE_PORT` changes its local port.
126
128
 
129
+ On the local page, expand a working-directory folder and select a session to
130
+ browse its conversation history. Viewing is read-only and does not change
131
+ mobile sync selection or create a separate archive.
132
+
127
133
  Use **重连** on the local page to retry with saved credentials without
128
134
  restarting coding agents. Recognized authorization-service outages retry
129
135
  automatically; other server-initiated disconnects require user action.
@@ -209,10 +215,17 @@ Relay Server and Android client setup.
209
215
 
210
216
  ## Windows app
211
217
 
212
- The Windows app's **PC Client** tab downloads and caches the published client;
213
- it is not bundled with the app. Follow the dependency prompts, then configure
214
- your Relay connection. Closing the app stops only clients it started;
215
- an existing client is reused without changing its settings or lifetime.
218
+ Windows release packages include a private Node runtime and prebuilt PC Client.
219
+ The **PC Client** tab does not need a global Node/npm installation or a first-run
220
+ client download; update or repair it through the Windows app. WebView2 and
221
+ provider sign-in remain separate prerequisites. Source builds without a bundled
222
+ runtime retain the Node/npm setup path.
223
+
224
+ Closing the window keeps clients running in the notification area. **Open**
225
+ restores the window; **Exit** stops only app-owned clients, never external ones.
226
+ App-managed configuration is encrypted and saved separately from external ENV
227
+ files. See the [Windows runtime design](../../docs/remote-sessions/windows-runtime-design.md)
228
+ for configuration ownership and the limits of Windows user-scoped protection.
216
229
 
217
230
  ## Coding agents
218
231
 
@@ -285,6 +298,10 @@ credentials; sending requires the authentication described above.
285
298
  Credentials stay on the PC; discovery does not verify authentication.
286
299
  Copilot-specific Workbench, group and peer-chat operations remain unsupported.
287
300
 
301
+ Codex controls depend on the installed CLI's [App Server capabilities](https://developers.openai.com/codex/app-server/).
302
+ Changes require an idle session and affect its subsequent turns, not approval or
303
+ sandbox permissions.
304
+
288
305
  The ACP executable must speak the Agent Client Protocol over stdio; an ordinary
289
306
  Codex or Claude Code CLI is not automatically an ACP endpoint. Arguments are
290
307
  passed literally, without a shell. AgentKnight does not download or authenticate