@ai-driven-dev/cli installs AI tool runtime configs, IDE integrations, and plugins from an AIDD marketplace into a project. Every file it writes is hash-tracked in a manifest, so drift is detected and owned files can be restored.

Supported AI tools: Claude Code, Cursor, GitHub Copilot, Codex, OpenCode, Kilo Code. Supported IDE: VS Code. Requires Node.js >= 22.12, and git to fetch marketplace plugins.

Run without installing:

npx @ai-driven-dev/cli@latest setup

Or install once for every project:

npm install -g @ai-driven-dev/cli@latest
aidd --version

aidd setup --ai claude --ide vscode --plugins recommended --yes
aidd plugin install aidd-dev
aidd doctor
aidd sync
aidd update

The first command bootstraps the project: manifest, default marketplace, tool configs, plugins. --scope user on setup registers the framework source and supported tools machine-wide instead, and writes nothing under the project. See the scope support below.

Not needed for the public marketplace. Needed for a private one.

Two methods are stored in auth.json:

• stored: the token itself is written to the file, from --token <value>.
• external: only the provider name is written, and the token is asked from it at fetch time, from --gh.

Token resolution stops at the first hit:

1. AIDD_TOKEN.
2. The project file, .aidd/auth.json.
3. The user file, auth.json in the user config directory.

aidd auth login --level project writes the project file, --level user the user one. aidd plugin install --token <value> and aidd marketplace add --token <value> pass a token for one call without storing it.

Run aidd --help, then a group's own --help, for flags this page does not repeat.

setup, doctor, sync and clean accept --scope <project|user>. Project scope is the default and acts on this project alone.

setup --scope user requires an explicit supported --ai list, no --ide, and --plugins none (or omit --plugins in a scripted run). It records the source and tools in the user registry without installing tool configuration files or enabling plugins. --ai all includes unsupported tools and is refused.

Native activation requires the corresponding claude, codex, or copilot executable on PATH. When it is missing, registration succeeds with a warning and activation remains unrun; install the host CLI, then run aidd sync --scope user.

aidd setup --scope user --ai claude,codex,copilot --plugins none --yes

aidd setup --help prints the same support list, generated from the registry.

aidd translate <source> --to <tool> --out <dir> converts a framework source tree into a target-native plugin tree. It records nothing in the manifest, unlike aidd sync. It is the author-side command that produces what consumers install.

Two output layouts, chosen by --as:

• marketplace, the default: a self-contained marketplace tree the consumer registers with aidd marketplace add, with plugin paths rewritten to the target's own plugin-root token.
• flat: plugin content materialized straight under the target's workspace directory, with no marketplace step. --force overwrites files already at those paths, and applies to this layout only.

OpenCode and Kilo Code declare no marketplace contract, so they are flat only. Every other target accepts both layouts.

In the project:

On the machine, under $AIDD_USER_CONFIG_DIR, else $XDG_CONFIG_HOME/aidd, else ~/.config/aidd:

• auth.json, the user-level credential.
• marketplaces.json and references.json, the user-scope registry and the projects claiming it.
• manifest.json, what --scope user owns.
• cache/built/<version>/, one built tree per CLI version.

Per tool, the settings file the CLI writes:

• Architecture
• Write a plugin
• Marketplace
• Glossary
• FAQ
• Contributing