How to Install AgentKit (ak CLI) from Scratch for Claude Code (2026)

Every command in this guide comes from the official documentation at agentkit.best/docs and docs.agentkit.best (checked 08/2026). The ak CLI is currently on a beta channel, so commands and flags may change - double-check the latest command on the docs before you run it.

Which AgentKit? The ak CLI for Claude Code, not OpenAI's AgentKit

Before you copy a single command, take 30 seconds to make sure you are installing the right thing. The word "agentkit" is spread across several unrelated products right now: OpenAI AgentKit (launched 10/2025), BCG-X's agentkit (a Next.js/FastAPI/LangChain starter kit), Google's agents-cli, and a handful of other same-name sites. Install one of those by mistake and the commands will never work for Claude Code.

This article is about: the kit for Claude Code at agentkit.best, driven by a CLI called ak. It is the successor to the old Claude Kit (ck was renamed to ak). It turns Claude Code (plus Codex and Copilot) into an "AI dev and marketing team" through skills and agents. If you are looking for OpenAI's or BCG's product, this is not it.

For the full story behind the rename and why ak replaces ck, read how Claude Kit was renamed to AgentKit (ck to ak).

Before you install (prerequisites)

AgentKit runs on top of Claude Code - it does not replace it. You need two things before you start:

• ① Claude Code installed and working. Check with claude --version. If you get a "command not found" error, install Claude Code first using this Claude Code installation guide (prerequisite). Claude Code needs Node 18+, and you will also need a Claude plan (Pro, Max, or API) to run the model.
• ② An AgentKit account. You sign in to the CLI with an email or an API key. To actually download a kit (Engineer or Marketing), you need an entitlement tied to that account - in other words, you already own the kit.

A point that trips people up: the ak binary itself is a native binary and does not need Node.js or Bun to run. But when the target kit is Claude Code, the Claude Code environment still needs Node 18+. These are two separate things.

No kit yet? You can still install the CLI and sign in, but ak kit init will tell you the entitlement is missing. If you want to use it for real, take a look at the AgentKit plans and grab a license (20% off via link) - the Engineer and Marketing kits are each a one-time purchase, and the Bundle combines both.

Step 1 - Install the ak CLI (macOS / Linux / Windows)

The installer auto-detects your OS and architecture, downloads the stable build, verifies the SHA-256 checksum, and installs to ~/.local/bin. Pick the command for your operating system:

macOS / Linux:

curl -fsSL https://agentkit.best/install.sh | sh

Windows (PowerShell):

irm https://agentkit.best/install.ps1 | iex

If your corporate network blocks the main domain, use the backup domain releases.agentkit.best/install.sh (or .ps1). A few optional environment variables come in handy:

• AK_INSTALL_DIR - change the install directory if you would rather not use the default.
• AK_CHANNEL=beta - install the beta channel (newest, possibly less stable).
• AK_VERSION=x.y.z - pin a specific version.

Once it is installed, verify immediately with two commands:

ak --version
ak doctor

ak --version prints the version number; ak doctor scans your environment and reports PATH, permissions, and conflicts - if everything is green, you are good. Small tip: if ak doctor flags a PATH problem, do not rush ahead to login and installing a kit; fix PATH first, because almost every later error traces back to this. On macOS/Linux the binary lives at ~/.local/bin/ak, so you can run it by its full path for a quick check before you worry about PATH.

Step 2 - Sign in and authorize (ak login)

This is where most of the confusion happens, so read carefully.

A license key does NOT activate the CLI. The license key only activates the AgentKit Desktop App. The ak CLI is authorized (entitled) by signing in to your account. If you keep hunting for a "paste your license key" prompt in the terminal, you will never find it - it does not exist.

On a personal machine (opens a browser or sends an OTP by email):

ak login --email [email protected]

In CI or any non-interactive environment, use an API key:

ak login --api-key ak_live_... --no-interactive

Confirm you signed in to the right account and see what you have access to:

ak whoami
ak licenses

ak whoami tells you which account you are signed in as; ak licenses lists the entitlements (kits) you are allowed to download. If ak licenses comes back empty even though you are sure you bought a kit, double-check that you are not signed in with the wrong email.

