VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Statusline Update AgentKit CLI & Kits Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit UI Review Gate Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App Promotions Support VividKit
AgentKit Recommended for new setups ak CLI

What Is AgentKit?

A beginner mental model: AgentKit is the next generation of ClaudeKit — kit-based workflows, more runtimes, the ak CLI, and Desktop App.

Context

ClaudeKit is now AgentKit

Both a rebrand and an expansion. Kits, Skills, Agents, Hooks, and structured workflows stay central — with a wider product surface.

New native CLI

ak replaces ck for the new line

More runtimes

Via adapters — no parity promise

Desktop App

Local visual control center

Why it exists

What problem does it solve?

You want verified AI workflows installed into the coding assistant you already use, then run tasks with that runtime’s models, tools, and permissions — while you stay responsible for reviewing plans, diffs, and external actions.

Product surface

Four main surfaces

Each surface has a job. Desktop does not replace the terminal; the CLI does not replace your coding assistant.

CLI

AgentKit CLI (ak)

Authenticates, resolves, verifies, installs, updates, diagnoses, and removes AgentKit-owned content.

KIT

Kits

Versioned packages of Skills, Agents, Hooks, and supporting artifacts — the unit you install.

ADP

Runtime adapters

Project Kit content into the structure a coding agent understands.

APP

Desktop App

Native UI for setup, Kit browsing, project registration, and local activity.

Critical boundary

Install a Kit ≠ run a workflow

Install a Kit

AgentKit installs and adapts content. It does not start a task.

  • CLI / Desktop own lifecycle
  • Adapter projects into the runtime
  • You choose project or global scope

Invoke a Skill

The coding assistant runs the AI session with its own model, tools, and permissions.

  • Syntax varies (/ak:…, $ak:…)
  • Hooks / events differ by runtime
  • You review the result

Runtimes

Supported runtime model

Paths

Where should you start?

New setup

Start with AgentKit

Install ak → install a Kit → open runtime → invoke a Skill.

Installation and onboarding →
Already on ClaudeKit

Kits continue; Desktop is extra

ak login with your ClaudeKit purchase account → keep using AgentKit Kits. Desktop App is separate. File migrate is optional.

Migrate / cutover (optional) →

Continue learning