@dadado/agent-kit-cli

中文文档
6.16.1发布于 2026/11/11Apache-2.0TypeScriptES Module构建来源已验证近 30 天下载 3939

Agent Kit CLI: HITL framework install and tooling for AI-assisted IDEs (rules, skills, plan/handoff, context).

原始使用文档
文档目录5 节
  1. Install
  2. Mission Control
  3. Bare invoke (welcome)
  4. Common commands
  5. Docs

@dadado/agent-kit-cli

npm version of @dadado/agent-kit-cli License: Apache-2.0 Node.js >=22.12 Latest release of the public agent-kit repository

Mission Kit helmet mark

Agent Kit CLI: HITL operating-layer install and tooling for AI-assisted IDEs (rules, skills, plan/handoff, staging-to-prod, memory). It installs local workspace contracts; it is not a hosted control plane or graph workflow runtime.

Install

From your project root (Node.js 22.12+):

npx @dadado/agent-kit-cli@latest install

Use @latest so npx does not reuse a stale cached CLI. Pin a version when you need a reproducible install:

npx @dadado/[email protected] install

Optional L1 packs:

npx @dadado/agent-kit-cli@latest install --pack clean-code,context-management

Install writes L0 kit files under .cursor/, plus autogit/ and .cursor/agent-kit.json. It does not copy the Agent Kit monorepo into your project.

After install, in Cursor run /agent-kit-onboard, then /start-project when you have a deliverable.

Mission Control

From package version 4.8.2 onward, this npm package includes Mission Control panel assets under dashboard/. In a consumer workspace after install:

agent-kit dashboard

The panel binds to loopback by default, serves its own static files, and snapshots the current workspace. L0 install does not copy dashboard/ into your app; agent-kit dashboard resolves the panel from the installed package.

Browser-free: agent-kit mission-control is a third surface (ASCII Mission, Flight Log, Checklist, Crew Monitor) that reuses the same snapshot builders without starting the HTTP server. agent-kit mission-control --once prints one frame (Claude Code /agent-kit). The web dashboard stays shipped.

Older tags before 4.8.2 do not include those assets. Prefer a current pin, or point MISSION_CONTROL_KIT_ROOT / AGENT_KIT_HOME at an agent-kit checkout that contains dashboard/.

Bare invoke (welcome)

With no subcommand, agent-kit prints a branded Mission Kit welcome (ASCII helmet, version, and short utility hints) then exits. Technical identifiers stay agent-kit / @dadado/agent-kit-cli.

agent-kit
# → welcome + hints (doctor, status, dashboard, init, --help)

agent-kit --help
# → grouped command list (SETUP / MISSION / DASHBOARD / INTEGRITY)

NO_COLOR=1 agent-kit
# → plain text (no ANSI); also plain when stdout is not a TTY or CI=1

Subcommands and agent-kit --version are unchanged. agent-kit run <slash> starts those project slashes headless from .cursor/commands/ (numbered-list HITL). agent-kit run-plan-all is a first-class alias of agent-kit run run-plan-all. Typing /run-plan-all in zsh is a filesystem path. /git-prod and /kit-prod stay operator-gated and are omitted from that catalog. Factory /kit-staging is not a catalog slash either (factory disk / landing wraps only).

On an interactive TTY, long-running commands (init, install, doctor, update, run-plan ticks) show an in-process ANSI spinner plus a rotating Mission Kit tip. Set AGENT_KIT_REDUCED_MOTION=1 for static text on a capable TTY. Runtime dependencies stay @clack/prompts, citty, and kolorist (no ora / figlet / chalk / ink). Window titles for agent-kit dashboard and agent-kit dashboard-broadcast use the workspace basename, not the CLI package folder.

Common commands

CommandPurpose
agent-kit installBootstrap L0 (+ optional packs) and write agent-kit.json
agent-kit statusShow installed kit version and profile
agent-kit doctorDiagnose repository readiness (--json includes an env pillar: bin-on-PATH, npm prefix writability, Node version, shell profile)
agent-kit setup-globalSelf-heal a root-owned npm global prefix (relocate to ~/.npm-global, fix PATH, reinstall)
agent-kit updateRe-apply L0/packs/skills from the registry
agent-kit dashboardStart Mission Control for this workspace (browser panel)
agent-kit mission-controlASCII Mission Control TUI (--once for one frame)
agent-kit add <id>Install a skill or L1 pack
agent-kit run <slash>One headless session from an L0 slash file (numbered-list HITL; never git-prod)
agent-kit run-planHeadless continuous plan runner (never promotes to production)
agent-kit run-plan-allHeadless /run-plan-all queue from the L0 file (same as run run-plan-all; never git-prod)

Run agent-kit --help or agent-kit <command> --help for the full surface.

Docs

版本与发布记录

@dadado/agent-kit-cli 共发布 77 个版本,首次发布于 2026/07/20;过去 12 个月发布了 77 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
6.16.1latest2026/11/11今天
6.16.02026/11/11今天
6.15.02026/11/091 天前
6.14.02026/11/083 天前
6.13.12026/11/037 天前
6.12.02026/10/2813 天前

关于 @dadado/agent-kit-cli 的常见问题

@dadado/agent-kit-cli 是什么?

Agent Kit CLI: HITL framework install and tooling for AI-assisted IDEs (rules, skills, plan/handoff, context).

如何安装 @dadado/agent-kit-cli?

在项目目录运行 npm install @dadado/agent-kit-cli,或使用 pnpm add / yarn add / bun add。它还提供命令行工具 agent-kit,可以用 npx agent-kit 直接运行。

@dadado/agent-kit-cli 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@dadado/agent-kit-cli 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@dadado/agent-kit-cli 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=22.12。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@dadado/agent-kit-cli 可以商用吗?

@dadado/agent-kit-cli 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@dadado/agent-kit-cli 的下载量有多少?

根据 npm 官方下载统计,@dadado/agent-kit-cli 在 2026/10/11 – 2026/11/09 这 30 天内被下载 3,939 次,日均约 131 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@dadado/agent-kit-cli 还在维护吗?

最新版本 6.16.1 发布于 2026/11/11(今天);至今共发布 77 个版本,其中过去 12 个月发布了 77 个;首次发布于 2026/07/20。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。