@blue-soda/dsh-remote 0.5.7 → 0.5.8
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 +14 -3
- package/dist/index.js +909 -353
- package/dist/index.js.map +4 -4
- package/dsh-plugin.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -23,7 +23,7 @@ Continue DeepSeek Harness sessions and experimental Codex workspaces from anothe
|
|
|
23
23
|
Add the current package version to the `web` profile, then restart Harness:
|
|
24
24
|
|
|
25
25
|
```sh
|
|
26
|
-
dsh plugin --profile web add -w @blue-soda/dsh-remote@0.5.
|
|
26
|
+
dsh plugin --profile web add -w @blue-soda/dsh-remote@0.5.8
|
|
27
27
|
```
|
|
28
28
|
|
|
29
29
|
### dsh-TUI Host
|
|
@@ -31,7 +31,7 @@ dsh plugin --profile web add -w @blue-soda/dsh-remote@0.5.7
|
|
|
31
31
|
Remote can also run as a Host in a terminal-only [dsh-TUI](https://github.com/ccch1mneyyy/dsh-TUI) profile:
|
|
32
32
|
|
|
33
33
|
```sh
|
|
34
|
-
dsh plugin --profile dsh-tui add -w @blue-soda/dsh-remote@0.5.
|
|
34
|
+
dsh plugin --profile dsh-tui add -w @blue-soda/dsh-remote@0.5.8
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
After starting dsh-TUI, manage Remote with `/remote`, `/remote login`, `/remote status`, and `/remote logout`.
|
|
@@ -44,11 +44,12 @@ After starting dsh-TUI, manage Remote with `/remote`, `/remote login`, `/remote
|
|
|
44
44
|
- Use the official workspace file tree and bounded read-only previews on supported Harness versions.
|
|
45
45
|
- Use an optional Host-local terminal and authorized loopback development-service previews.
|
|
46
46
|
- Open Host Codex projects in the existing Remote UI through the optional experimental Codex domain. It is **off by default** since 0.5.1: turn it on in the DeepSeek Remote settings card, which starts `codex app-server` on the Host and applies immediately.
|
|
47
|
+
- Long Codex histories load tail-first: the Host indexes turn ids without full items, loads full items from the newest turns, and the client reuses its last page for 60 seconds. A real 136-turn thread opens from its 25 newest turns (a 50-message page) instead of reading the whole thread.
|
|
47
48
|
- Reach the Host without opening a public listening port or configuring router port forwarding.
|
|
48
49
|
|
|
49
50
|
## Compatibility
|
|
50
51
|
|
|
51
|
-
Plugin `0.
|
|
52
|
+
Plugin `0.5.8` targets DeepSeek Harness `dsh-v0.2.0-rc.2` and retains `dsh-v0.1.7-rc.1` compatibility; it also supports `dsh-v0.1.6-alpha.2` and earlier settings hosts. It supports:
|
|
52
53
|
|
|
53
54
|
- `dsh-v0.1.1-rc.2` through the official legacy `ApiProxy`;
|
|
54
55
|
- `dsh-v0.1.2-alpha.1` through `dsh-v0.1.2-rc.1` through the official Typert Remote Gateway;
|
|
@@ -56,6 +57,16 @@ Plugin `0.4.29` targets DeepSeek Harness `dsh-v0.2.0-rc.2` and retains `dsh-v0.1
|
|
|
56
57
|
|
|
57
58
|
The same package feature-detects the older settings registry and the `0.1.7-rc.1` and `0.2.0-rc.2` Volatile settings entry. Remote Web/Desktop and Android normalize released sessions that still report the retired `code` agent preset to `ptc`. The Host reads the running Harness version from the CLI entrypoint, or from the 0.2.0 Desktop shell's `@deepseek-ai/dsh-desktop-host` entrypoint when the Harness CLI package is only a sibling of that entrypoint inside `app.asar`.
|
|
58
59
|
|
|
60
|
+
## Codex history diagnostics
|
|
61
|
+
|
|
62
|
+
The Codex virtual harness runs in the DSH client's Node process. By default it writes **no** cache diagnostics file. To enable the optional metadata file, start the **client** with:
|
|
63
|
+
|
|
64
|
+
```sh
|
|
65
|
+
DSH_CODEX_HISTORY_STATS=1
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
It then writes `codex-history-cache-stats.json` under `$DSH_HOME` (default `~/.dsh`) on cache hits/misses. The file contains only cache metadata - `hits`/`misses`, TTL, session id, record count, cursor, first/last seq and age - never message text, tool output or event data. The switch is checked in the client Node process; it has no effect on the Host's history pages.
|
|
69
|
+
|
|
59
70
|
## Self-hosted Server
|
|
60
71
|
|
|
61
72
|
This repository includes a self-hosted, Relay-only Server in [`apps/server`](https://github.com/blue-soda/ds-harness-remote/tree/main/apps/server) that supports multiple accounts, with devices and tokens namespaced per account. `DSH_SERVER_ACCOUNT` and `DSH_SERVER_PASSWORD` configure a seed account; account creation is off by default and can be enabled with `DSH_SERVER_REGISTRATION_CODE`, or replaced by DeepSeek platform sign-in (`DSH_SERVER_DEEPSEEK_LOGIN=on`) or a QR provider (`DSH_SERVER_OAUTH_PROVIDER`). It provides account login, device credentials, encrypted Control/Noise forwarding, Relay, and a device-status page. It does not provide the complete site - Remote Web session UI or Admin - or WebRTC/TURN deployment.
|