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

Files

creatixchu 761ceb79f3 fix(host,client): roll back partial flow registrations; cover the widened double

- The browse client half mirrors -native's rollback: a pair construction
  that throws halfway (declared-but-occupied second hole) disposes the
  earlier deferral before rethrowing, so no orphaned slot subscription
  outlives the failed fiber (ds-review-bot).
- The TestWorkspaces browse methods gain the coverage CI's per-file gate
  requires (defaults + stub overrides, recorded like their siblings).

2026-07-29 01:33:16 +08:00

apiproxy

Merge remote-tracking branch 'origin/doc/host-client-group-readmes' into feat/directory-picker

2026-07-29 01:09:33 +08:00

directory-picker

feat(host,client): compose directory picking through slots — dual-face -native, no wire advertisement

2026-07-28 21:51:01 +08:00

directory-picker-browse

fix(host,client): roll back partial flow registrations; cover the widened double

2026-07-29 01:33:16 +08:00

directory-picker-native

fix(host): roll back the surviving deferral when flow-registration setup fails halfway

2026-07-29 01:29:08 +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.