AgentKit Studio
Releases and migration

Release notes

From v0.0.16 backwards, what each release changes in terms you can observe — organised by "what you will notice", not by commit log.

Read only the part you care about. Every entry is phrased as "what you will notice"; implementation details stay in code.

Version overview

VersionDateIn one lineBreaking
0.0.162026-11-16Image messages survive, per-workspace Harness, in-process Harness removed⚠️ Yes
0.0.152026-11-16A standalone Harness service takes over execution; UI unified on the DSH design systemYes
0.0.142026-11-10The plugin market becomes discovery; desktop updates stop advancing one version at a timeNo
0.0.13—Personal assistant runtime removed; Studio returns to being a generic DSH plugin⚠️ Yes
0.0.12—DSH baseline moves to 0.2.2-rc.1; prompt predictionYes
0.0.11 and earlier—Desktop plugin alignment and cloud-instance tolerance—

v0.0.16

What you will notice

  • Images stop disappearing. Sent images survive thumbnails, the lightbox, and a history refresh; image-only messages render too.
  • Turn durations are accurate. Answer-only turns use committed start/end times instead of network jitter.
  • Each workspace talks to its own Harness. Switching between Alpha and Beta keeps model, working directory, and history separate.
  • Entry copy changed. "Manual configuration" now lives under More ways to create; runtime selection is a radio group, not a dropdown.
  • Process output is collapsed by default. Failed turns show a neutral summary; expand for the full reason. Usage is pinned under the composer.

Breaking changes

ChangeImpactWhat to do
In-process Harness removedCustom deployments relying on in-process execution failUse a standalone Harness service or an explicit external command
Old sessions/native-* control routes deletedIntegrations calling them get STUDIO_LEGACY_HARNESS_RETIREDMigrate to the new routes
Three bundledDependencies removedThe npm package no longer inlines Harness Core/Node/UIDeclare the dependencies explicitly
publishConfig.executableFiles removedLocal-process launchers no longer ship in the packageDo not depend on an in-package launcher
Unbound directories are refusedNo fallback to another projectComplete the workspace binding

Full steps in upgrade to v0.0.16.

v0.0.15

What you will noticeDetails
Tasks reach the standalone serviceNative sessions, Team roles, and bound A2A tasks all execute there; the desktop reconnects to the original Run
Unified interfaceThe agent form collapses to three steps; resource library, delivery, and operations share DSH design tokens
New agents default to DSH NativeStar Harness is hidden from creation (editing existing Star Harness agents still works)
Denser MCP resource page"Auth headers / environment credentials" folds into an advanced section that auto-expands for custom headers
Light-theme buttons are readablePrimary button hover no longer flips the white label to a light background
Deployment details show image tagsUpdate checks split into current and target image (tag + digest)

Internal changes you will not operate directly: managed Codex timeout variables added to the env whitelist, the Hosted UI session registry moved to agent scope, frozen-host MCP turn budget raised to 15 minutes (adjustable via AGENTKIT_RUNTIME_TIMEOUT_MS), and the browser bundle size became a gate.

v0.0.14

What you will noticeDetails
The plugin market can discoverAggregates npm keywords:dsh-plugin and GitHub topic:dsh-plugin with category filters, download/star sorting, detail cards, one-click install
Updates no longer hop version by versionEvery publication mirrors the same feed onto the compatibility lane, so historical installs jump straight to the newest release
Long sessions compress less oftenThe model context window reads context_length from the model gateway /v1/models instead of a fixed 128000
Incompatibility is explainedWhen a cloud image catalog declares an unimplemented capability, only that image is retired and the latest compatible one is used
Cloud Codex runs full-access by defaultThe container is already the isolation boundary; Codex's own sandbox cannot start on a read-only rootfs. Narrow it with AGENTKIT_CODEX_SANDBOX
Partially unavailable resources still chatDegraded operation is the default; AGENTKIT_STRICT_RESOURCES=1 restores fail-closed

v0.0.13 and earlier

VersionChange
0.0.13Personal assistant runtime, Host routes, and contracts removed; Studio is a generic DSH plugin again, with a plugin-purity gate
0.0.12DSH baseline moves to dsh-v0.2.2-rc.1; prompt prediction added
0.0.11Desktop startup alignment stops copying runtime plugins into the profile and resolves app.asar directly
0.0.8Deleted cloud instances are treated as expired and local bindings are cleaned up; personal assistant creation uses the productised deployment action
0.0.7Falls back to the local configuration record when cloud instance details are unavailable, with an explanation
0.0.6Personal assistant settings can be configured online; saving submits a platform update
0.0.2Cloud personal assistant onboarding, Windows NSIS packaging, and certificate signing
0.0.1Initial release: agent authoring, resource binding, native conversations, deployment, automation, channels

Index by concern

You care aboutVersionKey change
Images and multimodal0.0.16Sent images survive thumbnails, the lightbox, and history refresh
Multi-workspace isolation0.0.16Each workspace connects to its own Harness; unbound directories are refused
Execution architecture0.0.15 / 0.0.160.0.15 introduced the standalone service; 0.0.16 removed the in-process one
Plugin ecosystem0.0.14The market turns from a mirror into a discovery surface
Long-session stability0.0.14The context window reads from the model gateway instead of a fixed 128000
UI consistency0.0.15Unified on DSH design tokens; the agent form collapses to three steps
Resource degradation0.0.14Degraded operation by default; AGENTKIT_STRICT_RESOURCES=1 restores fail-closed

Should you upgrade?

Your situationRecommendation
You run a custom in-process HarnessRead upgrade to v0.0.16 first
You only author agents locallyUpgrade directly; no breaking impact
You rely on the plugin market0.0.14 or later, where discovery exists
You need multi-workspace isolationRequires 0.0.16

On this page