AgentKit Studio
Runtimes and deployment

Runtime comparison

Compare DSH Native, Star Harness and Codex across loop ownership, session ownership, Run persistence, the Studio seam and capability sets.

The difference between the three runtimes is not "which one is smarter" — it is which side owns the state. Everything below comes from the capability matrix in src/runtime-contract.mjs; none of it comes from marketing copy.

Five dimensions side by side

DimensionDSH Native HarnessStar HarnessCodex Agent
Model/tool loop ownerDSH native loop (owner: 'dsh')Harness native kernel (owner: 'ksadk-harness', execution: 'native-kernel')Codex App Server (owner: 'studio', execution: 'codex-app-server')
Session / transcript ownerDSH Session, event source dsh-sessionNative run store, event source native-run-storeDSH Session, event source studio-codex-adapter
Stream ownerdsh-agent/assistant-streamnative-model-portcodex-turn/item
Run persistenceNative DSH persistence plus replayDurable receipts (durable-receipts) plus resumeNative DSH persistence plus replay
Studio seamNative execution passes straight through; Studio only projects resources and modelsnpm plugin plus the whole-turn contract agentkit.native-dsh-turn/v1In-process adapter plus an ephemeral Codex thread
Capability setsession, session-events, stream, cancel, replay, persistence, build-bindingnative-run, durable-receipts, tool-approval, cancel, resume, child-taskssession, stream, cancel, replay, build-binding
Contract versionagentkit.studio.runtime/v1agentkit.native-dsh-turn/v1studio.codex.adapter/v1

Source: src/runtime-contract.mjs:19-35.

What the capability sets imply

CapabilityDSH NativeStar HarnessCodexMeaning
sessionyesyes (native-run)yesAll three produce a visible session
cancelyesyesyesAll three can abort the current turn
replayyesnoyesOnly the DSH side can replay by native request
persistence / durable-receiptspersistencedurable-receiptsno separate entryDurability takes a different shape per runtime
resumenoyesnoOnly Star Harness can resume across processes
child-tasksnoyesnoOnly Star Harness has a child-task model

Absent is a boundary, not a gap

A missing resume or child-tasks means DSH Native and Codex delegate Run lifetime to the DSH session. Star Harness owns its own Run ledger, so it must carry recovery semantics itself. Choose based on whether you need conversational continuity or a recoverable Run.

Creatability matrix

RuntimeIn ALLOWED_RUNTIME_TYPESCreation formEditing an existing AgentPortable bundle / deployment
dsh-nativeyesyes (default)yesyes
codexyesyesyesyes
harnessyesselectable once installed and enabledyesyes

Source: src/client/theme.mjs:26, src/client/pages/agent-form.mjs:61-79.

Star Harness is configurable, not permanently unavailable

For harness, creatableRuntime additionally requires starHarnessReady, which comes from canCreate on star-harness/status — installed + enabled + at least one usable workspace (src/client/pages/agent-form.mjs:61-79, src/host/services/star-harness.mjs:150). Before it is installed the button renders disabled with an "unavailable" badge; once installed and bound to a workspace it can be selected for a new Agent. See Star Harness for the install and binding flow.

The runtime.type field

Prop

Type

The default comes from STUDIO_DEFAULT_AUTHORING_RUNTIME = 'dsh-native' (src/authoring-defaults.mjs:4).

The five mandatory Run identity fields

Whichever path you take, a Run must resolve the same identity set or it is rejected before routing:

FieldRequiredValidation
agentIdyesNon-empty string
sessionIdyesNon-empty string
runIdyesNon-empty string
revisionyesMatches ^\d+$ and is at least 1
buildIdyesNon-empty string

A missing field throws RUN_IDENTITY_INVALID; a mismatch against the bound route throws RUN_IDENTITY_MISMATCH (src/runtime-contract.mjs:43-64).

Switching runtimes

ActionBehaviourSource
Edit an existing AgentKeeps its original runtime and never switches on its ownsrc/client/pages/agent-form.mjs:48
Pick DSH Native while creatingClears previously selected tools so no stale binding enters a new native loop:83
Pick Star Harness while creatingRequires installing it, enabling it and binding a workspace first; otherwise not selectablesrc/client/pages/agent-form.mjs:61-79

Switching a runtime does not migrate Run history: old sessions keep opening on their original runtime.

Whether a run target is ready

The run target catalogue row inside start checks counts only types in ALLOWED_RUNTIME_TYPES and renders them by UI name:

ResultMeaningSource
confirmedThe Host returned at least one supported run targetsrc/client/state/start-checks.mjs:21-24
missingThe Host has registered no supported run targetsame
unknownThe catalogue read failed, or an older RPC supplied only the default native entry:20, :23

A legacy fallback is not a catalogue

An older RPC carrier only returns a single source: 'dsh' default native entry, which is not a real run-target catalogue. Studio reports that as unknown, never confirmed, so a degraded connection is not displayed as a ready runtime (src/client/state/start-checks.mjs:20).

On this page