Files
deepseek-harness/packages/api
Tianyi Cui 5f773a0ded feat(workspace): restore archived sessions from a settings page
Sessions could be archived from the sidebar row menu but never restored:
the registry-global archive set was a one-way display filter with no
inverse RPC and no surface listing its members.

WorkspaceRegistry.unarchiveSession drops one id from archivedSessionIds in
one durable write on the same operation chain as archive, with no
session-existence probe because a removal cannot introduce an unknown
referent. The Workspace controller exposes it as workspace.unarchiveSession
returning the complete archive set, which the existing archived follow
increment already propagates, so no frame type and no persisted field
changes.

The new client package dsh-client-ui-settings-unarchive-sessions owns the
restore surface: one localized settings.section page listing the archive
set joined with loaded session summaries, newest archive first, searchable
by title or workspace, with one Unarchive action per row.
2026-09-13 16:45:45 +08:00
..

description, kind
description kind
Package map for the application's Remote layer: typed Client-to-Host capability calls, results, and forwarded events, for users and maintainers navigating the group. package-group

api/ — Remote API layers

English | 中文

Summary

The api/ group provides the application's Remote layer: a Client environment can call the business capabilities running on the Host — manage goals, run commands, list the plugin inventory, discover file and session references — as typed method calls, and receive the results or forwarded Host events. remotes decides which capabilities are exposed and how each call reaches the right session's agent; gateway carries the calls and their results between Client and Host. The stack runs over the application's shared Connection; streaming session data is deliberately outside it.

Table of Contents


Packages

The packages below provide the Remote layer; the package READMEs own the exhaustive contracts.

Package Role ctx key
remotes/ Chooses which Host capabilities and events the Client can consume. —
gateway/ Carries typed unary calls, multiplexed streams, and forwarded Host events. ctx.typertGateway / ctx.remote
session-controller/ Owns Session commands, history streams, live control state, and Agent/Session identity policy. ctx.sessionController / ctx.remote.session
settings-controller/ Owns the configuration-surface reads and writes over the settings-domain seams. ctx.settingsController, ctx.credentialsController / ctx.remote.settings, ctx.remote.credentials
workspace-controller/ Owns Workspace mutations and the complete Client Workspace projection. ctx.workspaceController / ctx.remote.workspace
workspace-files/ Owns bounded workspace file access — stat, paged read, list, and the instrumented-operation changes feed — and the Client file resource provider over it. ctx.workspaceFiles / ctx.remote.workspaceFiles

Remote calls run Client → Host over the application's shared Connection. API Gateway owns Remote transport, while the controller packages own Session, configuration-surface, and Workspace behavior. Feature packages register exact Connection Fetch routes for responses that do not fit Remote invocation, such as streamed downloads.


Start with the API Gateway reference to see the Remote model end to end, then the Typert subsystem page for the shared definitions and Connection for the physical carrier.

  • API Gateway reference — the current-state reference for the Typert API Gateway: programming model, generation pipeline, and runtime invocation.
  • Typert subsystem reference — the public contracts shared by protocol, Gateway, and consumer assemblies.
  • Connection — the RPC carrier, /api trust fence, and response envelopes behind every Remote call.

Dev Note

Working context for maintainers — click to expand

None.