Concepts
AgentKit architecture
See how the CLI, released kits, runtime adapters, and your project work together.
AgentKit sits between released workflow packages and a supported coding assistant. The CLI handles installation and lifecycle operations; the assistant still runs the AI session and its tools.
flowchart TB
accTitle: From a verified Kit to runtime surfaces
accDescr: An authenticated registry supplies a verified Kit release to the AgentKit CLI. The CLI projects it through an adapter into Claude Code, Codex, or Cursor surfaces.
registry["Authenticated registry"] --> release["Verified Kit release"]
release --> cli["AgentKit CLI"]
cli --> adapter["Adapter projection"]
adapter --> claude["Claude Code surfaces"]
adapter --> codex["Codex surfaces"]
adapter --> cursor["Cursor surfaces"]The parts of the system
- AgentKit CLI (
ak) authenticates access, resolves released kit packages, verifies release material, installs through a selected adapter, and manages updates, diagnostics, uninstall, and recovery snapshots. - A released Kit packages workflows and their supporting components as a versioned unit. You may install the whole Kit or select Skills where the command supports selection.
- A runtime adapter translates supported Kit surfaces into the files and registrations understood by Claude Code, Codex, or Cursor. It also reports content that the target cannot activate.
- A project or user scope determines where the adapted content is available. Project scope is the default for the current workspace. User scope makes the installation available through that runtime's user directories.
- The coding assistant discovers the installed content and performs the workflow using its own model, tools, permission system, and lifecycle events.
What happens when you use a workflow
- You choose an outcome and invoke a Skill, or ask the runtime to perform a workflow that delegates to an Agent.
- The runtime loads the adapted instructions and any supporting files it knows how to use.
- Skills, Agents, and supported Hooks coordinate the work. The exact behavior depends on the runtime's capabilities.
- The workflow may create or change project artifacts such as code, plans, or reports.
- You review the result and decide what to keep, commit, publish, or send.
Installing a Kit does not run its workflows. It also does not commit or publish project changes. A workflow that can affect a remote system, disclose data, or incur cost still needs the permissions and confirmation required by that runtime and workflow.
Installation and execution are separate
AgentKit owns the installation lifecycle for files it can identify as its own. The coding assistant owns execution. Your repository and user-created artifacts remain yours.
This separation matters during updates and removal: AgentKit can replace or remove an unchanged file it previously installed, but it preserves unknown or user-modified files when ownership cannot be proven. See Projects, artifacts, and checkpoints for the recovery model.