Install eve agents with the shadcn CLI
Add any evex agent to your eve project with npx shadcn add. Prerequisites, what the CLI writes, and how to configure and verify the agent after install.
Prerequisites: an eve project
Agents install into an eve project: the CLI writes the agent/ directory layout that the eve framework loads at runtime. If you do not have an eve app yet, create one first and run every install command from its root.
eve requires Node.js 24 or newer. npx, bundled with Node, downloads and runs both the eve and shadcn CLIs on demand, so no global installs are needed.
npx eve@latest init my-agentcd my-agentRun the install command
Every agent installs with a single command. Replace the slug with the agent you picked from the catalog; the exact command is shown on every agent page.
evex is part of the official shadcn community registry, so the @evex namespace resolves without any registry configuration on your side.
npx shadcn@latest add @evex/{slug}npx shadcn@latest add @evex/code-reviewerWhat the CLI writes
The CLI fetches the registry item and writes the agent package into your project. You can preview the full file list on the agent page before running anything.
- agent/ - the agent source: configuration, instructions, skills, tools, and subagents
- evals/ - the eval suite the author ships with the agent
- README.md - setup and usage notes written by the author
- .env.example - present when the agent reads environment variables, listing every variable it needs
- npm dependencies declared by the agent, which the CLI prompts you to install
After the install
Three steps take you from installed files to a working agent.
- Copy .env.example values into your environment and fill in real credentials; the template names every variable the agent reads
- Read the installed README.md for agent-specific setup, usage, and caveats
- Run the evals under evals/ to confirm the agent behaves as expected in your project
Troubleshooting
If the CLI writes files somewhere unexpected or the agent fails to load, check that you ran the command from the root of an eve app. The installed files assume the eve framework is present: create a project with npx eve@latest init, or add eve to an existing package with npm install eve@latest, then rerun the install.
If the CLI prompts you to install npm packages, those are the dependencies the agent declares in its registry item. The list matches the dependencies shown on the agent page, so review it there first and accept the prompt to complete the install.