backend-dev — Claude Code subagent for APIs: setup
The backend-dev subagent builds backend APIs and draws on earlier API work. Use it for tasks involving endpoints, routes, REST, or GraphQL.
no license ★ 850 updated 2026-10-26
.claude/agents/dev-backend-api.mdWhat backend-dev does
backend-dev can read and edit project files related to APIs, including routes, controllers, and models. Before a task, it searches memory for similar successful work. Afterwards, it runs npm run test:api and stores the outcome for later tasks; a passing test also triggers coordination-pattern training.
The agent works with .js, .ts, .json, .yaml, and .yml files in permitted directories such as src/, api/, and tests/. It cannot work in node_modules/, .git/, dist/, or build/, and web search is restricted. Database migrations, breaking API changes, and authentication changes require confirmation. Some work also needs approval from architecture.
What it helps with
- create a user authentication endpoint
- add a route to an API
- build a CRUD API for products
- run API tests after making changes
Example prompts for the agent
- Create an endpoint for user authentication.
- Build a CRUD API for products with input validation.
- Add a route for retrieving a user profile.
How to install backend-dev
Manually: put the files in place
.claude/agents/dev-backend-api.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/dev-backend-api.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/dev-backend-api.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about backend-dev
How do I install backend-dev in Claude Code?
Add the agent file at .claude/agents/dev-backend-api.md.
What does backend-dev do?
It helps build backend APIs, searches memory for related past work, and runs npm run test:api after implementation.
Which changes need confirmation from backend-dev?
It asks for confirmation before database migrations, breaking API changes, and authentication changes.