dsh-local-link 1.2.6 → 1.2.7
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/CHANGELOG.md +17 -0
- package/README.md +3 -3
- package/README.ru.md +3 -3
- package/README.zh.md +3 -3
- package/docs/ARCHITECTURE.md +1 -1
- package/package.json +46 -42
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,23 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project are documented here.
|
|
4
4
|
|
|
5
|
+
## 1.2.7 — 2026-11-20
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
|
|
9
|
+
- Added the verified DeepSeek Harness `0.2.2-rc.5` to `engines.dsh` and the matching Host peer range, and updated exact development contracts. Earlier declarations, including `0.2.2-rc.1`, are retained. Ordinary rc.5 startup no longer requires a version exemption.
|
|
10
|
+
- Pinned the development graph's OpenTelemetry API to 1.9.1 to satisfy the SDK's `<1.10` peer constraint. Production dependencies are unchanged.
|
|
11
|
+
- Updated English, Russian and Simplified Chinese compatibility documentation. README screenshots retain their original rc.1 capture labels; no runtime UI or trusted-LAN behavior changed.
|
|
12
|
+
|
|
13
|
+
### Fixed
|
|
14
|
+
|
|
15
|
+
- npm publication now explicitly supplies the English `README.md` content instead of allowing npm to select `README.zh.md`. All three localized README files remain in the package. The release command restores the original manifest after success, failure or dry-run; a prepublish check rejects accidental publication without the explicit English metadata.
|
|
16
|
+
|
|
17
|
+
### Validation
|
|
18
|
+
|
|
19
|
+
- Typecheck, all 123 tests across 19 files, build, package and npm publication dry-run passed with the rc.5 SDK.
|
|
20
|
+
- Isolated EN/ZH checks on rc.5 cover pairing, selected-chat QR handoff, authenticated HTTP/WebSocket access, immediate socket closure on revoke, 15 Host-only RPC variants, three native app routes, new-chat creation, paired-device shortcuts, and ten mobile viewports from 320 to 768 CSS pixels. Physical-phone, voice, model generation and the full historical Host matrix were not rerun.
|
|
21
|
+
|
|
5
22
|
## 1.2.6 — 2026-11-18
|
|
6
23
|
|
|
7
24
|
### Changed
|
package/README.md
CHANGED
|
@@ -13,7 +13,7 @@ Use the same [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)
|
|
|
13
13
|
|
|
14
14
|
Open `Local access`, scan the QR code, and the paired browser arrives at the desktop's currently selected Harness session with the same live conversation, permissions, workspaces, and plugin surfaces.
|
|
15
15
|
|
|
16
|
-
|
|
16
|
+
Local Link `1.2.7` supports DeepSeek Harness `0.2.2-rc.5` and the earlier Hosts declared in `engines.dsh`. It reorganizes the stock Web interface into responsive drawers, compact session controls, and touch-friendly actions while keeping the same client, session, plugin slots, permissions, and live agent stream.
|
|
17
17
|
|
|
18
18
|
> **Security boundary:** the gateway uses plain HTTP and is intended only for a trusted private network. Do not expose its port to the internet or use it on public Wi-Fi.
|
|
19
19
|
|
|
@@ -73,11 +73,11 @@ The profile points at the checkout, so rebuild after changing client code and re
|
|
|
73
73
|
|
|
74
74
|
## Compatibility
|
|
75
75
|
|
|
76
|
-
Local Link `1.2.
|
|
76
|
+
Local Link `1.2.7` is built and checked against DeepSeek Harness `0.2.2-rc.5`, including ordinary plugin startup without a version exemption. Its mobile adapter supports the native sidebar mask and navigation lifecycle. The gateway recognizes both legacy dotted and current slash-based API names, while native app launching and Host administration remain available only on the Harness computer. Existing `webStartup` / `webRuntime`, public Session scopes, and native Settings navigation integrations are retained.
|
|
77
77
|
|
|
78
78
|
The installable DeepSeek Harness range is declared in `package.json` through `engines.dsh`. Compatibility is checked against exact releases—not inferred from a successful installation or a moving dist-tag.
|
|
79
79
|
|
|
80
|
-
Acceptance on `0.2.2-rc.
|
|
80
|
+
Acceptance on `0.2.2-rc.5` covers pairing, selected-chat QR handoff, authenticated HTTP/WebSocket access, immediate socket closure on revoke, Host-only API and native-app restrictions, new-chat creation, paired-device controls, and mobile layouts at 320–768 CSS pixels in EN and ZH. These checks used isolated profiles with fictional data and a loopback gateway. Earlier Host declarations retain the historical acceptance recorded in the [changelog](CHANGELOG.md); the full old-version matrix and physical-phone checks were not rerun. Mobile microphone capture over plain LAN HTTP remains unsupported; this release adds neither HTTPS nor voice input.
|
|
81
81
|
|
|
82
82
|
## Use
|
|
83
83
|
|
package/README.ru.md
CHANGED
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
|
|
14
14
|
Откройте `Local access`, отсканируйте QR-код — и подключённый браузер попадёт в текущую сессию Harness, выбранную на компьютере. Диалог, права доступа, рабочие пространства и интерфейсы плагинов останутся теми же.
|
|
15
15
|
|
|
16
|
-
|
|
16
|
+
Local Link `1.2.7` поддерживает DeepSeek Harness `0.2.2-rc.5` и предыдущие Host, объявленные в `engines.dsh`. Стандартный веб-интерфейс получает адаптивные панели, компактные элементы управления сессией и удобные для касаний действия. Клиент, сессия, слоты плагинов, разрешения и поток событий агента остаются прежними.
|
|
17
17
|
|
|
18
18
|
> **Граница безопасности:** шлюз работает по незашифрованному HTTP и предназначен только для доверенной частной сети. Не выставляйте его порт в интернет и не используйте плагин в публичных сетях Wi-Fi.
|
|
19
19
|
|
|
@@ -73,11 +73,11 @@ dsh web
|
|
|
73
73
|
|
|
74
74
|
## Совместимость
|
|
75
75
|
|
|
76
|
-
Local Link `1.2.
|
|
76
|
+
Local Link `1.2.7` собирается и проверяется на DeepSeek Harness `0.2.2-rc.5`, включая обычную загрузку плагина без исключения для версии. Мобильный адаптер учитывает маску сайдбара и порядок закрытия панели после навигации. Шлюз распознаёт старые API с точками и новые с `/`, сохраняя запуск приложений и администрирование Host доступными только на компьютере с Harness. Интеграции с `webStartup` / `webRuntime`, публичными Session-scoped слотами и штатными настройками сохранены.
|
|
77
77
|
|
|
78
78
|
Диапазон устанавливаемых версий DeepSeek Harness объявлен в `package.json` через `engines.dsh`. Совместимость проверяется на конкретных релизах и не выводится только из успешной установки или плавающего dist-tag.
|
|
79
79
|
|
|
80
|
-
На `0.2.2-rc.
|
|
80
|
+
На `0.2.2-rc.5` проверены сопряжение, переход по QR в выбранный чат, авторизованные HTTP/WebSocket, немедленное закрытие соединения после отзыва устройства, ограничения Host API и запуска приложений, создание чатов, управление устройствами и мобильная вёрстка на ширинах 320–768 CSS-пикселей в EN и ZH. Проверка выполнена в отдельных профилях с вымышленными данными и шлюзом на loopback. Предыдущие Host оставлены в диапазоне на основании исторических проверок из [changelog](CHANGELOG.md); вся старая матрица и физический телефон заново не проверялись. Запись с микрофона телефона через обычный LAN HTTP по-прежнему не поддерживается: релиз не добавляет HTTPS или голосовой ввод.
|
|
81
81
|
|
|
82
82
|
## Использование
|
|
83
83
|
|
package/README.zh.md
CHANGED
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
|
|
14
14
|
打开 `Local access` 并扫描二维码后,已配对的浏览器会进入桌面端当前选中的 Harness 会话,并继续使用相同的实时对话、权限、工作区和插件界面。
|
|
15
15
|
|
|
16
|
-
`1.2.
|
|
16
|
+
Local Link `1.2.7` 支持 DeepSeek Harness `0.2.2-rc.5` 及 `engines.dsh` 声明的较早 Host,让原生 Web 客户端可以在窄屏触控设备上使用。移动视图只调整界面布局,不接管 Harness 的会话、权限或业务逻辑。
|
|
17
17
|
|
|
18
18
|
> **安全边界:** 网关使用明文 HTTP,仅适用于可信私有网络。不要将端口暴露到互联网,也不要在公共 Wi-Fi 上使用。
|
|
19
19
|
|
|
@@ -71,11 +71,11 @@ profile 会指向当前 checkout。修改客户端代码后需要重新构建;
|
|
|
71
71
|
|
|
72
72
|
## 兼容性
|
|
73
73
|
|
|
74
|
-
Local Link `1.2.
|
|
74
|
+
Local Link `1.2.7` 使用 DeepSeek Harness `0.2.2-rc.5` 的契约构建并完成验证,包括无需版本豁免的正常插件启动。移动适配器兼容原生侧栏遮罩及导航后的关闭流程。网关同时识别旧版点分隔 API 和新版 `/` 分隔 API;原生应用启动和 Host 管理仍仅限 Harness 所在电脑。保留 `webStartup` / `webRuntime`、公开会话作用域和原生 Settings 导航集成。
|
|
75
75
|
|
|
76
76
|
可安装的 DeepSeek Harness 版本范围通过 `package.json` 中的 `engines.dsh` 声明。兼容性按精确发布版本验证,不会因为安装成功或可变的 dist-tag 就推断为兼容。
|
|
77
77
|
|
|
78
|
-
在 `0.2.2-rc.
|
|
78
|
+
在 `0.2.2-rc.5` 上已验证配对、二维码打开所选会话、认证 HTTP/WebSocket、撤销设备后立即关闭连接、Host API 和原生应用启动限制、新建会话、已配对设备管理,以及 EN/ZH 在 320–768 CSS px 的移动布局。验证使用独立的虚构数据配置和 loopback 网关。较早 Host 的声明依据[更新日志](CHANGELOG.md)中的历史验收;本次未重新运行全部旧版本矩阵或实体手机验收。普通局域网 HTTP 仍不支持手机麦克风录音;本次发布不提供 HTTPS 或语音输入。
|
|
79
79
|
|
|
80
80
|
## 使用方法
|
|
81
81
|
|
package/docs/ARCHITECTURE.md
CHANGED
|
@@ -177,7 +177,7 @@ No service discovery, certificate generator, tunnel client, native application,
|
|
|
177
177
|
|
|
178
178
|
## Compatibility strategy
|
|
179
179
|
|
|
180
|
-
Local Link `1.2.
|
|
180
|
+
Local Link `1.2.7` develops against the exact DeepSeek Harness `0.2.2-rc.5` contracts; published `1.2.6` used `0.2.2-rc.1`. The installable Host range is declared by `engines.dsh`, including ordinary startup on rc.5 without version exemptions. Current development and Harness `0.2.2` require Node.js 24.9+; the plugin's Node.js 22.19 runtime baseline is retained for earlier declared Hosts. Earlier Host acceptance remains historical rather than a freshly rerun full matrix.
|
|
181
181
|
|
|
182
182
|
The 0.1.7+ icon exports are weight-named; the client also resolves older size-named exports. Current-session details, QR identity and mobile autofocus use public Session scopes. The invitation observer also mounts on desktop; cleanup cannot erase a newer scope's identity. The legacy subagent sheet is registered only when its catalog actions exist; current Harness owns the native header catalog. Mobile details replace the older `stats` and newer `activity` / `usage` composer pills while desktop contributions remain intact.
|
|
183
183
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-local-link",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.7",
|
|
4
4
|
"description": "DeepSeek Harness plugin for lightweight LAN access to the current Web UI from phones, tablets, and other computers.",
|
|
5
5
|
"publishConfig": {
|
|
6
6
|
"access": "public"
|
|
@@ -58,15 +58,17 @@
|
|
|
58
58
|
},
|
|
59
59
|
"scripts": {
|
|
60
60
|
"build": "tsdown",
|
|
61
|
+
"prepublishOnly": "node scripts/npm-publish.ts --check",
|
|
61
62
|
"prepack": "npm run build",
|
|
62
|
-
"release:check": "npm run verify && pnpm audit --prod && npm publish --dry-run",
|
|
63
|
+
"release:check": "npm run verify && pnpm audit --prod && npm run release:publish -- --dry-run",
|
|
64
|
+
"release:publish": "node scripts/npm-publish.ts",
|
|
63
65
|
"test": "vitest run",
|
|
64
66
|
"typecheck": "tsc --noEmit",
|
|
65
67
|
"verify": "npm run typecheck && npm run test && npm pack --dry-run"
|
|
66
68
|
},
|
|
67
69
|
"engines": {
|
|
68
70
|
"node": "^22.19.0 || >=24.0.0",
|
|
69
|
-
"dsh": "0.1.0-rc.8 || 0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.7-rc.2 || 0.2.0-rc.2 || 0.2.1-alpha.2 || 0.2.1-rc.2 || 0.2.1-rc.5 || 0.2.2-rc.1"
|
|
71
|
+
"dsh": "0.1.0-rc.8 || 0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.7-rc.2 || 0.2.0-rc.2 || 0.2.1-alpha.2 || 0.2.1-rc.2 || 0.2.1-rc.5 || 0.2.2-rc.1 || 0.2.2-rc.5"
|
|
70
72
|
},
|
|
71
73
|
"keywords": [
|
|
72
74
|
"deepseek",
|
|
@@ -90,7 +92,7 @@
|
|
|
90
92
|
"author": "DoNotEatMe",
|
|
91
93
|
"peerDependencies": {
|
|
92
94
|
"@deepseek-ai/cordis": "^4.0.2",
|
|
93
|
-
"@deepseek-ai/dsh-host-webserver": "0.1.0-rc.8 || 0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.7-rc.2 || 0.2.0-rc.2 || 0.2.1-alpha.2 || 0.2.1-rc.2 || 0.2.1-rc.5 || 0.2.2-rc.1",
|
|
95
|
+
"@deepseek-ai/dsh-host-webserver": "0.1.0-rc.8 || 0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.7-rc.2 || 0.2.0-rc.2 || 0.2.1-alpha.2 || 0.2.1-rc.2 || 0.2.1-rc.5 || 0.2.2-rc.1 || 0.2.2-rc.5",
|
|
94
96
|
"react": "^18.2.0"
|
|
95
97
|
},
|
|
96
98
|
"peerDependenciesMeta": {
|
|
@@ -111,43 +113,43 @@
|
|
|
111
113
|
"devDependencies": {
|
|
112
114
|
"@deepseek-ai/cordis": "~4.1.0",
|
|
113
115
|
"@deepseek-ai/cordis-plugin-include": "~1.1.0",
|
|
114
|
-
"@deepseek-ai/dsh-agent": "0.2.2-rc.
|
|
115
|
-
"@deepseek-ai/dsh-agent-default-model": "0.2.2-rc.
|
|
116
|
-
"@deepseek-ai/dsh-api-gateway": "0.2.2-rc.
|
|
117
|
-
"@deepseek-ai/dsh-api-session-controller": "0.2.2-rc.
|
|
118
|
-
"@deepseek-ai/dsh-atomic-write": "0.2.2-rc.
|
|
119
|
-
"@deepseek-ai/dsh-attachment": "0.2.2-rc.
|
|
120
|
-
"@deepseek-ai/dsh-client-connection": "0.2.2-rc.
|
|
121
|
-
"@deepseek-ai/dsh-client-locale": "0.2.2-rc.
|
|
122
|
-
"@deepseek-ai/dsh-client-ui-conversation": "0.2.2-rc.
|
|
123
|
-
"@deepseek-ai/dsh-client-ui-layout": "0.2.2-rc.
|
|
124
|
-
"@deepseek-ai/dsh-client-ui-primitives": "0.2.2-rc.
|
|
125
|
-
"@deepseek-ai/dsh-client-ui-renderer": "0.2.2-rc.
|
|
126
|
-
"@deepseek-ai/dsh-client-ui-session": "0.2.2-rc.
|
|
127
|
-
"@deepseek-ai/dsh-client-ui-settings": "0.2.2-rc.
|
|
128
|
-
"@deepseek-ai/dsh-client-ui-sidebar": "0.2.2-rc.
|
|
129
|
-
"@deepseek-ai/dsh-client-ui-slots": "0.2.2-rc.
|
|
130
|
-
"@deepseek-ai/dsh-client-ui-theme": "0.2.2-rc.
|
|
131
|
-
"@deepseek-ai/dsh-file-reference": "0.2.2-rc.
|
|
132
|
-
"@deepseek-ai/dsh-home-paths": "0.2.2-rc.
|
|
133
|
-
"@deepseek-ai/dsh-host-webserver": "0.2.2-rc.
|
|
134
|
-
"@deepseek-ai/dsh-llm": "0.2.2-rc.
|
|
135
|
-
"@deepseek-ai/dsh-native-command": "0.2.2-rc.
|
|
136
|
-
"@deepseek-ai/dsh-sandbox": "0.2.2-rc.
|
|
137
|
-
"@deepseek-ai/dsh-scope": "0.2.2-rc.
|
|
138
|
-
"@deepseek-ai/dsh-session": "0.2.2-rc.
|
|
139
|
-
"@deepseek-ai/dsh-session-log-export": "0.2.2-rc.
|
|
140
|
-
"@deepseek-ai/dsh-session-persistence": "0.2.2-rc.
|
|
141
|
-
"@deepseek-ai/dsh-session-projection": "0.2.2-rc.
|
|
142
|
-
"@deepseek-ai/dsh-session-query": "0.2.2-rc.
|
|
143
|
-
"@deepseek-ai/dsh-session-title": "0.2.2-rc.
|
|
144
|
-
"@deepseek-ai/dsh-settings": "0.2.2-rc.
|
|
145
|
-
"@deepseek-ai/dsh-skill": "0.2.2-rc.
|
|
146
|
-
"@deepseek-ai/dsh-storage": "0.2.2-rc.
|
|
147
|
-
"@deepseek-ai/dsh-storage-domain": "0.2.2-rc.
|
|
148
|
-
"@deepseek-ai/dsh-subagent": "0.2.2-rc.
|
|
149
|
-
"@deepseek-ai/dsh-system-prompt": "0.2.2-rc.
|
|
150
|
-
"@deepseek-ai/dsh-timeout": "0.2.2-rc.
|
|
116
|
+
"@deepseek-ai/dsh-agent": "0.2.2-rc.5",
|
|
117
|
+
"@deepseek-ai/dsh-agent-default-model": "0.2.2-rc.5",
|
|
118
|
+
"@deepseek-ai/dsh-api-gateway": "0.2.2-rc.5",
|
|
119
|
+
"@deepseek-ai/dsh-api-session-controller": "0.2.2-rc.5",
|
|
120
|
+
"@deepseek-ai/dsh-atomic-write": "0.2.2-rc.5",
|
|
121
|
+
"@deepseek-ai/dsh-attachment": "0.2.2-rc.5",
|
|
122
|
+
"@deepseek-ai/dsh-client-connection": "0.2.2-rc.5",
|
|
123
|
+
"@deepseek-ai/dsh-client-locale": "0.2.2-rc.5",
|
|
124
|
+
"@deepseek-ai/dsh-client-ui-conversation": "0.2.2-rc.5",
|
|
125
|
+
"@deepseek-ai/dsh-client-ui-layout": "0.2.2-rc.5",
|
|
126
|
+
"@deepseek-ai/dsh-client-ui-primitives": "0.2.2-rc.5",
|
|
127
|
+
"@deepseek-ai/dsh-client-ui-renderer": "0.2.2-rc.5",
|
|
128
|
+
"@deepseek-ai/dsh-client-ui-session": "0.2.2-rc.5",
|
|
129
|
+
"@deepseek-ai/dsh-client-ui-settings": "0.2.2-rc.5",
|
|
130
|
+
"@deepseek-ai/dsh-client-ui-sidebar": "0.2.2-rc.5",
|
|
131
|
+
"@deepseek-ai/dsh-client-ui-slots": "0.2.2-rc.5",
|
|
132
|
+
"@deepseek-ai/dsh-client-ui-theme": "0.2.2-rc.5",
|
|
133
|
+
"@deepseek-ai/dsh-file-reference": "0.2.2-rc.5",
|
|
134
|
+
"@deepseek-ai/dsh-home-paths": "0.2.2-rc.5",
|
|
135
|
+
"@deepseek-ai/dsh-host-webserver": "0.2.2-rc.5",
|
|
136
|
+
"@deepseek-ai/dsh-llm": "0.2.2-rc.5",
|
|
137
|
+
"@deepseek-ai/dsh-native-command": "0.2.2-rc.5",
|
|
138
|
+
"@deepseek-ai/dsh-sandbox": "0.2.2-rc.5",
|
|
139
|
+
"@deepseek-ai/dsh-scope": "0.2.2-rc.5",
|
|
140
|
+
"@deepseek-ai/dsh-session": "0.2.2-rc.5",
|
|
141
|
+
"@deepseek-ai/dsh-session-log-export": "0.2.2-rc.5",
|
|
142
|
+
"@deepseek-ai/dsh-session-persistence": "0.2.2-rc.5",
|
|
143
|
+
"@deepseek-ai/dsh-session-projection": "0.2.2-rc.5",
|
|
144
|
+
"@deepseek-ai/dsh-session-query": "0.2.2-rc.5",
|
|
145
|
+
"@deepseek-ai/dsh-session-title": "0.2.2-rc.5",
|
|
146
|
+
"@deepseek-ai/dsh-settings": "0.2.2-rc.5",
|
|
147
|
+
"@deepseek-ai/dsh-skill": "0.2.2-rc.5",
|
|
148
|
+
"@deepseek-ai/dsh-storage": "0.2.2-rc.5",
|
|
149
|
+
"@deepseek-ai/dsh-storage-domain": "0.2.2-rc.5",
|
|
150
|
+
"@deepseek-ai/dsh-subagent": "0.2.2-rc.5",
|
|
151
|
+
"@deepseek-ai/dsh-system-prompt": "0.2.2-rc.5",
|
|
152
|
+
"@deepseek-ai/dsh-timeout": "0.2.2-rc.5",
|
|
151
153
|
"@types/node": "^24.3.0",
|
|
152
154
|
"@types/qrcode": "^1.5.5",
|
|
153
155
|
"@types/react": "~18.3.1",
|
|
@@ -164,5 +166,7 @@
|
|
|
164
166
|
"bugs": {
|
|
165
167
|
"url": "https://github.com/donoteatme/dsh-local-link/issues"
|
|
166
168
|
},
|
|
167
|
-
"homepage": "https://github.com/donoteatme/dsh-local-link#readme"
|
|
169
|
+
"homepage": "https://github.com/donoteatme/dsh-local-link#readme",
|
|
170
|
+
"readme": "# dsh-local-link\n\n**English** | [中文](README.zh.md) | [Русский](README.ru.md)\n\n[](https://github.com/donoteatme/dsh-local-link/actions/workflows/ci.yml)\n[](https://www.npmjs.com/package/dsh-local-link)\n[](https://www.npmjs.com/package/dsh-local-link)\n[](https://awesome-dsh-plugin.com/p/donoteatme/dsh-local-link/)\n[](https://dsh.market/)\n[](LICENSE)\n\nUse the same [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) Web session from a phone, tablet, or another computer on your trusted private network. `dsh-local-link` adds one-time QR pairing and a responsive Mobile View to the stock DSH client—without a hosted relay, cloud account, native app, replacement chat UI, or second workspace picker.\n\nOpen `Local access`, scan the QR code, and the paired browser arrives at the desktop's currently selected Harness session with the same live conversation, permissions, workspaces, and plugin surfaces.\n\nLocal Link `1.2.7` supports DeepSeek Harness `0.2.2-rc.5` and the earlier Hosts declared in `engines.dsh`. It reorganizes the stock Web interface into responsive drawers, compact session controls, and touch-friendly actions while keeping the same client, session, plugin slots, permissions, and live agent stream.\n\n> **Security boundary:** the gateway uses plain HTTP and is intended only for a trusted private network. Do not expose its port to the internet or use it on public Wi-Fi.\n\n<p align=\"center\">\n <img src=\"docs/images/local-access-qr.jpg\" width=\"960\" alt=\"DeepSeek Harness with dsh-local-link open: one-time QR pairing to the current stock Harness session\">\n</p>\n\n<p align=\"center\"><sub>One Harness session, paired directly across the trusted LAN.</sub></p>\n\n## Features and scope\n\nLocal Link is intentionally a small LAN companion for the existing Harness Web client, not a general remote-access platform. Its purpose is to make one path dependable: open the Harness instance already running on a computer from another trusted device on the same private network, then use the same sessions and interface in a browser.\n\nDevelopment stays focused on:\n\n- reliable same-LAN browser access to the current Harness Host;\n- short-lived invitations and understandable paired-device lifecycle controls;\n- responsive presentation of the stock client without duplicating Harness business logic;\n- compatibility with registered Harness views, slots, permissions, themes, and session state;\n- accessibility, localization, bounded diagnostics, and security hardening inside that boundary.\n\nThe following are deliberate non-goals:\n\n- public-internet exposure, hosted relays, managed tunnels, or cloud accounts;\n- a separate native phone or desktop application;\n- a replacement chat client or fork of the Harness interface;\n- independent workspace, file, or session synchronization outside Harness;\n- a general-purpose remote extension runtime unrelated to opening the current Web UI.\n\nThis does not mean the plugin is finished or frozen. It means future changes should make the local browser path simpler, safer, more compatible, or easier to diagnose instead of widening the product into a different class of system.\n\n## Install\n\n### npm — recommended\n\nStop a running `dsh web` process, install the plugin into the Web profile, then start Harness again:\n\n```shell\ndsh plugin --profile web add dsh-local-link\ndsh web\n```\n\n### Git clone — development checkout\n\nRequirements for this checkout: Git, Node.js 24.9+, Corepack, and a global `dsh` installation compatible with the package's declared `engines.dsh` range. Harness `0.2.2` requires Node.js 24.9+; the plugin retains its Node.js 22.19 baseline for older declared Hosts.\n\n```shell\ngit clone https://github.com/donoteatme/dsh-local-link.git\ncd dsh-local-link\ncorepack pnpm install --frozen-lockfile\nnpm run verify\ndsh plugin --profile web add .\ndsh web\n```\n\nThe profile points at the checkout, so rebuild after changing client code and restart `dsh web` after Host-side changes.\n\n## Compatibility\n\nLocal Link `1.2.7` is built and checked against DeepSeek Harness `0.2.2-rc.5`, including ordinary plugin startup without a version exemption. Its mobile adapter supports the native sidebar mask and navigation lifecycle. The gateway recognizes both legacy dotted and current slash-based API names, while native app launching and Host administration remain available only on the Harness computer. Existing `webStartup` / `webRuntime`, public Session scopes, and native Settings navigation integrations are retained.\n\nThe installable DeepSeek Harness range is declared in `package.json` through `engines.dsh`. Compatibility is checked against exact releases—not inferred from a successful installation or a moving dist-tag.\n\nAcceptance on `0.2.2-rc.5` covers pairing, selected-chat QR handoff, authenticated HTTP/WebSocket access, immediate socket closure on revoke, Host-only API and native-app restrictions, new-chat creation, paired-device controls, and mobile layouts at 320–768 CSS pixels in EN and ZH. These checks used isolated profiles with fictional data and a loopback gateway. Earlier Host declarations retain the historical acceptance recorded in the [changelog](CHANGELOG.md); the full old-version matrix and physical-phone checks were not rerun. Mobile microphone capture over plain LAN HTTP remains unsupported; this release adds neither HTTPS nor voice input.\n\n## Use\n\n### Open Harness on another device\n\n1. Open the session you want on the computer.\n2. Click `Local access` at the bottom of the Harness sidebar.\n3. Scan the QR code or copy the one-time link to another device on the same network.\n4. The first browser to use the invitation opens the stock Harness client at the selected session. Host-level administration that Harness reserves for loopback remains unavailable remotely.\n\nThe invitation is one-use, expires after five minutes by default, and is replaced immediately when `Generate another code` is selected. After successful pairing, the QR panel closes automatically. Reopen `Local access` to generate a fresh invitation for another browser or device.\n\nPhone and tablet browsers automatically receive Mobile View when the viewport is at most 834 CSS pixels wide. The same responsive behavior can be previewed with browser device emulation; no URL parameter, user-agent switch, or second client is involved.\n\n## Mobile View\n\nThe stock Harness Web interface is difficult to operate on a phone: persistent desktop navigation consumes the viewport, session controls compete with the conversation title, several actions depend on hover or long press, and subagent information is too dense for a narrow screen. Mobile View makes that existing interface usable without introducing a second client or duplicating Harness business logic.\n\n| Stock narrow-screen behavior | Mobile View in `1.2.x` |\n| --- | --- |\n| Desktop navigation competes with the conversation | Workspace and session navigation opens as a dismissible left drawer |\n| Session metadata crowds the header | Context, model, access, preset, activity, and export move into a compact right drawer |\n| Subagent details are difficult to scan or reach | On 0.1.5, a composer chip opens the catalog in a bottom sheet; on 0.1.7 and 0.2, Harness owns its header catalog and navigation |\n| Hover-oriented session and workspace actions | Overflow actions remain visible and touch-accessible |\n| Session changes can summon the software keyboard | Automatic composer focus is suppressed while intentional input focus still works |\n| Desktop spacing ignores phone safe areas | Header, composer, tabs, media, overlays, and scrolling adapt to narrow viewports |\n\nThe implementation changes presentation, not Harness ownership or behavior:\n\n- the native workspace/session browser becomes a left drawer;\n- dynamic Chat, Trajectory, composer, overlay, and third-party plugin slots remain intact;\n- Current session opens from the header with context breakdown, model, workspace access, preset, activity, and session-log download;\n- on mobile, the duplicate stock context meter below the chat and the Host-app opener (Explorer/VS Code/Rider) are hidden; the context meter remains available on desktop, and native app launching remains available on the loopback desktop only;\n- on 0.1.5, child-agent status opens the nested catalog in a touch-friendly bottom sheet; on 0.1.7 and 0.2, the native Harness subagent header action owns that navigation;\n- the Harness theme service powers a compact sun/moon action;\n- desktop-only Settings and the nested Local access action are omitted from mobile navigation, while the appearance action remains available;\n- session and active-workspace menus stay immediately available on touch screens;\n- safe areas, scrollable tabs, bounded media, and virtual-keyboard behavior are adapted for narrow viewports;\n- plugin-owned modal drawers contain keyboard focus and return it to the invoking control when closed;\n- existing workspaces remain available, while the misleading remote `Add workspace` directory picker is omitted.\n\nThese dark-theme previews were captured from real Harness `0.2.2-rc.1` browser sessions: mobile frames are `430 × 932`, desktop frames are `1440 × 1000`. The isolated profiles contain fictional workspaces, conversations, models, devices, and usage only. The Chinese README has its own Simplified Chinese captures; Russian documentation shares the English images. Subagents use the native Harness header catalog.\n\n| Navigation | Current session | Subagents | Conversation |\n| :---: | :---: | :---: | :---: |\n| <img src=\"docs/images/mobile-navigation.png\" width=\"210\" alt=\"Dark Mobile View navigation drawer with a synthetic workspace and session\"> | <img src=\"docs/images/mobile-session-info.png\" width=\"210\" alt=\"Dark Mobile View Current session drawer with synthetic model, workspace access, statistics, and session log data\"> | <img src=\"docs/images/mobile-subagents.png\" width=\"210\" alt=\"Native dark Harness header catalog with two synthetic child agents\"> | <img src=\"docs/images/mobile-chat.png\" width=\"210\" alt=\"Dark Mobile View Harness conversation with native message actions and one-line composer controls\"> |\n\n### Permissions\n\nThe remote browser inherits the selected Harness session's **Read only**, **Workspace write**, or **Full access** authority. Mobile View displays that value but does not create or weaken a permission layer. This applies to ordinary session operations; Settings, credentials, native Host actions, and agent-preset authoring remain loopback-only. Hiding `Add workspace` is a usability constraint, not an authorization boundary.\n\nThe responsive enhancements target viewports from 360 through 834 CSS pixels wide. The release matrix defines checks at `360 × 800`, `390 × 844`, `430 × 932`, and `768 × 1024`; release acceptance also requires portrait and landscape checks on a real phone. See [Mobile View](docs/MOBILE_VIEW.md) for behavior, theme persistence, compatibility surfaces, and the complete acceptance checklist.\n\n### Manage trusted browsers\n\nOn the Harness computer, use `Paired devices` in the QR panel or open `Settings → Local access`. Each new browser starts as `My device`; its subtitle is detected automatically, for example `Phone · Chrome`, `Tablet · Safari`, or `Computer · Edge`.\n\n- `Rename` changes display metadata only.\n- `Revoke` invalidates the browser credential and immediately closes its open Local Link WebSocket connections.\n- A cleared cookie, private window, new browser profile, or revoked device needs a new invitation.\n\nBrowsers do not reliably distinguish laptops from desktop computers, so both are shown as `Computer`.\n\n<p align=\"center\">\n <img src=\"docs/images/local-access-devices.jpg\" width=\"960\" alt=\"DeepSeek Harness Settings opened directly on the compact Local access paired-device list\">\n</p>\n\nExpand `Diagnostics` on the same Settings page to inspect the most recent local gateway events. `Copy report` produces issue-ready JSON and `Clear` removes the local history. The report contains event codes, timestamps, severity, and a small allowlisted context only; it never includes pairing tokens, cookies, IP addresses, device or session IDs, device names, request paths, prompts, conversations, or project files.\n\n<p align=\"center\">\n <img src=\"docs/images/local-access-diagnostics.jpg\" width=\"960\" alt=\"DeepSeek Harness Local access settings with the native-style Diagnostics panel expanded\">\n</p>\n\n## Why it stays small\n\n- **Stock Harness UI:** the plugin opens the existing Web client and live agent stream.\n- **Local only:** one private-network gateway forwards to the loopback Harness Host.\n- **Two runtime dependencies:** configuration schema support and QR generation.\n- **No fingerprinting:** access is a random per-browser credential, not a device identity guess.\n- **Native extension points:** sidebar and Settings content use Harness slots and locale services.\n- **Native responsive enhancement:** the shipped Harness AppFrame stays mounted; registered conversation views and overlays remain dynamic.\n- **JSON localization:** all visible plugin copy lives in matching locale dictionaries.\n- **Local diagnostics:** a bounded, redacted event history helps debug installs without analytics or an external collector.\n\n## How it works\n\n```text\nDesktop browser on 127.0.0.1:3080\n └─ Local access → one-use invitation\n │\nPhone / tablet / computer on the private LAN\n └─ 192.168.x.x:3088 → network + Host validation\n → pairing or device-cookie validation\n → HTTP / WebSocket proxy\n → 127.0.0.1:3080 (the same Harness Host)\n```\n\nThe gateway does not create a second Harness session. During first connection it transfers the desktop browser's current session selection to the new browser origin; session data and ongoing conversation events still come from the same Host.\n\nAuthorization uses a 256-bit random cookie credential. Only its SHA-256 hash is stored. The editable name and detected device/browser text never grant access.\n\nThe LAN authority is declared through Harness's official connection `trustedHosts` contract. This enables authenticated session API and WebSocket traffic without pretending that the phone is loopback. Harness `0.1.2-rc.1` and the verified `0.1.5` and `0.1.7` builds authenticate the transport as a whole, so Local Link itself rejects the configuration, credential, native Host-action, and agent-preset-authoring RPCs that earlier supported Harness builds kept loopback-only.\n\n## Configuration\n\nThe bundled profile patch installs conservative defaults:\n\n| Option | Default | Purpose |\n| --- | --- | --- |\n| `listenHost` | `0.0.0.0` | Listen on local interfaces; request validation still accepts only private/loopback sources. |\n| `listenPort` | `3088` | LAN gateway port. |\n| `upstreamOrigin` | `http://127.0.0.1:3080` | Existing loopback Harness Web server. |\n| `accessMode` | `pairing` | Require a one-use invitation and device cookie. |\n| `pairingTtlSeconds` | `300` | Invitation lifetime. |\n| `deviceTtlDays` | `90` | Remembered-browser lifetime. |\n| `diagnosticsEnabled` | `true` | Keep the bounded local diagnostic history. |\n| `diagnosticsMaxEntries` | `15` | Maximum retained events (`5`–`200`). |\n| `diagnosticsFile` | next to `stateFile` | Local JSON event store; the bundled profile uses `~/.dsh/local-link/diagnostics.json`. |\n\n`listenHost` accepts only `0.0.0.0` or an explicit private/loopback IP literal. Public listener addresses are rejected during startup; this configuration guard complements, rather than replaces, the operating-system firewall.\n\n`trusted-lan` disables per-device authorization and should be reserved for isolated development networks. `pairing` is the supported default because a connected Harness browser can read files, submit prompts, approve actions, and trigger commands.\n\nThe plugin never creates firewall rules. If Windows prompts for network access, allow only the **Private** network profile and never forward port `3088` on the router.\n\n## Troubleshooting and diagnostics\n\nDiagnostics are a local, event-driven history of failures—not a request log. The plugin retains 15 events by default, shows the newest 12, coalesces identical five-second bursts, and records nothing for successful starts, requests, pairing, copies, renames, or revocations.\n\nFor support:\n\n1. Reproduce the failed action once.\n2. Open `Settings → Local access → Diagnostics`.\n3. Click `Refresh` if the panel was already open.\n4. Use the newest stable event code to identify the failed boundary.\n5. Click `Copy report`, review the JSON, and attach it to an issue if needed.\n\nThe report never includes secrets, addresses, IDs, names, URLs, paths, prompts, conversations, or project data and is never uploaded automatically. See the [event reference and first checks](docs/DIAGNOSTICS.md) for every tracked failure.\n\n## Localization\n\nHarness's active language selects the plugin dictionary; the plugin has no separate language switch.\n\nThe minimal automatic pairing page loads before Harness locale services are available. It reuses the same dictionaries and selects English or Chinese from the connecting browser's language list; English is the fallback.\n\n| Language | Dictionary | Status |\n| --- | --- | --- |\n| English | `src/locales/en.json` | Included |\n| Chinese | `src/locales/zh.json` | Included |\n\nDictionary keys are checked for parity in tests. To add a locale, copy `en.json`, translate values without changing keys, register the locale ID in `src/client.tsx`, extend the pre-client pairing-page language map in `src/gateway/pair-page.ts`, and run `npm test`.\n\n## Development\n\n```shell\ncorepack pnpm install --frozen-lockfile\nnpm run typecheck\nnpm test\nnpm run build\nnpm run verify\n```\n\nProject documentation:\n\n- [Architecture and compatibility boundaries](docs/ARCHITECTURE.md)\n- [Mobile View behavior and release matrix](docs/MOBILE_VIEW.md)\n- [Local diagnostics and event codes](docs/DIAGNOSTICS.md)\n- [Security model](docs/SECURITY.md)\n- [Contributing](CONTRIBUTING.md)\n- [Security reporting](SECURITY.md)\n\n## Known limitations\n\n- LAN traffic is not encrypted; the current gateway uses plain HTTP.\n- Revocation blocks new requests and reconnects and terminates every open Local Link WebSocket authenticated by the revoked device.\n- A light/dark choice made from a remote browser is page-scoped in the supported Harness builds; reload returns to the Host preference and resolves `system` against the remote device.\n- Invitations use the highest-ranked private IPv4 interface detected at startup; choosing among multiple LAN interfaces is not exposed yet.\n- The shortcut that opens a specific Settings section uses a small semantic compatibility bridge because Harness does not expose a general settings-navigation service.\n- Harness's footer-action container needs a compatibility layout rule when the full-width Cordis action is present.\n- Mobile View targets viewports from 360 CSS pixels wide, but third-party fixed-width views, virtual keyboards, orientation changes, split-screen browsers, and operating-system text scaling still require real-device acceptance.\n- Plugin-owned buttons and text inputs use Harness `Button` and `Input` primitives and their semantic variants. The supported Harness builds do not expose a complete public responsive-shell, spacing, or radius contract, so mobile geometry and responsive compositions remain documented design-system compatibility risks; icon export changes are handled by a version-tolerant adapter.\n\n## Development disclosure\n\nThe initial implementation and documentation were developed collaboratively with OpenAI Codex. Changes remain subject to maintainer review, automated tests, security review, and the same contribution requirements as human-authored changes. No runtime AI service, telemetry, or generated-code dependency is included in the package.\n\n## License\n\n[MIT](LICENSE) © 2026 dsh-local-link contributors.\n",
|
|
171
|
+
"readmeFilename": "README.md"
|
|
168
172
|
}
|