dsh-local-link 0.2.0 → 1.0.0
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 +28 -0
- package/README.md +51 -18
- package/cordis.patch.yml +1 -1
- package/docs/ARCHITECTURE.md +9 -6
- package/docs/COMPATIBILITY.md +45 -0
- package/docs/DIAGNOSTICS.md +2 -1
- package/docs/SECURITY.md +2 -1
- package/lib/client.js +10 -6
- package/lib/client.js.map +1 -1
- package/lib/index.mjs +77 -13
- package/package.json +6 -6
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,34 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project are documented here.
|
|
4
4
|
|
|
5
|
+
## 1.0.0 — 2026-08-29
|
|
6
|
+
|
|
7
|
+
The first stable Local Link release. It keeps the focused same-LAN access and
|
|
8
|
+
responsive Harness-client scope established by the `0.2.x` previews, with an
|
|
9
|
+
exact compatibility matrix covering the current verified Harness release and
|
|
10
|
+
prerelease targets.
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- Added the native browser-authentication handoff required by DeepSeek Harness `0.1.2-alpha.1`, while preserving the separate Local Link device credential and the older release-candidate flow.
|
|
15
|
+
- Kept alpha boot-manifest batches aligned when withholding the remote native directory picker, and allowed the alpha's exact `/api/remote.mux` live-stream endpoint without widening the WebSocket allowlist.
|
|
16
|
+
- Made Current session tolerate alpha conversation summaries that omit the legacy `nodes` collection while continuing to resolve the selected model through Harness's native model directory.
|
|
17
|
+
|
|
18
|
+
### Validated
|
|
19
|
+
|
|
20
|
+
- Verified pairing, current-session opening, live conversation streaming, responsive navigation, Current session, and subagent surfaces in an isolated checkout of DeepSeek Harness `0.1.2-alpha.1`.
|
|
21
|
+
- Reverified Local Access, one-use QR regeneration, and responsive navigation against DeepSeek Harness `0.1.1-rc.2`, `0.1.1-rc.1`, and `0.1.0-rc.8` using the same release source.
|
|
22
|
+
|
|
23
|
+
## 0.2.1 — 2026-08-29
|
|
24
|
+
|
|
25
|
+
### Fixed
|
|
26
|
+
|
|
27
|
+
- Quoted the `trustedHosts` JavaScript expression in the bundled Cordis overlay so a clean npm installation parses and boots with the strict DSH patch-list YAML schema.
|
|
28
|
+
|
|
29
|
+
### Validated
|
|
30
|
+
|
|
31
|
+
- Documented supported and verified Harness versions in a newest-first compatibility matrix.
|
|
32
|
+
|
|
5
33
|
## 0.2.0 — 2026-08-29
|
|
6
34
|
|
|
7
35
|
### Added
|
package/README.md
CHANGED
|
@@ -1,16 +1,39 @@
|
|
|
1
1
|
# dsh-local-link
|
|
2
2
|
|
|
3
|
-
[](https://github.com/donoteatme/dsh-local-link/actions/workflows/ci.yml)
|
|
4
4
|
[](https://www.npmjs.com/package/dsh-local-link)
|
|
5
|
+
[](https://awesome-dsh-plugin.com)
|
|
5
6
|
[](LICENSE)
|
|
6
7
|
|
|
7
|
-
Lightweight, self-hosted [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin for paired LAN access and a practical Mobile View of the
|
|
8
|
+
Lightweight, self-hosted [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin for paired LAN access and a practical Mobile View of the existing DSH Web client.
|
|
8
9
|
|
|
9
10
|
Open `Local access`, scan one QR code, and continue the desktop's currently selected Harness session from a phone, tablet, or another computer on the same private network. There is no hosted relay, tunnel provider, native application, account, replacement chat UI, or second workspace picker.
|
|
10
11
|
|
|
11
|
-
|
|
12
|
+
The stable `1.0.0` release also addresses the stock Web client's desktop-first behavior on narrow touch screens. It reorganizes the existing Harness interface into responsive drawers, compact session controls, and touch-friendly actions while keeping the same client, session, plugin slots, permissions, and live agent stream.
|
|
12
13
|
|
|
13
|
-
> **
|
|
14
|
+
> **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.
|
|
15
|
+
|
|
16
|
+
## Focused product scope
|
|
17
|
+
|
|
18
|
+
Local 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.
|
|
19
|
+
|
|
20
|
+
Development stays focused on:
|
|
21
|
+
|
|
22
|
+
- reliable same-LAN browser access to the current Harness Host;
|
|
23
|
+
- short-lived invitations and understandable paired-device lifecycle controls;
|
|
24
|
+
- responsive presentation of the stock client without duplicating Harness business logic;
|
|
25
|
+
- compatibility with registered Harness views, slots, permissions, themes, and session state;
|
|
26
|
+
- accessibility, localization, bounded diagnostics, and security hardening inside that boundary.
|
|
27
|
+
|
|
28
|
+
The following are deliberate non-goals:
|
|
29
|
+
|
|
30
|
+
- public-internet exposure, hosted relays, managed tunnels, or cloud accounts;
|
|
31
|
+
- a separate native phone or desktop application;
|
|
32
|
+
- a replacement chat client or fork of the Harness interface;
|
|
33
|
+
- independent workspace, file, or session synchronization outside Harness;
|
|
34
|
+
- a general-purpose remote extension runtime unrelated to opening the current Web UI.
|
|
35
|
+
|
|
36
|
+
This 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.
|
|
14
37
|
|
|
15
38
|
## Install
|
|
16
39
|
|
|
@@ -25,10 +48,10 @@ dsh web
|
|
|
25
48
|
|
|
26
49
|
### Git clone — development checkout
|
|
27
50
|
|
|
28
|
-
Requirements: Git, Node.js 22.19+ or 24+, Corepack, and a global `dsh` installation running DeepSeek Harness
|
|
51
|
+
Requirements: Git, Node.js 22.19+ or 24+, Corepack, and a global `dsh` installation running a verified DeepSeek Harness version from the compatibility table below.
|
|
29
52
|
|
|
30
53
|
```shell
|
|
31
|
-
git clone https://github.com/
|
|
54
|
+
git clone https://github.com/donoteatme/dsh-local-link.git
|
|
32
55
|
cd dsh-local-link
|
|
33
56
|
corepack pnpm install --frozen-lockfile
|
|
34
57
|
npm run verify
|
|
@@ -38,6 +61,19 @@ dsh web
|
|
|
38
61
|
|
|
39
62
|
The profile points at the checkout, so rebuild after changing client code and restart `dsh web` after Host-side changes.
|
|
40
63
|
|
|
64
|
+
## Compatibility
|
|
65
|
+
|
|
66
|
+
Compatibility is checked against exact DeepSeek Harness versions, including the real Web client, Local Access pairing flow, responsive navigation, Current session, and subagent surfaces. A successful package installation alone is not treated as compatibility proof.
|
|
67
|
+
|
|
68
|
+
| DeepSeek Harness | Local Link status | Notes |
|
|
69
|
+
| --- | --- | --- |
|
|
70
|
+
| `0.1.2-alpha.1` | **Supported prerelease** | `1.0.0` includes the native browser-authentication and stream compatibility required by this alpha. |
|
|
71
|
+
| `0.1.1-rc.2` | **Supported baseline** | Primary development and complete repository verification target. |
|
|
72
|
+
| `0.1.1-rc.1` | **Verified** | Core LAN, pairing, session, and Mobile View surfaces checked. |
|
|
73
|
+
| `0.1.0-rc.8` | **Verified** | Core LAN, pairing, session, and Mobile View surfaces checked. |
|
|
74
|
+
|
|
75
|
+
Versions older than `0.1.0-rc.8` are untested and unsupported. Every newer Harness prerelease is checked independently before support is claimed. See the full [compatibility policy](docs/COMPATIBILITY.md).
|
|
76
|
+
|
|
41
77
|
## Use
|
|
42
78
|
|
|
43
79
|
### Open Harness on another device
|
|
@@ -45,7 +81,7 @@ The profile points at the checkout, so rebuild after changing client code and re
|
|
|
45
81
|
1. Open the session you want on the computer.
|
|
46
82
|
2. Click `Local access` at the bottom of the Harness sidebar.
|
|
47
83
|
3. Scan the QR code or copy the one-time link to another device on the same network.
|
|
48
|
-
4. The first browser to use the invitation opens the
|
|
84
|
+
4. 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.
|
|
49
85
|
|
|
50
86
|
The invitation is one-use, expires after five minutes by default, and is replaced immediately when `Generate another code` is selected.
|
|
51
87
|
|
|
@@ -59,7 +95,7 @@ Phone and tablet browsers automatically receive Mobile View when the viewport is
|
|
|
59
95
|
|
|
60
96
|
The 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.
|
|
61
97
|
|
|
62
|
-
| Stock narrow-screen behavior | Mobile View in `0.
|
|
98
|
+
| Stock narrow-screen behavior | Mobile View in `1.0.0` |
|
|
63
99
|
| --- | --- |
|
|
64
100
|
| Desktop navigation competes with the conversation | Workspace and session navigation opens as a dismissible left drawer |
|
|
65
101
|
| Session metadata crowds the header | Context, model, access, preset, activity, and export move into a compact right drawer |
|
|
@@ -75,6 +111,7 @@ The implementation changes presentation, not Harness ownership or behavior:
|
|
|
75
111
|
- Current session opens from the header with context breakdown, model, workspace access, preset, activity, and session-log download;
|
|
76
112
|
- child-agent status shows total and active counts, then opens the native nested catalog as a touch-friendly bottom sheet;
|
|
77
113
|
- the Harness theme service powers a compact sun/moon action;
|
|
114
|
+
- desktop-only Settings and the nested Local access action are omitted from mobile navigation, while the appearance action remains available;
|
|
78
115
|
- session and active-workspace menus stay immediately available on touch screens;
|
|
79
116
|
- safe areas, scrollable tabs, bounded media, and virtual-keyboard behavior are adapted for narrow viewports;
|
|
80
117
|
- plugin-owned modal drawers contain keyboard focus and return it to the invoking control when closed;
|
|
@@ -88,13 +125,13 @@ These previews are captured from the running Harness client at a `430 × 932` vi
|
|
|
88
125
|
|
|
89
126
|
### Permissions
|
|
90
127
|
|
|
91
|
-
The 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. Hiding `Add workspace` is a usability constraint, not an authorization boundary.
|
|
128
|
+
The 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.
|
|
92
129
|
|
|
93
|
-
The responsive enhancements target viewports from 360 through 834 CSS pixels wide. The release matrix
|
|
130
|
+
The 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.
|
|
94
131
|
|
|
95
132
|
### Manage trusted browsers
|
|
96
133
|
|
|
97
|
-
|
|
134
|
+
On 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`.
|
|
98
135
|
|
|
99
136
|
- `Rename` changes display metadata only.
|
|
100
137
|
- `Revoke` invalidates the browser credential for subsequent HTTP requests and reconnects.
|
|
@@ -204,6 +241,7 @@ npm run verify
|
|
|
204
241
|
Project documentation:
|
|
205
242
|
|
|
206
243
|
- [Architecture and compatibility boundaries](docs/ARCHITECTURE.md)
|
|
244
|
+
- [Verified DeepSeek Harness compatibility](docs/COMPATIBILITY.md)
|
|
207
245
|
- [Mobile View behavior and release matrix](docs/MOBILE_VIEW.md)
|
|
208
246
|
- [Local diagnostics and event codes](docs/DIAGNOSTICS.md)
|
|
209
247
|
- [Security model](docs/SECURITY.md)
|
|
@@ -214,9 +252,10 @@ Project documentation:
|
|
|
214
252
|
|
|
215
253
|
- LAN traffic is not encrypted in the current preview gateway.
|
|
216
254
|
- Revocation blocks new requests and reconnects but does not yet terminate an already-open WebSocket.
|
|
255
|
+
- A light/dark choice made from a remote browser is memory-backed by Harness `0.1.1-rc.2`; reload returns to the Host preference and resolves `system` against the remote device.
|
|
256
|
+
- Invitations use the highest-ranked private IPv4 interface detected at startup; choosing among multiple LAN interfaces is not exposed yet.
|
|
217
257
|
- The shortcut that opens a specific Settings section uses a small semantic compatibility bridge because Harness `0.1.1-rc.2` exposes `openSection` only to onboarding.
|
|
218
258
|
- Harness's footer-action container needs a compatibility layout rule when the full-width Cordis action is present.
|
|
219
|
-
- Compatibility is currently pinned to DeepSeek Harness `0.1.1-rc.2` and must be retested for each supported Harness release.
|
|
220
259
|
- 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.
|
|
221
260
|
- Plugin-owned buttons and text inputs use Harness `Button` and `Input` primitives and their semantic variants. Harness `0.1.1-rc.2` still has no public responsive-shell, spacing, or radius contract, so mobile geometry, responsive compositions, and the few missing primitive icons remain documented design-system compatibility risks.
|
|
222
261
|
|
|
@@ -224,12 +263,6 @@ Project documentation:
|
|
|
224
263
|
|
|
225
264
|
The 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.
|
|
226
265
|
|
|
227
|
-
## Acknowledgements
|
|
228
|
-
|
|
229
|
-
The mobile UX research included the MIT-licensed [DSH Mobile](https://github.com/sorsama/deepseek-harness-mobile) project by its contributors. Its mobile navigation, session-details, subagent, and activity-status presentation helped inform the interaction direction used here.
|
|
230
|
-
|
|
231
|
-
No DSH Mobile source code or assets are included in this package. Local Link implements its Mobile View independently in TypeScript and React, using the stock Harness client, design primitives, services, and plugin slots instead of shipping a replacement Android client.
|
|
232
|
-
|
|
233
266
|
## License
|
|
234
267
|
|
|
235
268
|
[MIT](LICENSE) © 2026 dsh-local-link contributors.
|
package/cordis.patch.yml
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
- id: connection
|
|
6
6
|
inject: [webRuntime, localLinkGateway]
|
|
7
7
|
config:
|
|
8
|
-
trustedHosts: !!js [...ctx.webRuntime.trustedHosts, ...ctx.localLinkGateway.trustedHosts]
|
|
8
|
+
trustedHosts: !!js "[...ctx.webRuntime.trustedHosts, ...ctx.localLinkGateway.trustedHosts]"
|
|
9
9
|
|
|
10
10
|
- insert:
|
|
11
11
|
- id: dsh-local-link
|
package/docs/ARCHITECTURE.md
CHANGED
|
@@ -46,6 +46,8 @@ Configuration accepts only the wildcard `0.0.0.0` or an explicit private/loopbac
|
|
|
46
46
|
|
|
47
47
|
After authentication, the gateway forwards the browser's original `Host`, `Origin`, referrer, and fetch-site headers to the loopback Harness listener. The Cordis profile patch supplies the gateway's current LAN authorities to the official connection module through its public `trustedHosts` option. Ordinary Harness API and WebSocket traffic can therefore pass the declared origin check without pretending to be loopback.
|
|
48
48
|
|
|
49
|
+
Harness `0.1.2-alpha.1` additionally requires a native browser-authentication exchange. After Local Link pairing succeeds, the plugin asks the injected Harness connection service for an authenticated URL at the gateway origin, validates that the result stays on that origin, and lets the stock root consume the short-lived token. The gateway forwards Harness authentication cookies but strips its own device cookie before proxying, so the two credentials remain independent. Older release candidates do not expose this service and keep the direct-root redirect.
|
|
50
|
+
|
|
49
51
|
The connection module separately rechecks privileged configuration, credential, native Host-action, and agent-preset-authoring methods with an empty trust extension. Those operations remain loopback-only. `tests/trust-boundary.test.ts` exercises this split against the real connection package: a trusted gateway authority reaches ordinary dispatch while every privileged method returns `403`.
|
|
50
52
|
|
|
51
53
|
### Authentication state
|
|
@@ -90,7 +92,7 @@ The compact appearance button is visually placed in the stock sidebar brand row
|
|
|
90
92
|
|
|
91
93
|
Theme persistence remains entirely owned by Harness SettingsScope. In Harness `0.1.1-rc.2`, the client Settings binder selects durable `host` storage only for loopback connections and `memory` storage for non-loopback connections. A phone can therefore change the theme for its current page, but reload creates a new remote SettingsScope and returns to the durable host preference—often `system`, which is then resolved using the phone's own color scheme. Local Link does not impersonate a loopback client and does not add a competing cookie or browser-storage preference. Persistent per-device theme selection requires a safe client/device preference scope from Harness.
|
|
92
94
|
|
|
93
|
-
The authenticated gateway manifest omits Harness's host directory-picker client capability. The stock WorkspaceBrowser already treats `sidebar.workspaces.directoryFlow` as optional, so it naturally keeps Search, View options, existing workspaces, and sessions while withholding `Add workspace` from every remote gateway viewport. Loopback desktop boot entries are unchanged; no DOM selector or duplicated workspace browser is involved.
|
|
95
|
+
The authenticated gateway manifest omits Harness's host directory-picker client capability. The stock WorkspaceBrowser already treats `sidebar.workspaces.directoryFlow` as optional, so it naturally keeps Search, View options, existing workspaces, and sessions while withholding `Add workspace` from every remote gateway viewport. In alpha manifests the same entry is removed from the batch activation list without rewriting the server-registered batch URL. Loopback desktop boot entries are unchanged; no DOM selector or duplicated workspace browser is involved.
|
|
94
96
|
|
|
95
97
|
Subagent controls also stay inside the native graph. A mobile-only list entry in `conversation.input.dock` projects the existing `useSessions` catalog into a compact status chip above the composer. The sheet itself is an additive `shell.overlay` entry, while a higher-priority mobile occupant of `conversation.session.header.lineage` removes the desktop dropdown without replacing the session header. Opening and expanding the sheet uses `ctx.sessions.setSubagentCatalogOpen`; selecting a row uses `ctx.sessions.openSubagent`. Closing the sheet or a tree branch releases every corresponding catalog observation. There is no second session store, WebSocket, or data-polling loop. While the sheet is visible, one one-second presentation clock updates displayed activity durations from the already-observed catalog and is cleared when the sheet closes.
|
|
96
98
|
|
|
@@ -140,10 +142,10 @@ This boundary keeps connection setup in one place and persistent access manageme
|
|
|
140
142
|
2. The Host builds a LAN URL containing the token and current session in the fragment, then renders the same URL as a QR data URL. Neither value reaches the initial HTTP request.
|
|
141
143
|
3. The phone opens a minimal automatic connection page. The secret remains in the URL fragment and is not sent in the initial HTTP request.
|
|
142
144
|
4. The page immediately POSTs the token with a coarse device category and browser name; there is no confirmation form and no fingerprinting.
|
|
143
|
-
5. The gateway consumes the token, stores a credential hash, and sets the browser cookie.
|
|
145
|
+
5. The gateway consumes the token, stores a credential hash, and sets the Local Link browser cookie.
|
|
144
146
|
6. The desktop's loopback-only status check observes the consumed token and closes the QR panel.
|
|
145
147
|
7. Before booting Harness, the page writes the selected session into Harness's own `dsh.sessions.current` persisted-selection cell for the LAN browser origin.
|
|
146
|
-
8. The browser redirects to the complete stock Harness root. Harness loads the shared server-side session list and opens the transferred current conversation, whose ordinary WebSocket stream shows live agent activity.
|
|
148
|
+
8. The browser continues through the native Harness browser-authentication handoff when the installed version requires it, then redirects to the complete stock Harness root. Harness loads the shared server-side session list and opens the transferred current conversation, whose ordinary WebSocket stream shows live agent activity.
|
|
147
149
|
|
|
148
150
|
### Normal request
|
|
149
151
|
|
|
@@ -155,7 +157,7 @@ This boundary keeps connection setup in one place and persistent access manageme
|
|
|
155
157
|
|
|
156
158
|
### WebSocket upgrade
|
|
157
159
|
|
|
158
|
-
The same network, Host, and credential checks run before
|
|
160
|
+
The same network, Host, and credential checks run before an exact supported stream path is passed to the upstream server. Release candidates use `/api/events.mux` or `/api/events.host`; `0.1.2-alpha.1` uses `/api/remote.mux`. Query-bearing and arbitrary WebSocket paths remain rejected. Revocation affects new connections; a future milestone will actively close already-open sockets for a revoked device.
|
|
159
161
|
|
|
160
162
|
## Dependency policy
|
|
161
163
|
|
|
@@ -164,17 +166,18 @@ Runtime dependencies are intentionally limited:
|
|
|
164
166
|
- `@deepseek-ai/schemastery`: Cordis-compatible configuration schema.
|
|
165
167
|
- `qrcode`: QR rendering for the desktop sidebar panel.
|
|
166
168
|
|
|
167
|
-
HTTP forwarding and the
|
|
169
|
+
HTTP forwarding and the supported Harness event WebSocket tunnels use Node's built-in `node:http` and `node:net` modules. No general-purpose proxy package is shipped.
|
|
168
170
|
|
|
169
171
|
No service discovery, certificate generator, tunnel client, native application, analytics SDK, remote log collector, or extension runtime is included.
|
|
170
172
|
|
|
171
173
|
## Compatibility strategy
|
|
172
174
|
|
|
173
|
-
The plugin
|
|
175
|
+
The plugin uses DeepSeek Harness `0.1.1-rc.2` as its development baseline and explicitly adapts `0.1.2-alpha.1`. Most integration uses declared package contracts, but several adapters are intentionally version-sensitive:
|
|
174
176
|
|
|
175
177
|
| Adapter | Why it exists | Failure behavior | Removal condition |
|
|
176
178
|
| --- | --- | --- | --- |
|
|
177
179
|
| Connection `trustedHosts` profile patch | Authenticated non-loopback pages need an explicitly declared LAN authority for ordinary API and WebSocket traffic. | An undeclared authority is rejected; privileged RPCs remain loopback-only independently. | Harness exposes a first-class authenticated-gateway registration contract. |
|
|
180
|
+
| Alpha browser-authentication handoff | `0.1.2-alpha.1` requires a native one-time browser token in addition to Local Link device pairing. | An absent or invalid handoff fails closed and records `BROWSER_AUTH_HANDOFF_FAILED`; older release candidates keep their direct-root path. | Harness publishes a stable gateway-authentication contract across releases. |
|
|
178
181
|
| Remote boot capability filter | The native directory picker targets the Host filesystem and is misleading from a remote browser. | If the known picker entries change, `Add workspace` can reappear; server authorization remains unchanged. | Harness exposes a remote-client capability policy. |
|
|
179
182
|
| Settings navigation bridge | The shell keeps `openSection` private outside onboarding. | The shortcut does nothing; ordinary `Settings → Local access` remains available. | Harness exposes general settings navigation. |
|
|
180
183
|
| Footer stack rule | Cordis reserves a full-width cell inside a horizontal list container. | Without it, Local access has zero width while Cordis is mounted. | Harness stacks full-width footer actions or gives entries an explicit layout contract. |
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
# DeepSeek Harness compatibility
|
|
2
|
+
|
|
3
|
+
Local Link extends version-sensitive Harness Host, client-slot, theme, layout,
|
|
4
|
+
session, and Settings contracts. Compatibility is verified against exact Harness
|
|
5
|
+
versions and is never inferred from package installation alone.
|
|
6
|
+
|
|
7
|
+
## Compatibility matrix
|
|
8
|
+
|
|
9
|
+
Last checked on 2026-08-29 with Node.js 22 and Windows using the
|
|
10
|
+
`dsh-local-link@1.0.0` release source. Versions are listed newest first.
|
|
11
|
+
|
|
12
|
+
| DeepSeek Harness | Status | Last checked |
|
|
13
|
+
| --- | --- | --- |
|
|
14
|
+
| `0.1.2-alpha.1` | **Supported prerelease** | 2026-08-29 |
|
|
15
|
+
| `0.1.1-rc.2` | **Supported baseline** | 2026-08-29 |
|
|
16
|
+
| `0.1.1-rc.1` | **Verified** | 2026-08-29 |
|
|
17
|
+
| `0.1.0-rc.8` | **Verified** | 2026-08-29 |
|
|
18
|
+
|
|
19
|
+
Versions older than `0.1.0-rc.8` are untested and unsupported.
|
|
20
|
+
|
|
21
|
+
### Status meanings
|
|
22
|
+
|
|
23
|
+
- **Supported baseline** is the Harness version used for current development
|
|
24
|
+
and the complete repository verification gate.
|
|
25
|
+
- **Supported prerelease** is an exact Harness prerelease included in the
|
|
26
|
+
release gate without implying compatibility with later alpha builds.
|
|
27
|
+
- **Verified** means the published plugin was installed and its core LAN,
|
|
28
|
+
pairing, session, and responsive surfaces were checked on that version.
|
|
29
|
+
- **Untested** means no compatibility claim is made.
|
|
30
|
+
|
|
31
|
+
Every newer Harness alpha still requires an independent check; support for
|
|
32
|
+
`0.1.2-alpha.1` does not imply support for the moving alpha branch.
|
|
33
|
+
|
|
34
|
+
## Verification policy
|
|
35
|
+
|
|
36
|
+
Every new Harness prerelease or release is checked in a fresh isolated
|
|
37
|
+
installation. A version is promoted only after the plugin boots, the LAN and
|
|
38
|
+
pairing boundary works, the current session opens, and the responsive
|
|
39
|
+
navigation, conversation, Current session, and subagent surfaces have been
|
|
40
|
+
exercised. Real-phone portrait and landscape checks are required for a new
|
|
41
|
+
supported baseline.
|
|
42
|
+
|
|
43
|
+
A successful package installation alone is not compatibility proof. Harness
|
|
44
|
+
may change authentication, DOM semantics, client slots, exported primitives,
|
|
45
|
+
theme storage, or responsive geometry while the plugin still appears to boot.
|
package/docs/DIAGNOSTICS.md
CHANGED
|
@@ -82,7 +82,8 @@ The copied report wraps the retained events with a schema version and export tim
|
|
|
82
82
|
| `REQUEST_REJECTED` | Source-address or `Host` validation rejected the LAN request. | Confirm both devices use the same private network and the QR URL contains the computer's current private address. |
|
|
83
83
|
| `AUTH_REQUIRED` | An unpaired browser opened a protected gateway page. | Pair that browser with a fresh QR/link; direct `:3088` access is intentionally rejected. |
|
|
84
84
|
| `HTTP_UPSTREAM_ERROR` | The gateway could not reach Harness on `127.0.0.1:3080`. | Confirm `dsh web` is running and `upstreamOrigin` matches its port. |
|
|
85
|
-
| `
|
|
85
|
+
| `BROWSER_AUTH_HANDOFF_FAILED` | Harness returned an invalid browser-authentication handoff target. | Confirm the installed Harness version is supported and restart `dsh web`. |
|
|
86
|
+
| `INDEX_REWRITE_ERROR` | The returned Harness index did not match the supported boot contract. | Confirm the installed Harness version appears in the compatibility matrix and restart `dsh web`. |
|
|
86
87
|
| `WS_REJECTED` | A WebSocket upgrade failed trust, authorization, or path validation. | Re-pair the browser and verify no proxy rewrites the URL. |
|
|
87
88
|
| `WS_UPSTREAM_ERROR` | The gateway could not open the loopback Harness event socket. | Confirm the desktop Harness process is still running and reload the paired browser. |
|
|
88
89
|
| `CLIPBOARD_COPY_FAILED` | The browser refused or failed to copy the one-time link. | Grant clipboard permission or select and copy the displayed link manually. |
|
package/docs/SECURITY.md
CHANGED
|
@@ -24,6 +24,7 @@ Mobile View does not reduce that authority. It inherits the selected Harness ses
|
|
|
24
24
|
- `HttpOnly` and `SameSite=Strict` device cookie.
|
|
25
25
|
- Device expiry and explicit revocation.
|
|
26
26
|
- Authentication before HTTP proxying and WebSocket upgrade.
|
|
27
|
+
- Separation of the Local Link device credential from Harness browser-authentication cookies during proxying and alpha token exchange.
|
|
27
28
|
- Gateway-side block for desktop administration paths.
|
|
28
29
|
- Structural loopback source, Host, and Origin validation for every desktop administration request; lookalike DNS names fail closed.
|
|
29
30
|
- Gateway authorities declared through the stock connection `trustedHosts` contract without claiming loopback identity.
|
|
@@ -49,7 +50,7 @@ Revoking a device blocks subsequent requests and reconnects, but an already-upgr
|
|
|
49
50
|
|
|
50
51
|
### Version-sensitive Harness integration
|
|
51
52
|
|
|
52
|
-
Authenticated LAN trust, remote boot capability filtering, direct Settings navigation, coexistence with the stock Cordis footer action, and responsive AppFrame presentation
|
|
53
|
+
Authenticated LAN trust, browser-authentication handoff, remote boot capability filtering, direct Settings navigation, coexistence with the stock Cordis footer action, and responsive AppFrame presentation need small version-sensitive adapters. They do not grant privileged loopback methods, but a Harness upgrade can break presentation or fail closed. Before declaring another Harness version supported, rerun the trust-boundary suite and manually retest pairing, live conversation streaming, Settings navigation, rename, revoke, Cordis coexistence, mobile workspace/session actions, Current session, subagents, theme switching, and third-party conversation tabs.
|
|
53
54
|
|
|
54
55
|
### Firewall automation
|
|
55
56
|
|
package/lib/client.js
CHANGED
|
@@ -592,13 +592,17 @@ window.__ModuleLoader__.load({
|
|
|
592
592
|
const model = group.models.map(recordOf).find((candidate) => candidate?.id === modelId);
|
|
593
593
|
return typeof model?.name === "string" ? model.name : modelId;
|
|
594
594
|
}
|
|
595
|
-
function lastUsedModel(
|
|
596
|
-
|
|
597
|
-
|
|
595
|
+
function lastUsedModel(value) {
|
|
596
|
+
const nodes = recordOf(value)?.nodes;
|
|
597
|
+
if (!Array.isArray(nodes)) return void 0;
|
|
598
|
+
for (let index = nodes.length - 1; index >= 0; index -= 1) {
|
|
599
|
+
const node = recordOf(nodes[index]);
|
|
598
600
|
if (node?.kind !== "assistant") continue;
|
|
599
|
-
const identity = node.requestConfig ?? node.provenance;
|
|
600
|
-
|
|
601
|
-
|
|
601
|
+
const identity = recordOf(node.requestConfig) ?? recordOf(node.provenance);
|
|
602
|
+
const model = typeof identity?.model === "string" ? identity.model : void 0;
|
|
603
|
+
if (model === void 0) continue;
|
|
604
|
+
const provider = typeof identity?.provider === "string" ? identity.provider : "";
|
|
605
|
+
return provider.length > 0 ? `${provider} · ${model}` : model;
|
|
602
606
|
}
|
|
603
607
|
}
|
|
604
608
|
function sessionStats(value) {
|