DSH-native Architecture

DeepSeek Harness owns agent execution, model and provider services, credentials, Sessions, tools, approvals, attachments, persistence, and canonical events. DSH Console owns terminal interaction, input preparation, presentation, and focused adapters to those public services.

At the DSH boundary, runtime adapters consume official canonical types. A Session projector converts canonical user, assistant, reasoning, image, tool, todo, interruption, error, and usage events into stable TUI View Models. React components do not depend on the complete DSH SDK surface.

Live streaming and Session replay share the same projector. DSH JSONL logs and attachment storage remain the only persistent source of truth; the Console does not create a second conversation store.

Attachments are admitted before a turn is created. Agent and Session switches prepare a candidate first and only replace the active runtime after validation and flush succeed. These boundaries keep failures from silently changing model context or losing the visible conversation.