# Installation

Install an agent recipe into your Eve or Flue project.

> For the complete documentation index, see [llms.txt](/llms.txt). Markdown variants are available by appending `.md` to any URL or sending an `Accept: text/markdown` header. An agent skill is available at [/.well-known/agent-skills/site-skill.md](/.well-known/agent-skills/site-skill.md).



## Prerequisites [#prerequisites]

Complete these before running the install command.

**1. An agent project.** Start from an existing one or scaffold a new project:

* **Eve** — `npx eve@latest init my-agent` ([docs](https://vercel.com/docs/eve)).
  Recipes install under `agent/`, which Eve discovers automatically.
* **Flue** — `npx flue@latest init my-agent` ([docs](https://flueframework.com)).
  Recipes install under `agents/`, `workflows/`, `tools/`, and `skills/`.

**2. The framework package.** Each recipe declares its framework package (`eve`
or `@flue/runtime`) as a dependency, so the shadcn CLI prompts to install it if
it is missing.

**3. Environment variables.** Some recipes call external services and need
secrets set in your project's environment — for example `EXA_API_KEY` for web
search, `WORKSPACE_DIR` for the sandboxed assistant, or a database URL for the
SQL recipe. The required keys are documented in each recipe's tools and
instructions; add them to your `.env` before invoking the agent.

**4. Live preview (optional).** To run a recipe's preview from this docs site,
set `ANTHROPIC_API_KEY`. The Eve preview can additionally proxy a deployed Eve
instance via `EVE_PREVIEW_URL` — see the
[Preview Backend](https://github.com/shadcn-labs/agentcn#preview-backend) notes.

## Add a Recipe [#add-a-recipe]

From your project root, run the install command shown on the recipe's page. For
example, the [Deep Search](/docs/agents/eve/deep-search) agent:

```bash
# Eve
npx shadcn@latest add https://agentcn.vercel.app/r/eve/deep-search.json
```

```bash
# Flue
npx shadcn@latest add https://agentcn.vercel.app/r/flue/deep-search.json
```

The CLI writes the recipe's files into your project at their target paths — for
Eve, under `agent/`; for Flue, under `agents/`, `workflows/`, `tools/`, and
`skills/`. Your framework discovers them automatically.

Prefer short names like `@agentcn/eve/deep-search`? Register the namespace once —
see [Registry](/docs/registry).

## Customize [#customize]

The installed files are plain source — you own them. Common changes:

* **Swap the model** in the agent definition.
* **Extend the tools** by adding files alongside the installed ones.
* **Reshape the output** schema to capture the fields you care about.

See each recipe's **Customization** section for specifics.

## Usage [#usage]

Start your project's dev server (for example `pnpm dev`) and invoke the agent
through your framework — Eve exposes it through a durable session, Flue through
its route handler. You can also try any recipe before installing it using the
**live preview** embedded in its docs page.