mirror of https://github.com/deepseek-ai/deepseek-harness synced 2026-08-15 21:04:50 +00:00

Files

imccyu 19336686a6 feat(apiproxy): session.rename RPC delegating to the session-title service

New unary method in RpcMethodMap with the title-invalid error code; the impl
resolves the agent (cold sessions resume first) and delegates to
ctx.sessionTitle.rename, returning the normalized title plus its event seq so
clients settle the title projection cell ahead of the push frame. session.fork
stays on the reserved-seam list.

2026-07-29 18:59:23 +08:00

apiproxy

feat(apiproxy): session.rename RPC delegating to the session-title service

2026-07-29 18:59:23 +08:00

directory-picker

fix(host): cancellable listing scans and O(log window) insertion

2026-07-29 04:42:13 +08:00

directory-picker-browse

fix(host,client): abort superseded listings on the wire; keep the native swap resolvable

2026-07-29 06:19:18 +08:00

directory-picker-native

refactor(client): deferGroupRegistration owns the multi-hole flow semantics

2026-07-29 03:17:01 +08:00

webserver

doc(packages): add the host/ and client/ group READMEs and table rows

2026-07-28 15:04:59 +08:00

README.i18n.yaml

feat(host,client): ship the in-app directory browser as the browse package's client half

2026-07-28 22:22:14 +08:00

README.md

feat(host,client): ship the in-app directory browser as the browse package's client half

2026-07-28 22:22:14 +08:00

README.zh.md

feat(host,client): ship the in-app directory browser as the browse package's client half

2026-07-28 22:22:14 +08:00

README.md

host/ — web-GUI host half

English | 中文

The host side of the dsh web GUI: the API gateway every client shape shares, and the plain HTTP server it rides on. The browser side lives in client/; the composed application is apps/cli serving apps/web. All product packages.

Package	Role	ctx key
`apiproxy/`	The shared API gateway: the zero-Node TS wire contract (`src/api/`), the fetch carrier pair (`toFetchHandler` host-side, `AbstractApiClient` client-side), and the host implementation over `ctx.agents`/`ctx.workspace`	`ctx.apiProxy`
`webserver/`	Plain HTTP route-registration carrier: `node:http` server listening on activation; routes register as named `exact`/`prefix` handlers	`ctx.httpServer`
`directory-picker/`	Workspace-directory picking seam: discriminated `native`/`browse` capability the gateway's picker RPCs delegate to	`ctx.directoryPicker`
`directory-picker-native/`	Dual-face native interaction: OS-chooser backend (osascript / PowerShell / Zenity+KDialog, host-display only) + the browser half filling ui-workspace's directory-flow slots	(registers `ctx.directoryPicker`)
`directory-picker-browse/`	Dual-face browse interaction: listing/creation primitives over Node stdlib (remote-capable) + the browser half rendering the in-app Select Workspace Directory dialog	(registers `ctx.directoryPicker`)

apiproxy is transport-agnostic by design — it registers no routes; carriers wrap ctx.apiProxy themselves. The HTTP carrier route (with its /api browser-trust fence) is mounted by client/connection's node half, which is why that package lives in the client group: it owns both ends of the wire.