@qwen-code/channel-base 0.19.11-nightly.20260717.f8e6e8931 → 0.19.11
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 +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -72,9 +72,9 @@ Migration note for existing TypeScript plugins: if your adapter constructor or f
|
|
|
72
72
|
Channel adapters can run in two host modes:
|
|
73
73
|
|
|
74
74
|
- `qwen channel start [name]` is the standalone service. It uses `AcpBridge` over a `qwen-code --acp` child process and remains the default channel command.
|
|
75
|
-
- `qwen serve --channel <name>` and `qwen serve --channel all` are experimental daemon-managed modes.
|
|
75
|
+
- `qwen serve --channel <name>` and `qwen serve --channel all` are experimental daemon-managed modes. `qwen serve` starts one out-of-process channel worker, the worker connects back to the daemon through the SDK, and adapters receive a `DaemonChannelBridge`-backed `ChannelAgentBridge` facade.
|
|
76
76
|
|
|
77
|
-
In daemon-managed mode,
|
|
77
|
+
In daemon-managed mode, one daemon is bound to one workspace. Every selected channel's `cwd` must resolve to that same workspace. The optional `shellCommand` method is exposed to adapters only when the daemon advertises the `session_shell_command` capability.
|
|
78
78
|
|
|
79
79
|
## Architecture
|
|
80
80
|
|