Introduction

agentcn is a registry of complete, production-ready agent recipes. It is not a UI component registry — each recipe distributes the backend agent files (instructions, tools, skills, workflows) that you copy straight into your project with the shadcn CLI.

Philosophy

agentcn follows the shadcn model for backend agents: copy-paste recipes you can own, with zero lock-in and sensible defaults that work immediately.

Agents are too often shipped as opaque packages — you import a black box and fight its constraints the moment you need something different. agentcn takes the opposite approach. You get the full source of each agent and stay close to your framework's primitives, so you can read every line, swap the model, extend the tools, or reshape the output without working around a library.

Why agentcn?

Most agent setups are either too opinionated or too scattered. agentcn is built for teams that want to ship quickly without giving up control:

• Own Your Code: Copy recipes into your project and customize everything.
• Start Fast: Run one command and get a working agent with production-ready defaults.
• Scale Safely: Build on Eve or Flue directly, then drop to the raw framework APIs whenever you need more control.

Frameworks

Every recipe ships in both flavors where it makes sense, so you can adopt the pattern in whichever framework you already use:

• Eve — a filesystem-first framework for durable backend AI agents that run on Vercel Functions.
• Flue — an agent runtime with first-class subagents, skills, and bounded workflows.

Features