Skip to main content
subagent CX Codex

backend-developer · voltagent/awesome-codex-subagents — Codex subagent: what it does and install

backend-developer is a Codex subagent for scoped backend implementation and bug fixes once the owning code path is known. It checks a success case and a high-risk failure path.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/backend-developer.toml
Open on GitHub

What backend-developer does

backend-developer traces the entry point, domain boundary, and persistence effects before changing backend behavior. It makes the smallest coherent change for the task, then checks input handling, access rules, transactions, and retry behavior where those paths are affected.

Its report lists changed files and backend paths, summarizes the behavior change and validation, and notes remaining risks or follow-up checks. Write-path changes get a persistence and rollback check. The agent leaves unrelated refactoring out unless the parent agent explicitly requests it.

What it helps with

  • fix a bug in a backend request handler
  • keep domain logic within its service boundary
  • preserve authorization checks while changing an API path
  • verify rollback behavior after a failed write

Example prompts for the agent

  • Fix the bug in this backend request handler.
  • Change the permission check for this API path and test the denied case.
  • Check that this write operation rolls back on failure.

How to install backend-developer

Manually: put the files in place

.codex/agents/backend-developer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/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-developer

How do I install backend-developer in Codex?

Add the agent file at .codex/agents/backend-developer.toml.

What does backend-developer do?

It makes scoped backend changes and fixes bugs, then validates a success path and a high-risk failure path.

What does backend-developer check for write-path changes?

It checks persistence and rollback behavior. It also verifies access rules on paths changed by the task.

Source text

backend-developer.toml · MIT
# backend-developer

Use when a task needs scoped backend implementation or backend bug fixes after the owning path is known.

Own backend changes as production behavior with explicit data, auth, and failure-path integrity.

Working mode:
1. Map entry point, domain logic boundary, and persistence side effects.
2. Implement the smallest coherent change that fixes or delivers the target behavior.
3. Validate behavior under normal and high-risk failure paths.

Focus on:
- request/event entry points and service boundary ownership
- input validation and contract-safe output behavior
- transaction boundaries and consistency guarantees
- idempotency and retry behavior for side-effecting operations
- authentication/authorization behavior in touched paths
- logging, metrics, and operator-facing error visibility
- backward compatibility for existing clients or downstream consumers

Implementation checks:
- avoid hidden side effects in shared helpers
- keep domain logic centralized, not split across adapters/controllers
- preserve existing behavior outside changed scope
- make failure semantics explicit (timeouts, not found, conflict, transient failure)

Quality checks:
- validate one critical success path and one high-risk failure path
- verify persistence and rollback behavior for changed write paths
- ensure changed path still enforces auth/permission rules
- call out environment dependencies not verifiable in local checks

Return:
- files and backend path changed
- behavior change summary
- validation performed
- residual risk and follow-up verification needed

Do not broaden into unrelated refactors unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Backend and APIs →

backend-developer by other authors comes first.

backend-developer VoltAgent Community backend-developer — a subagent for building backend APIs and microservices in Node.js, Python, and Go. Helps implement relational schemas, caching, and OWASP security rules. CX Codex 2,724installs fullstack-developer VoltAgent Community The fullstack-developer subagent carries a feature across the database, API, and frontend layers. Use it when one change needs a consistent end-to-end implementation. CX Codex 18,117installs backend-engineer First Fluke backend-engineer is a Claude Code subagent for API, authentication, and database migration tasks. It joins work on those tasks when requested. CX Codex ★ 1,472repo stars backend-architect Community Guides API design, database optimization, and scalable backend architecture. Activate it when designing server endpoints, securing authentication systems, or tuning query performance. ★ 2,003repo stars engineering-backend-architect PeterHdd The engineering-backend-architect Claude Code skill plans backend architecture, data models, and APIs. It activates for service-boundary choices, query tuning, and database migration plans. CX Codex +1 356installs backend-development-performance-engineer Seth Hobson backend-development-performance-engineer is a Claude Code subagent that reviews performance in newly built features. It looks for slow responses, memory use, and inefficient queries during development. CX Codex ★ 42,780repo stars replica-backend Jakeschincariol Builds the backend of an app clone: auth, database migrations and access rules, Stripe payments, email and background jobs. Reads replica/architecture.md and keeps a checklist in replica/backend.md. CX Codex +1 1,600installs

From the same set176

The whole set →
graphql-architect graphql-architect — a subagent that audits GraphQL schemas for architectural flaws, performance risks, and security gaps. Guides schema evolution, resolver design, and federation without breaking clients. CX Codex ★ 6,505repo stars fullstack-developer fullstack-developer handles bounded cross-layer features from user actions down to backend effects and UI updates. Useful when a single worker needs to own the full integration path. CX Codex ★ 6,505repo stars frontend-developer frontend-developer — a scoped subagent for frontend changes and UI bug fixes, with checks for state integrity, accessibility, and nearby regressions. CX Codex ★ 6,505repo stars electron-pro electron-pro — a subagent for Electron development: helps map responsibility across main, preload, and renderer processes, design IPC bridges, verify security boundaries, and validate packaging assumptions. CX Codex ★ 6,505repo stars design-bridge design-bridge converts DESIGN.md documents into precise, structured UI instructions for implementation agents. CX Codex ★ 6,505repo stars code-mapper The code-mapper subagent maps code paths, ownership boundaries, and execution flow before edits. Use it when behavior is spread across several layers. CX Codex ★ 6,505repo stars api-designer api-designer designs API contracts, plans versioning, and inspects breaking changes before implementation starts in Codex. CX Codex ★ 6,505repo stars healthcare-admin This Codex subagent handles healthcare administration work, including medical coding, compliance reviews, and payer contract analysis. Use it when a task concerns healthcare operations rather than general software development. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open