Managing entities

Browse and inspect the AgentKit building blocks in Desktop — Kits, Subagents, Commands, Hooks, Sessions, and MCP servers.

The Entities group holds the building blocks AgentKit knows about on this computer. Desktop inspects and, for Kits, installs them; it does not run a skill or agent. After this page you will know what each surface shows and where its edits stop.

Install and inspect Kits

Kits page with the install wizard open on the destination step

The Kits page shows your license state, licensed and available Kits, and existing global and project installs. The Install wizard walks three steps — choose a destination (a coding agent, or all registered agents; global or a single project), review version and safety, then confirm.

Kit removal is a CLI workflow, not a Desktop action. Preview it before confirming with --yes.

Read Subagents

Subagents list with an agent detail pane and its frontmatter

Subagents lists every agent AgentKit sees, with filters for source, install state, and runtime. The detail pane shows the agent's model, tool grants, and runtime, plus its frontmatter and rendered instructions.

This surface is read-only: it inspects the agent definition. Launch the agent from its coding assistant, not from here.

Browse Commands

Commands grouped by their source command

Commands groups every registered command by its source, with the description and owning Kit for each. Use search and the source/runtime filters to find one, then View its definition.

Like Subagents, this is an inspector. Running a command happens in the coding assistant that owns it.

Check Hooks in the harness

Hooks page showing installed and registered hooks in the harness

Hooks shows how many hooks are installed versus registered in the harness, plus blocks and warnings. Each row lists its matcher and lets you toggle Active or Remove from harness.

Desktop manages harness registration here; it does not edit the soft hook preferences in config.yaml. Review the matcher before changing a hook's state.

Inspect Sessions

Sessions list with recorded session evidence

Sessions summarizes recorded Claude Code and Codex work — project, session, and message counts, durations, and a searchable recent-sessions table. Open a row to inspect its evidence.

Desktop is a session inspector, not a launcher, and it reads only supported session sources. Per-session tool-call and token columns are marked as coming later.

Verify MCP servers

MCP servers list with sources and verification status

The MCP surface lists configured servers, the config files they came from, the known catalog, and how many are verified. Each server shows its source config.toml, scope, and status, with Edit, Disable, Verify, and Delete actions.

Verification runs only when you ask for it. Preview any configuration change before applying it, because it can alter the target runtime's setup.

Next, see how projects and plans are organized in Projects and plans.