@buda-ai/connector 0.1.7 → 0.1.8

package/README.md

@@ -50,13 +50,22 @@ an OAuth token with `--launch-config-stdin`.
 Desktop can start the sidecar with:
 
 ```bash
-printf '{"serverUrl":"https://buda.im","oauthToken":"..."}\n' \
-  | buda-connector daemon --launch-config-stdin
+printf '{"serverUrl":"https://buda.im","spaceId":"spc_...","oauthToken":"..."}\n' \
+  | buda-connector daemon --desktop --launch-config-stdin --plain
 ```
 
+The Desktop controller keeps stdin open as its transient lease. Closing Desktop closes the
+lease and stops a transient daemon. If the standalone CLI takes the same daemon over as
+persistent, closing Desktop no longer stops it.
+
+Packaged Desktop launches also set `BUDA_CONNECTOR_BUNDLED_RUNTIME_ROOT`,
+`BUDA_CONNECTOR_RUNTIME_ENTRYPOINT`, and `BUDA_CONNECTOR_RUNTIME_NODE` so the detached runtime is
+copied out of the application bundle without requiring network access.
+
 Supported launch config fields:
 
 - `serverUrl`
+- `spaceId`
 - `token`
 - `workdirRoot`
 - `oauthToken`
@@ -72,13 +81,32 @@ The token selects that Space's independent local connector profile:
 npx -y @buda-ai/connector@latest daemon --token "cet_..."
 ```
 
-Desktop and other authenticated clients should use OAuth token launch config
-instead:
-
-```bash
-printf '%s\n' '{"serverUrl":"https://buda.im","oauthToken":"..."}' \
-  | npx -y @buda-ai/connector@latest daemon --launch-config-stdin
-```
+The command installs the runtime into a stable, platform-specific directory under `~/.buda`,
+starts or reuses one detached daemon for the device/Space identity, and attaches the terminal
+Dashboard. The Dashboard lists every local Connector identity stored in `~/.buda/device.json`
+across servers and Spaces, and also discovers running daemons from their authenticated local
+control records if a stored identity is missing. It opens before registration finishes and shows a
+token-scoped `Connecting / New Connector / Resolving Space` row until the server returns the
+canonical identity. The Connector resolved by the invocation token is selected first.
+
+Dashboard controls:
+
+- `Up` / `Down` (or `K` / `J`): select a local Connector when the Connectors section is active.
+- `Tab`: switch between the Connectors, Activity, and Agent Debug sections.
+- Mouse wheel: scroll the Activity or Agent Debug pane under the pointer.
+- `S`: ask for confirmation, then gracefully stop the selected Connector. The Dashboard remains
+  open so another local Connector can be selected.
+- `Escape`: exit the Dashboard only. Every Connector daemon keeps running in the background.
+- `Ctrl+C`: open an exit menu. **Exit Dashboard only** is the safe default. Stopping every local
+  Connector requires choosing **Stop all local Connectors and exit** and confirming a second
+  warning because running Agent tasks will be interrupted.
+
+The manager sends stop requests through each daemon's existing authenticated local control
+channel. Local control requests time out instead of blocking the Dashboard indefinitely. When a
+missing local profile recovers an existing canonical Connector ID, an idle stale daemon is stopped
+cleanly before the new credential takes over; active Agent work is never force-stopped. The manager
+never prints Connector or device tokens. `--plain` and non-TTY launches retain their existing
+log/background behavior.
 
 You can also pass launch options directly:
 
@@ -88,15 +116,18 @@ buda-connector daemon --token "cet_..." --workdir "$HOME/.buda/agents"
 
 ## Local Files
 
-- `~/.buda/device.json` (versioned device profiles keyed by server origin and token fingerprint)
+- `~/.buda/device.json` (canonical identities keyed by device, normalized server origin, and Space)
+- `~/.buda/daemons/` (owner-only local control metadata and process locks)
+- `~/.buda/runtime/<platform>-<arch>-node<ABI>/<version>/` (stable detached runtimes)
 - `~/.buda/logs/connector.log`
 - `~/.buda/agents/`
 
 Existing `~/.buda/connector.log` files are left in place as historical logs after upgrading.
 
 Server URL paths and query strings do not create a new identity. Scheme and non-default port
-changes do. Connector tokens for different Spaces on the same server select independent profiles,
-so their daemons can run concurrently. Raw tokens are never used in profile keys or lock paths.
+changes do. Connector tokens for different Spaces on the same server resolve independent canonical
+identities, so their daemons can run concurrently. Raw tokens are never used in identity keys or
+lock paths.
 The installation-level physical device ID remains shared across profiles.
 
 New server profiles share a privacy-preserving device ID derived by hashing the operating