dsh-local-link 1.1.0 → 1.1.1
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 +15 -0
- package/README.md +9 -7
- package/docs/ARCHITECTURE.md +7 -7
- package/docs/COMPATIBILITY.md +32 -12
- package/docs/MOBILE_VIEW.md +1 -1
- package/package.json +22 -22
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,21 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project are documented here.
|
|
4
4
|
|
|
5
|
+
## 1.1.1 — 2026-09-12
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
|
|
9
|
+
- Moved the supported DeepSeek Harness baseline to `0.1.5-rc.1` and expanded the optional Host peer contract for the exact `0.1.5-rc.1` and `0.1.5-rc.2` packages.
|
|
10
|
+
- Updated direct development contracts to `0.1.5-rc.1` while preserving the Local Link gateway, pairing, and trusted-private-LAN boundary unchanged.
|
|
11
|
+
- Documented the new Harness `main`/`rightbar` AppFrame alongside the retained session, composer, sidebar, Settings, and overlay slots used by Local Link.
|
|
12
|
+
|
|
13
|
+
### Validated
|
|
14
|
+
|
|
15
|
+
- Composed and booted clean Web profiles with the packed plugin source on Harness `0.1.5-rc.1` (`latest`) and `0.1.5-rc.2` (`next`).
|
|
16
|
+
- Rechecked the packed `1.1.1` artifact on `0.1.2-rc.1`, `0.1.1-rc.2`, `0.1.1-rc.1`, and `0.1.0-rc.8`: every isolated profile passed plugin peer checks, pairing, authenticated HTTP and WebSocket traffic, immediate socket closure on revoke, and post-revoke rejection.
|
|
17
|
+
- Verified desktop Local Access and QR generation plus responsive activation and navigation at `390 × 844` without client exceptions on both exact Harness versions.
|
|
18
|
+
- Passed typecheck, all 98 automated tests across 16 files, production build, and package dry-run against both `0.1.5` RC contract sets.
|
|
19
|
+
|
|
5
20
|
## 1.1.0 — 2026-09-07
|
|
6
21
|
|
|
7
22
|
`1.1.0` updates Local Link for DeepSeek Harness `0.1.2-rc.1` while preserving the existing trusted-private-LAN product and security boundary. It keeps the stock Harness client, session state, permissions, and live stream instead of introducing a second remote client.
|
package/README.md
CHANGED
|
@@ -9,7 +9,7 @@ Use the same [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)
|
|
|
9
9
|
|
|
10
10
|
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.
|
|
11
11
|
|
|
12
|
-
The `1.1.
|
|
12
|
+
The `1.1.x` line supports DeepSeek Harness `0.1.5-rc.1` and keeps the stock Web client usable 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.
|
|
13
13
|
|
|
14
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
15
|
|
|
@@ -73,14 +73,16 @@ Compatibility is checked against exact DeepSeek Harness versions—not inferred
|
|
|
73
73
|
|
|
74
74
|
| DeepSeek Harness | Local Link status |
|
|
75
75
|
| --- | --- |
|
|
76
|
-
| `0.1.
|
|
76
|
+
| `0.1.5-rc.2` | **Verified next** |
|
|
77
|
+
| `0.1.5-rc.1` | **Supported release** |
|
|
78
|
+
| `0.1.2-rc.1` | **Verified** |
|
|
77
79
|
| `0.1.1-rc.2` | **Verified** |
|
|
78
80
|
| `0.1.1-rc.1` | **Verified** |
|
|
79
81
|
| `0.1.0-rc.8` | **Verified** |
|
|
80
82
|
|
|
81
|
-
All
|
|
83
|
+
All six rows were checked with the packed `1.1.1` source. Every exact version passed isolated profile composition, plugin peer checks, pairing, authenticated HTTP and WebSocket traffic, immediate socket closure on revoke, and rejection of the revoked device. The `0.1.5` rows also received the current real-client responsive check at `390 × 844`; historical responsive evidence remains recorded separately. `0.1.5-rc.1` is the development baseline. `0.1.5-rc.2` is an exact `next` check, not a promise about future movement of that tag.
|
|
82
84
|
|
|
83
|
-
|
|
85
|
+
Only the exact versions listed above carry a compatibility claim. Alpha builds—including the removed `0.1.2-alpha.1` row—versions older than `0.1.0-rc.8`, and whatever package a moving `next` tag points to later are unsupported until checked independently. See [Compatibility](docs/COMPATIBILITY.md) for the evidence and remaining real-device boundary.
|
|
84
86
|
|
|
85
87
|
## Use
|
|
86
88
|
|
|
@@ -99,7 +101,7 @@ Phone and tablet browsers automatically receive Mobile View when the viewport is
|
|
|
99
101
|
|
|
100
102
|
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.
|
|
101
103
|
|
|
102
|
-
| Stock narrow-screen behavior | Mobile View in `1.1.
|
|
104
|
+
| Stock narrow-screen behavior | Mobile View in `1.1.x` |
|
|
103
105
|
| --- | --- |
|
|
104
106
|
| Desktop navigation competes with the conversation | Workspace and session navigation opens as a dismissible left drawer |
|
|
105
107
|
| Session metadata crowds the header | Context, model, access, preset, activity, and export move into a compact right drawer |
|
|
@@ -181,7 +183,7 @@ The gateway does not create a second Harness session. During first connection it
|
|
|
181
183
|
|
|
182
184
|
Authorization 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.
|
|
183
185
|
|
|
184
|
-
The 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.
|
|
186
|
+
The 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` 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.
|
|
185
187
|
|
|
186
188
|
## Configuration
|
|
187
189
|
|
|
@@ -261,7 +263,7 @@ Project documentation:
|
|
|
261
263
|
- The shortcut that opens a specific Settings section uses a small semantic compatibility bridge because Harness does not expose a general settings-navigation service.
|
|
262
264
|
- Harness's footer-action container needs a compatibility layout rule when the full-width Cordis action is present.
|
|
263
265
|
- 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.
|
|
264
|
-
- Plugin-owned buttons and text inputs use Harness `Button` and `Input` primitives and their semantic variants. Harness `0.1.
|
|
266
|
+
- Plugin-owned buttons and text inputs use Harness `Button` and `Input` primitives and their semantic variants. Harness `0.1.5-rc.1` still has no complete public responsive-shell, spacing, or radius contract, so mobile geometry, responsive compositions, and the few missing primitive icons remain documented design-system compatibility risks.
|
|
265
267
|
|
|
266
268
|
## Development disclosure
|
|
267
269
|
|
package/docs/ARCHITECTURE.md
CHANGED
|
@@ -46,9 +46,9 @@ 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-rc.1`
|
|
49
|
+
Harness `0.1.2-rc.1` and the verified `0.1.5` builds require 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 supported builds that do not expose this service keep the direct-root redirect.
|
|
50
50
|
|
|
51
|
-
Harness `0.1.2-rc.1`
|
|
51
|
+
Harness `0.1.2-rc.1` and the verified `0.1.5` builds authenticate the connection transport as a whole and no longer apply the older method-specific loopback tier. To preserve Local Link's established scope, the LAN gateway rejects the former privileged configuration, credential, native Host-action, and agent-preset-authoring RPCs before proxying. This applies equally to `pairing` and `trusted-lan`; enabling `trusted-lan` never grants those Host administration operations. `tests/trust-boundary.test.ts` exercises the RC Host/Origin and browser-authentication fence, while `tests/gateway.test.ts` pins the Local Link RPC restriction including the renamed RC Settings methods and encoded-path handling.
|
|
52
52
|
|
|
53
53
|
### Authentication state
|
|
54
54
|
|
|
@@ -66,7 +66,7 @@ The loopback administration route exposes list, clear, and a narrow allowlisted
|
|
|
66
66
|
|
|
67
67
|
`src/client.tsx` registers two normal Harness contributions: a compact desktop `sidebar.footer.action` that shows a QR code and copyable one-time link, and a desktop-only `settings.section` that manages paired devices and the local diagnostic report. It does not replace the root layout. The desktop surfaces use plugin-owned classes and semantic selectors; version-sensitive stock-DOM hooks are isolated in `src/mobile-layout.tsx` and documented below.
|
|
68
68
|
|
|
69
|
-
The `0.1.
|
|
69
|
+
The `0.1.5-rc.1` browser graph is a normal Cordis `Context`. Session state comes from `@deepseek-ai/dsh-api-session-controller/client`; React slot hooks are supplied by `@deepseek-ai/dsh-client-ui-session/client`, and slot ownership/rendering comes from `@deepseek-ai/dsh-client-ui-renderer/client`. Agent-preset display reads `SessionSummary.projectionValues.agentPreset`, while subagent types come from `@deepseek-ai/dsh-subagent/client`. The removed `@deepseek-ai/dsh-client-runtime` aggregate is neither injected nor imported.
|
|
70
70
|
|
|
71
71
|
The Harness `sidebar.footer.action` contract is a list, but the supported Web client renders that list as a horizontal flex row while the stock Cordis action reserves `width: 100%` with `flex: none`. Without a compatibility rule, Cordis reduces later actions to zero width. Local Link orders its entry first and changes only the footer container that semantically contains `.dsh-local-link-footer` into a vertical stack. The same scoped rule normalizes the list gap and removes the following action's private top margin so Local access, Cordis, and Settings keep one visual rhythm. The selector is anchored on the plugin-owned class and accounts for the slot renderer's `display: contents` wrapper; it never names a generated Harness class.
|
|
72
72
|
|
|
@@ -82,7 +82,7 @@ Plain HTTP on a private IP is not a browser secure context, while the stock Harn
|
|
|
82
82
|
|
|
83
83
|
`src/mobile-layout.tsx` is mounted through the normal client plugin and activated by `matchMedia('(max-width: 834px)')`. Crossing the viewport boundary mounts or disposes one scoped set of enhancements. The gateway does not inspect user agents, parse `view` parameters, set layout cookies, load a second bundle, or alter the root-layout boot entry.
|
|
84
84
|
|
|
85
|
-
The shipped Harness root and AppFrame
|
|
85
|
+
The shipped Harness root and AppFrame own `sidebar`, `main`, `rightbar`, and `shell.overlay`; Conversation remains the native `main.conversation` panel. Local Link contributes only additive overlay, session-information, and subagent surfaces, then applies scoped responsive geometry to the existing frame. It never enumerates Chat, Trajectory, composer, dock, node, rightbar panel, or third-party registrations, so those continue to resolve through the native dynamic slots.
|
|
86
86
|
|
|
87
87
|
The existing `layout` controller opens and closes the stock sidebar. Responsive styles project that sidebar and the plugin's details surface as dismissible drawers, preserve overlay contributions, apply safe-area insets, and keep dynamic tab lists horizontally scrollable. At wider viewports the enhancement fiber is disposed and the untouched desktop presentation remains.
|
|
88
88
|
|
|
@@ -108,11 +108,11 @@ The automatic pairing page runs before the Harness client and locale service loa
|
|
|
108
108
|
|
|
109
109
|
Local Link uses Harness semantic color, state, border, background, elevation, and typography variables wherever the supported client exports an applicable token. Icons are imported from `@deepseek-ai/dsh-client-ui-primitives` when that package exposes the required glyph, and stock Harness menus, dialogs, conversation actions, Settings surfaces, and session operations that Local Link does not replace remain their native components. Literal colors following a `var(--dsw-*, fallback)` expression are defensive fallbacks and are not selected in the supported Harness build. The context breakdown's purple tools segment intentionally matches the stock Harness `ContextMeter` implementation exactly.
|
|
110
110
|
|
|
111
|
-
Harness `0.1.
|
|
111
|
+
Harness `0.1.5-rc.1` does not expose a complete public responsive-shell or Drawer contract, spacing scale, radius scale, or mobile component recipes. Mobile geometry—safe-area placement, drawer widths, tap-target dimensions, spacing, radii, and transition timing—therefore remains plugin-owned CSS. One plugin-scoped `--dllm-side-drawer-width` value keeps the stock sidebar projection, the rightbar surface, and Current session visually identical instead of duplicating width literals. A small set of concepts also has no exported Harness primitive: Local access/device, navigation, current-session information, permission variants, and the subagent group glyph. The compact feedback-note affordance is a scoped presentation adapter because the stock feedback action accepts text only and exposes no icon-mode contract.
|
|
112
112
|
|
|
113
113
|
All plugin-owned button and text-input controls use the exported Harness `Button` and `Input` primitives. Their semantic variants (`primary`, `outline`, `ghost`, and `toolbar`) remain owned by Harness; Local Link adds only the geometry required by its composed surfaces, such as a full-width sidebar row, a segmented copy action, a scrim, or a tree row. A source-level test rejects new raw `<button>` and `<input>` elements in the plugin UI.
|
|
114
114
|
|
|
115
|
-
Component-level alignment remains bounded by the contracts Harness actually exports. The responsive shell, side drawer, bottom sheet, QR composition, context card, and diagnostics disclosure have no equivalent complete public responsive component contract in `0.1.
|
|
115
|
+
Component-level alignment remains bounded by the contracts Harness actually exports. The responsive shell, side drawer, bottom sheet, QR composition, context card, and diagnostics disclosure have no equivalent complete public responsive component contract in `0.1.5-rc.1`, so their structure remains semantic HTML plus scoped CSS. They use Harness tokens and primitive controls internally and should migrate if Harness later publishes compatible responsive components.
|
|
116
116
|
|
|
117
117
|
These are compatibility surfaces, not an independent theme. Every Harness upgrade must compare them against the current token vocabulary, primitive icon catalog, slot contracts, and stock mobile behavior. They should be deleted in favor of upstream tokens or components as soon as equivalent public contracts exist.
|
|
118
118
|
|
|
@@ -175,7 +175,7 @@ No service discovery, certificate generator, tunnel client, native application,
|
|
|
175
175
|
|
|
176
176
|
## Compatibility strategy
|
|
177
177
|
|
|
178
|
-
The plugin develops against the exact DeepSeek Harness `0.1.
|
|
178
|
+
The plugin develops against the exact DeepSeek Harness `0.1.5-rc.1` contracts and separately checks `0.1.5-rc.2`. Most integration uses declared package contracts, but several adapters are intentionally version-sensitive:
|
|
179
179
|
|
|
180
180
|
| Adapter | Why it exists | Failure behavior | Removal condition |
|
|
181
181
|
| --- | --- | --- | --- |
|
package/docs/COMPATIBILITY.md
CHANGED
|
@@ -5,28 +5,35 @@ and Settings contracts. Each supported version is therefore checked directly.
|
|
|
5
5
|
|
|
6
6
|
## Compatibility matrix
|
|
7
7
|
|
|
8
|
-
Last checked on 2026-09-
|
|
9
|
-
`dsh-local-link@1.1.
|
|
8
|
+
Last checked on 2026-09-12 with Node.js 22 and Windows using packed
|
|
9
|
+
`dsh-local-link@1.1.1` source for every row. Versions are newest first.
|
|
10
10
|
|
|
11
11
|
| DeepSeek Harness | Status | Local Link source | Last checked |
|
|
12
12
|
| --- | --- | --- | --- |
|
|
13
|
-
| `0.1.
|
|
14
|
-
| `0.1.
|
|
15
|
-
| `0.1.
|
|
16
|
-
| `0.1.
|
|
13
|
+
| `0.1.5-rc.2` | **Verified next** | `1.1.1` | 2026-09-12 |
|
|
14
|
+
| `0.1.5-rc.1` | **Supported release** | `1.1.1` | 2026-09-12 |
|
|
15
|
+
| `0.1.2-rc.1` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
16
|
+
| `0.1.1-rc.2` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
17
|
+
| `0.1.1-rc.1` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
18
|
+
| `0.1.0-rc.8` | **Verified** | `1.1.1` | 2026-09-12 |
|
|
17
19
|
|
|
18
|
-
|
|
20
|
+
Only the exact versions in the matrix are supported or verified. Alpha builds,
|
|
21
|
+
including the previously tested `0.1.2-alpha.1`, versions older than
|
|
22
|
+
`0.1.0-rc.8`, and future versions reached through a moving dist-tag are
|
|
23
|
+
unsupported until they pass a new check.
|
|
19
24
|
|
|
20
25
|
### Status meanings
|
|
21
26
|
|
|
22
27
|
- **Supported release** is the current development target and receives the
|
|
23
28
|
complete repository and installed-runtime gate.
|
|
24
|
-
- **Verified** means the
|
|
29
|
+
- **Verified next** means the exact package version currently published under
|
|
30
|
+
`next` passed the compatibility gate; the moving tag itself is not supported.
|
|
31
|
+
- **Verified** means the current packed Local Link artifact passed the historical
|
|
25
32
|
RC gate on that exact version.
|
|
26
33
|
- **Untested** means no compatibility claim is made.
|
|
27
34
|
|
|
28
35
|
Every newer Harness version still requires an independent check; support for
|
|
29
|
-
`0.1.
|
|
36
|
+
`0.1.5-rc.1` does not imply support for a moving `next` tag or later alpha.
|
|
30
37
|
|
|
31
38
|
## Verification policy
|
|
32
39
|
|
|
@@ -38,9 +45,22 @@ on revoke, reject the revoked device, and activate the responsive shell at
|
|
|
38
45
|
`390 × 844`. Automated tests cover Current session, subagent, locale, slot, and
|
|
39
46
|
composition contracts.
|
|
40
47
|
|
|
41
|
-
All
|
|
42
|
-
|
|
43
|
-
|
|
48
|
+
All six exact Harness versions installed the packed `1.1.1` artifact without a
|
|
49
|
+
peer conflict and passed an isolated installed-runtime gate: profile composition
|
|
50
|
+
and boot, Local Link pairing, the version-appropriate browser-authentication
|
|
51
|
+
handoff, authenticated root access, an authenticated supported WebSocket,
|
|
52
|
+
immediate socket closure on revoke, and a `401` response when the revoked device
|
|
53
|
+
retried. `0.1.0-rc.8`, `0.1.1-rc.1`, and `0.1.1-rc.2` used `/api/events.mux`;
|
|
54
|
+
`0.1.2-rc.1` and the `0.1.5` builds used the current `/api/remote.mux` path.
|
|
55
|
+
|
|
56
|
+
The `0.1.5` rows compose and boot with the new `main`/`rightbar` AppFrame while
|
|
57
|
+
retaining the session header, composer, sidebar, Settings, and overlay slots
|
|
58
|
+
used by Local Link. Both exact RCs additionally passed typecheck, all 98
|
|
59
|
+
automated tests, production build/package verification, desktop Local Access
|
|
60
|
+
rendering, and the responsive shell at `390 × 844` without client exceptions.
|
|
61
|
+
The historical versions retain their earlier real-client responsive evidence;
|
|
62
|
+
the `1.1.1` patch changes package compatibility contracts and documentation, not
|
|
63
|
+
the shipped client or gateway implementation.
|
|
44
64
|
|
|
45
65
|
Historical RC runs used empty profiles, so they did not create provider-backed
|
|
46
66
|
conversations. Physical-phone portrait and landscape acceptance also remains a
|
package/docs/MOBILE_VIEW.md
CHANGED
|
@@ -51,7 +51,7 @@ Landscape phones, split-screen browsers, virtual keyboards, third-party fixed-wi
|
|
|
51
51
|
|
|
52
52
|
Mobile View keeps the official Harness root and AppFrame mounted. It contributes controls through overlay, conversation, theme, session, locale, button, and input contracts wherever Harness exposes them. The stock desktop presentation is unchanged when the media query does not match.
|
|
53
53
|
|
|
54
|
-
Harness `0.1.
|
|
54
|
+
Harness `0.1.5-rc.1` does not expose a complete public responsive shell, drawer recipe, spacing/radius scale, or every required glyph. The plugin therefore owns mobile geometry and a small number of scoped presentation adapters for stock brand, workspace, session-action, and feedback elements. Those hooks are documented in [Architecture and compatibility boundaries](ARCHITECTURE.md) and must be retested for each supported Harness version.
|
|
55
55
|
|
|
56
56
|
## Security
|
|
57
57
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-local-link",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.1",
|
|
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"
|
|
@@ -87,7 +87,7 @@
|
|
|
87
87
|
"author": "DoNotEatMe",
|
|
88
88
|
"peerDependencies": {
|
|
89
89
|
"@deepseek-ai/cordis": "^4.0.2",
|
|
90
|
-
"@deepseek-ai/dsh-host-webserver": "0.1.0-rc.8 || 0.1.1-rc.2 || 0.1.2-rc.1",
|
|
90
|
+
"@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",
|
|
91
91
|
"react": "^18.2.0"
|
|
92
92
|
},
|
|
93
93
|
"peerDependenciesMeta": {
|
|
@@ -107,26 +107,26 @@
|
|
|
107
107
|
},
|
|
108
108
|
"devDependencies": {
|
|
109
109
|
"@deepseek-ai/cordis": "4.0.2",
|
|
110
|
-
"@deepseek-ai/dsh-api-session-controller": "0.1.
|
|
111
|
-
"@deepseek-ai/dsh-attachment": "0.1.
|
|
112
|
-
"@deepseek-ai/dsh-client-connection": "0.1.
|
|
113
|
-
"@deepseek-ai/dsh-client-locale": "0.1.
|
|
114
|
-
"@deepseek-ai/dsh-client-ui-conversation": "0.1.
|
|
115
|
-
"@deepseek-ai/dsh-client-ui-layout": "0.1.
|
|
116
|
-
"@deepseek-ai/dsh-client-ui-primitives": "0.1.
|
|
117
|
-
"@deepseek-ai/dsh-client-ui-renderer": "0.1.
|
|
118
|
-
"@deepseek-ai/dsh-client-ui-session": "0.1.
|
|
119
|
-
"@deepseek-ai/dsh-client-ui-settings": "0.1.
|
|
120
|
-
"@deepseek-ai/dsh-client-ui-sidebar": "0.1.
|
|
121
|
-
"@deepseek-ai/dsh-client-ui-slots": "0.1.
|
|
122
|
-
"@deepseek-ai/dsh-client-ui-theme": "0.1.
|
|
123
|
-
"@deepseek-ai/dsh-host-webserver": "0.1.
|
|
124
|
-
"@deepseek-ai/dsh-code-runtime": "0.1.
|
|
125
|
-
"@deepseek-ai/dsh-session-persistence": "0.1.
|
|
126
|
-
"@deepseek-ai/dsh-session-query": "0.1.
|
|
127
|
-
"@deepseek-ai/dsh-session-log-export": "0.1.
|
|
128
|
-
"@deepseek-ai/dsh-settings": "0.1.
|
|
129
|
-
"@deepseek-ai/dsh-subagent": "0.1.
|
|
110
|
+
"@deepseek-ai/dsh-api-session-controller": "0.1.5-rc.1",
|
|
111
|
+
"@deepseek-ai/dsh-attachment": "0.1.5-rc.1",
|
|
112
|
+
"@deepseek-ai/dsh-client-connection": "0.1.5-rc.1",
|
|
113
|
+
"@deepseek-ai/dsh-client-locale": "0.1.5-rc.1",
|
|
114
|
+
"@deepseek-ai/dsh-client-ui-conversation": "0.1.5-rc.1",
|
|
115
|
+
"@deepseek-ai/dsh-client-ui-layout": "0.1.5-rc.1",
|
|
116
|
+
"@deepseek-ai/dsh-client-ui-primitives": "0.1.5-rc.1",
|
|
117
|
+
"@deepseek-ai/dsh-client-ui-renderer": "0.1.5-rc.1",
|
|
118
|
+
"@deepseek-ai/dsh-client-ui-session": "0.1.5-rc.1",
|
|
119
|
+
"@deepseek-ai/dsh-client-ui-settings": "0.1.5-rc.1",
|
|
120
|
+
"@deepseek-ai/dsh-client-ui-sidebar": "0.1.5-rc.1",
|
|
121
|
+
"@deepseek-ai/dsh-client-ui-slots": "0.1.5-rc.1",
|
|
122
|
+
"@deepseek-ai/dsh-client-ui-theme": "0.1.5-rc.1",
|
|
123
|
+
"@deepseek-ai/dsh-host-webserver": "0.1.5-rc.1",
|
|
124
|
+
"@deepseek-ai/dsh-code-runtime": "0.1.5-rc.1",
|
|
125
|
+
"@deepseek-ai/dsh-session-persistence": "0.1.5-rc.1",
|
|
126
|
+
"@deepseek-ai/dsh-session-query": "0.1.5-rc.1",
|
|
127
|
+
"@deepseek-ai/dsh-session-log-export": "0.1.5-rc.1",
|
|
128
|
+
"@deepseek-ai/dsh-settings": "0.1.5-rc.1",
|
|
129
|
+
"@deepseek-ai/dsh-subagent": "0.1.5-rc.1",
|
|
130
130
|
"@types/node": "^24.3.0",
|
|
131
131
|
"@types/qrcode": "^1.5.5",
|
|
132
132
|
"@types/react": "~18.3.1",
|