# AI DevKit > English | [中文](./README-zh.md) **The control plane for AI coding agents.** ![](agent-console-showcase.jpg) AI DevKit gives Claude Code, Codex CLI, Gemini CLI, opencode, Pi, Cursor, GitHub Copilot, Devin, and other coding agents one local-first operating layer: one config, one console, local memory retrieval, cross-agent communication, and composable engineering skills led by `dev-lifecycle`. - **One config for every agent** — `.ai-devkit.json` reconciles setup across the coding tools your team uses - **One console for running sessions** — `agent console` is a live TUI dashboard for supervising local agents across providers - **Cross-agent communication** — `agent send` lets you route prompts, logs, and test output to running agents - **Memory retrieval without context bloat** — `@ai-devkit/memory` stores decisions, conventions, and fixes in local SQLite so agents search when needed instead of carrying everything in every prompt - **Composable engineering skills** — `dev-lifecycle`, `verify`, `tdd`, review, debugging, security, docs, and simplification skills combine into reliable workflows The future is many AI coding agents. AI DevKit is the layer that makes them manageable. Run machine setup once, then `init` in each project: ```bash npx ai-devkit@latest setup cd your-project npx ai-devkit@latest init ``` `setup` installs built-in skills globally, session hooks, and the memory MCP wiring for detected agents. The `kiro`, `copilot`, `devin`, and `muse` targets detect `~/.kiro`, `~/.copilot`, `~/.config/devin`, and `~/.config/muse`, respectively. Copilot skills use the `github` environment and `~/.copilot/skills`; Devin and Muse use `~/.config/devin/skills` and `~/.config/muse/skills`. Kiro has no skill environment or root defined, so its target only detects the marker and reports the memory MCP skip. All four skip memory MCP wiring until a global config writer is verified. `init` writes project-local config. Your project gets: | What you need | What AI DevKit installs | |---------------|-------------------------| | One setup source | `.ai-devkit.json` for the agents and workflow you choose | | Running-agent visibility | `agent list`, `agent detail`, and `agent console` | | Addressable agents | `agent send`, `--stdin`, `--wait`, and agent groups where supported | | Retrieval-based memory | Local SQLite memory exposed through MCP and CLI, searched only when useful | | Composable senior-engineer workflow | `dev-lifecycle` plus verification, TDD, debugging, review, security, docs, and simplification skills | [![npm version](https://img.shields.io/npm/v/ai-devkit.svg)](https://www.npmjs.com/package/ai-devkit) [![npm downloads](https://img.shields.io/npm/dt/ai-devkit.svg)](https://www.npmjs.com/package/ai-devkit) [![GitHub stars](https://img.shields.io/github/stars/Codeaholicguy/ai-devkit.svg?style=social)](https://github.com/Codeaholicguy/ai-devkit) [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0) ## Who this is for Developers whose AI coding setup has grown from one assistant into a small, messy team of agents: - multiple terminals with no shared control surface - separate `CLAUDE.md` / `.cursor/rules` / `AGENTS.md` / MCP setup per tool - no easy way to send context, logs, or follow-up work to a running agent - the agent forgetting yesterday's conventions - "I've successfully implemented the feature" with a red build - the agent diving into code without a plan and producing the wrong thing Before AI DevKit, your agents are powerful but scattered. After AI DevKit, they have shared setup, a control surface, searchable memory, communication paths, and reusable skills that travel with your repo without bloating every prompt. | Without AI DevKit | With AI DevKit | |-------------------|----------------| | You manage agents as isolated terminal tabs | You supervise them from `ai-devkit agent console` | | You hand-maintain every agent setup | One config reconciles agent files, skills, and MCP setup | | You copy logs and context between sessions | `agent send` routes prompts and stdin to running agents | | You repeat project rules in every chat | Agents retrieve relevant memory and docs only when useful | | The agent jumps from prompt to code | `dev-lifecycle` guides requirements, design, planning, implementation, testing, and review | | "Done" means the agent stopped editing | "Done" requires fresh verification output | ## Start in 30 seconds ```bash npx ai-devkit@latest setup cd your-project npx ai-devkit@latest init ``` Run `setup` once per machine, then `init` per project. Pick your agents, install the control-plane pieces you need, and give every tool the same operating model. Re-run `init` whenever your agent list or workflow changes. Multi-agent orchestration (lead plus workers): **[docs guide](https://ai-devkit.com/docs/17-multi-agent-orchestration/)**. Here's what lands in your repo: ``` your-project/ ├── .ai-devkit.json # single source of truth (re-run init anytime) ├── .claude/ # or .cursor/, .codex/, etc. per agent you picked │ ├── skills/ # dev-lifecycle, verify, memory, tdd, ... │ └── … # Claude: project MCP in `.mcp.json`; memory MCP wired globally by `setup` └── docs/ai/ ├── requirements/ # phase 1 — what to build, why ├── design/ # phase 2 — how it'll be built ├── planning/ # phase 3 — task-by-task plan ├── implementation/ # phase 4 — execution notes └── testing/ # phase 5 — coverage strategy ``` ## Operate agents like infrastructure AI DevKit ships an agent control plane for everyday multi-agent work: ```bash # List running sessions across providers ai-devkit agent list # Open the live terminal UI ai-devkit agent console # Send a prompt to a running session and wait for the response ai-devkit agent send "run the tests and report back" --id --wait # Pipe multi-line output into a running session npm test 2>&1 | ai-devkit agent send --id --stdin # Send a prompt to a saved group of agents ai-devkit agent send "review this branch for release risk" --group reviewers # Pipe a session through Telegram — operate your agent from your phone ai-devkit channel start telegram --agent --daemon ``` Use this when work spans long-running agents, multiple providers, scheduled checks, review loops, or remote control from another channel. ## Add memory without bloating context AI DevKit memory is local SQLite knowledge for project decisions, coding conventions, and reusable fixes. Agents retrieve it when a task needs context instead of carrying every fact in every prompt. ```bash # Store a reusable project convention ai-devkit memory store \ --title "API handlers return DTOs" \ --content "REST handlers should return response DTOs instead of domain entities." \ --tags "api,backend" \ --scope "repo:codeaholicguy/ai-devkit" # Search before related work ai-devkit memory search --query "API response convention" ``` ## Compose engineering workflows with skills The control plane is useful on its own. For larger or riskier changes, AI DevKit also installs composable skills that make agents behave more like an engineering team. `dev-lifecycle` is the anchor skill. It guides the agent through requirements, design, planning, implementation, testing, and review. Other skills plug into that flow: - `memory` retrieves relevant project knowledge without stuffing all context into the session - `verify` blocks completion claims without fresh test or build evidence - `tdd` pushes test-first implementation when behavior changes - `dev-debug` keeps debugging reproducible instead of guess-and-patch - `security-review`, `document-code`, and `dev-simplify` add focused review passes when the task needs them ### Get the full engineering workflow stack Save [`templates/senior-engineer.yaml`](./templates/senior-engineer.yaml) locally and run: ```bash ai-devkit init --template ./senior-engineer.yaml ``` Bundles the built-in skills with curated additions from Anthropic, Vercel, and others: TDD, frontend design, webapp testing, doc co-authoring, React best practices, security review, and more. ## A feature, end-to-end ``` You: Use the dev-lifecycle skill to start requirements for OAuth login with Google Agent: Searches memory for prior auth conventions. Asks clarifying questions about scope, users, success criteria. Drafts docs/ai/{requirements,design,planning}/feature-oauth-login.md in a feature worktree. Stops before coding. You: Ask for a design review of feature-oauth-login Agent: Audits the design doc against the requirements. Flags gaps, proposes fixes — before any code gets written. You: Ask it to execute the implementation plan Agent: Works the planning doc task-by-task. Updates progress after each task. The `verify` skill blocks a task from being marked done without fresh test/build output. You: Ask for a code review Agent: Audits the diff against the design doc — scope creep, missing tests, edge cases the requirements named — before you push. ``` ## What changes in agent behavior The flow above is powered by **28 built-in skills** (installed globally by `setup`), including these core workflow skills: | Failure mode | AI DevKit behavior | |--------------|--------------------| | Agent starts coding too early | `dev-lifecycle` forces requirements, design, planning, implementation, tests, and review | | Agent says "done" without proof | `verify` blocks completion claims without fresh test/build evidence | | Agent commits unrelated local changes | `dev-commit` checks diffs, stages explicit paths, validates, and reports the SHA/status | | Agent forgets project decisions | `memory` gives it a local, searchable knowledge base across sessions and projects | | New behavior ships without tests | `tdd` pushes test-first implementation | | Debugging becomes guess-and-patch | `dev-debug` makes it reproduce, hypothesize, fix, and verify | | Existing code is opaque | `document-code` maps entry points, dependencies, and behavior | | Implementation gets bloated | `dev-simplify` reduces complexity before code ships | | Unit tests pass but the flow is broken | `dev-smoke` smoke-tests the affected flows end to end in a sandbox | | The same mistake keeps coming back | `dev-retro` turns friction into tests, checks, or skill fixes | | Documentation is hard to follow | `document-code` maps code; add community `technical-writer` via `skill add` if needed | Need more? `ai-devkit skill add ` pulls from 30+ publishers — Anthropic, Vercel, Supabase, Microsoft, Google. See the full built-in list in [Skills docs](https://ai-devkit.com/docs/7-skills/). ## Works across coding agents One `.ai-devkit.json` configures all of them. Add a new agent to your team without rewriting your rules. | Agent / environment | Project `init` setup | `agent start` / `send` control plane | |-------|-------|----------------| | [Claude Code](https://www.anthropic.com/claude-code) | yes | yes (`claude`) | | [Gemini CLI](https://github.com/google-gemini/gemini-cli) | yes | yes (`gemini_cli`) | | [Codex CLI](https://github.com/openai/codex) | yes | yes (`codex`) | | [Grok Build CLI](https://x.ai/cli) | yes | yes (`grok_cli`) | | [opencode](https://opencode.ai/) | yes | yes (`opencode`) | | [Pi](https://pi.dev) | yes | yes (`pi`) | | [GitHub Copilot](https://github.com/features/copilot) | yes | yes (`copilot`) | | [Kiro CLI](https://kiro.dev/cli/) | yes | yes (`kiro`) | | [Devin](https://devin.ai/) | yes | yes (`devin`) | | [Muse Code](https://dev.meta.ai/products/muse-code/) | yes | yes (`muse`) | | [Antigravity CLI](https://antigravity.google/) | yes | yes (`antigravity_cli`) | | [Cursor](https://cursor.sh/) | yes | — | | [Junie](https://www.jetbrains.com/junie/) | yes | setup/skills only | | [Cline](https://cline.bot/) | yes | setup/skills only | | [Antigravity IDE](https://antigravity.google/) | yes | setup/skills only | | [Amp](https://ampcode.com/) | yes | setup/skills only | | [Kilo Code](https://github.com/Kilo-Org/kilocode) | yes | setup/skills only | | [Roo Code](https://roocode.com/) | testing | setup/skills only | **Setup** — `ai-devkit setup` (machine) plus `ai-devkit init` (project) writes each agent's config (rules, MCP, skills). **Control plane** — `agent list`, `agent send`, and managed `agent start` target tmux-backed CLI sessions on **macOS/Linux** (experimental console; requires tmux). Use [channels](https://ai-devkit.com/docs/12-channel/) to message a running agent from Telegram or Slack. Not supported on Windows console. ## How is this different from `CLAUDE.md`, `.cursor/rules`, or `AGENTS.md`? Those files are static instructions the agent re-reads. AI DevKit gives agents an **operating layer**: generated setup, a control console, cross-agent messaging, local searchable memory, phase docs, skills loaded on demand, and verification gates. The rules still matter, but AI DevKit makes them operational across tools. | Static rules files | AI DevKit | |--------------------|-----------| | Tell one agent what you prefer | Reconciles setup across supported agents | | Do not show what is running | Lists, inspects, and controls live sessions | | Cannot send work between sessions | Routes prompts, stdin, and channel messages to agents | | Depend on the agent remembering every rule | Stores and searches reusable project knowledge | | Cannot prove a task is complete | Requires fresh command output before completion claims | ## What this isn't - **Not a smarter LLM.** Bad models stay bad — this raises the floor on process, not on raw capability. - **Not a replacement for Claude Code, Codex, Cursor, Gemini CLI, or opencode.** AI DevKit configures, supervises, and coordinates the agents you already use. - **Not a magic "write the feature for me" button.** You still review the requirements doc, accept the design, and read the diff. The workflow makes that review possible because you have artifacts to point at instead of only chat scrollback. - **Not a hosted service.** Apache-2.0-licensed, runs locally, no telemetry. Memory is a SQLite file on your disk. The control plane detects CLI sessions, types into tmux panes, and reads session files — it does not run a remote cloud agent for you. ## Documentation & community - Full guides, workflow patterns, skill authoring → **[ai-devkit.com/docs](https://ai-devkit.com/docs/)** - Release notes → **[CHANGELOG.md](./CHANGELOG.md)** - Contributing → open an issue or PR on **[GitHub](https://github.com/Codeaholicguy/ai-devkit)** ```bash git clone https://github.com/Codeaholicguy/ai-devkit.git cd ai-devkit && npm install && npm run build ``` ## License Apache License 2.0 ## Star History Star History Chart