Security: never commit or share your API key (it is prefixed with ak_live_, which bots scan for on GitHub). On a shared machine, remember to run ak logout when you are done.

Step 3 - Install a kit into Claude Code (ak kit init)

Now we get to the part that loads skills and agents into Claude Code. The standard command for the Engineer Kit:

ak kit init engineer --target claude-code --global

Swap engineer for marketing if you are installing the Marketing Kit. The --global flag installs for every project; drop it if you only want it in the current directory.

You do not have to install every skill - you can cherry-pick to keep your context lean:

ak kit init engineer --target claude-code --global --skills ak-cook,ak-plan
ak kit init engineer --target claude-code --global --exclude-skills ak-deep-swe

To see which kits and skills are available before you install:

ak kit list-kits
ak versions

Do not own the Engineer/Marketing kit yet? This step needs an entitlement. See what is inside the Engineer Kit to learn which skills and workflows it ships with, or get the Engineer or Marketing kit — 20% off, now $79.20/kit if you have already decided.

Step 4 - Try it in Claude Code (/ak:)

Open Claude Code in a project, type / then ak: - you will see the slash commands the kit just loaded pop up as suggestions:

/ak:cook # implement a feature within scope
/ak:plan # plan the work, break it into phases
/ak:fix # fix bugs, failing tests, CI
/ak:ask # quick questions about the codebase

Try running /ak:cook on a small real task (say, adding an endpoint) to confirm the whole install chain is wired up. If Claude Code accepts the command and starts working through the kit's workflow, you have installed it successfully. If you type /ak: and no command shows up, it usually means the kit was not loaded into the right target - go back and run ak kit init with the correct --target claude-code flag, or restart Claude Code so it reloads the command list. At this point you have walked the full multi-layer verify chain: ak --version (binary runs), ak doctor (clean environment), ak whoami (signed in), ak licenses (has entitlement), and finally /ak: showing up in Claude Code (the kit is live).

Migrating from the old Claude Kit (ck to ak)

If you used Claude Kit (ck) before, ak is the direct successor. Do not let the two binaries coexist - the old ck can hijack your PATH or leave a conflicting shim. After installing ak, run:

ak doctor --check ck_shim_collision

This command detects leftover shim conflicts from ck. Remove the old ck binary from your PATH if it warns you. The docs have also moved from docs.claudekit.cc to docs.agentkit.best, so stop following the old ck commands. The full context on the rename lives in Claude Kit renamed to AgentKit.

Troubleshooting common errors

Most problems installing ak fall into one of the cases below:

Frequently asked questions (FAQ)

Do I need Node.js to install the ak CLI?

No. The ak binary is native (macOS/Linux/Windows) and runs on its own, without Node.js or Bun. Only the Claude Code environment - the target you load kits into - needs Node 18+.

Where do I enter the license key, and why does the CLI not need one?

The license key activates the AgentKit Desktop App, not the CLI. The ak CLI is authorized by signing in to your account (ak login with an email or API key). This is the single most common point of confusion.

Can I install it on Windows?

Yes. Use PowerShell with irm https://agentkit.best/install.ps1 | iex. If typing ak after the install says "not recognized," just open a new terminal window.

Do I need Claude Code Pro?

You need some Claude plan that works with Claude Code (Pro, Max, or pay-as-you-go API) so the model can run. AgentKit does not replace that plan - it only adds skills and agents on top of Claude Code.

How do I uninstall ak?

Run ak uninstall. On a shared machine, run ak logout first to clear your session.

How many machines can one license cover?

The number of machines per license depends on the current terms at agentkit.best..

Conclusion and getting a license

To recap the 5 steps: install Claude Code (prerequisite), install the ak binary, run ak login to authorize, run ak kit init engineer --target claude-code --global, then type /ak: in Claude Code. Remember the biggest trap: license = Desktop App, CLI = account sign-in. Since the CLI is in beta, check the latest commands on the docs before you run them.

To understand how far AgentKit is actually worth it, read the full AgentKit review and weigh the cost with the AgentKit pricing breakdown.