AgentKit Studio

AgentKit Studio Documentation

Everything you need to build, run, deploy, and observe enterprise agents on DeepSeek Harness.

Hand the idea to an agent

AgentKit Studio is a product plugin for DeepSeek Harness (DSH): author agents, bind enterprise resources, run native conversations, and deploy agents to the cloud from one workbench. This documentation covers everything from the first minute to production operations.

Start here

Documentation map

SectionWhat you will findWho it is for
Getting startedInstall, quickstart, first conversationAnyone opening the product for the first time
ConceptsProduct model, three runtimes, resources, glossaryAnyone deciding which capability to use
GuidesStep-by-step playbooks with verificationDevelopers and operators who use it daily
ReferenceContracts, enums, error codes, commandsIntegrators, plugin authors, on-call
Runtimes and deploymentRuntime comparison, managed runtime lifecycle, degradationOwners of shipping and reliability
Ecosystem and pluginsDSH plugin authoring, plugin market, expert templatesAnyone extending the product
Releases and migrationRelease notes, compatibility, upgrade stepsAnyone tracking versions
HelpFAQ, troubleshooting, known limitationsAnyone who is stuck
ContributingDev environment, gates, patch governance, writing styleContributors

What the product does

Agent authoring

Multi-step form, immutable revisions, frozen runtime configuration.

Three runtimes

DSH Native, Star Harness, and Codex, with an explicit capability matrix.

Resource bindings

MCP servers, skills, knowledge bases, and memory bound to a revision.

Cloud deployment

24×7 managed runtimes with 19 observable, rollback-able deployment states.

Experts and teams

Expert templates and local teams sharing the same revision semantics.

Plugin ecosystem

DSH plugin market, Codex plugins, remote index, and readiness checks.

Docs ship with the product

This site publishes automatically from the main branch. The "last updated" stamp comes from Git, and prose is reviewed in the same pull request as the code — there is no window where the docs describe a product that no longer exists.

On this page