_Kerman
9365ef496d
# Conflicts: # packages/acp/acp/tests/approval.spec.ts # packages/acp/acp/tests/edges.spec.ts # packages/api/session-controller/tests/event-script.client.ts # packages/client/connection/src/client/fixture.ts # packages/client/ui-conversation/src/client/contract/slots.ts # packages/client/ui-conversation/src/client/contract/views.ts # packages/client/ui-conversation/src/client/index.ts # packages/client/ui-conversation/src/client/stores.ts # packages/core/agent-loop/tests/loop.spec.ts # packages/extensions/cordis-client-runner/src/client/slot-catalog.ts # packages/extensions/tool-cordis/src/api-catalog.ts # packages/host/apiproxy/src/api-proxy.ts # packages/host/apiproxy/src/api/events.ts # packages/host/apiproxy/tests/api-proxy-view.spec.ts # packages/interaction/user-approval/src/index.ts # packages/llm/llm-deepseek/tests/adapter.e2e.ts # packages/llm/llm-pi-ai/src/context.ts # packages/llm/llm-pi-ai/tests/context.spec.ts # packages/llm/llm/tests/content.spec.ts # packages/subagent/subagent/tests/continuation.spec.ts # packages/subagent/tool-subagent/tests/tool-subagent.spec.ts # packages/test-support/llm-replay/tests/llm-replay.spec.ts # packages/todo/tool-todo/tests/tool-todo.spec.ts # scripts/gen-persistence-catalog.ts
Session Controller
English | 中文
@deepseek-ai/dsh-api-session-controller owns the Host ctx.sessionController service and the generated Client ctx.remote.session namespace. It serves Session list, search, creation, model selection, rename, fork, prompt, attachment, queue, cancellation, message-aligned history, live log following, and Host-wide control state.
History pages and follow event frames carry only raw SessionWireEvent values. Tool arguments, result content, failures, and tool/result.data.meta pass through unchanged; the controller does not resolve a Tool definition, run a presenter, or attach UI data.
Each endpoint states its activation policy. List, search, attachment, history pages, and log following can inspect persistence without activating an Agent; queue mutation and cancellation require the corresponding live state; model, rename, and prompt commands may explicitly resume an ordinary Session. Create and fork are the only operations that create a new Agent. The service applies one preset-aware resume policy and subagent ownership fence to its own methods and to the Typert Agent and Session lookups used by other Remote namespaces.
The Client adapter exposes SessionEventStream, a Gateway RemoteJournalStream bound to one ordinary or direct-subagent address. It opens follow before the initial page, publishes only contiguous replace, prepend, and append changes, and repairs reconnect or sequence gaps through a tail page. A business, persistence, or unresolved continuity failure terminates the stream, while only physical carrier loss selects automatic resumption. SessionControlStream is a Gateway RemoteSnapshotStream; every generation opens with a complete process-local baseline, so reconnect replaces queue, jobs, and projection state instead of treating transient values as durable events.
Model Experience
None, as invoked Agent commands own any model-visible effect.
KV Cache effect
No direct effect; model requests remain owned by the Agent and LLM packages.
Known Limitations and Deferred Work
- Control baselines represent process-local state and therefore cannot reconstruct jobs after a Host restart.
- A failed follow resumption remains visible to the caller instead of retrying indefinitely.