Integrations / Agent Integrations

Coding Agents Overview

Browse docs

--- title: "Coding Agents Overview" description: "Choose the right Aurora integration path for Claude Code, Codex, OpenCode, and other coding agents." icon: "bot" ---

Overview

Aurora can sit between coding agents and upstream model providers. The right integration path depends on the API shape the agent expects.

Recommended paths

Agent type	Preferred Aurora path	Notes
Claude Code	Anthropic-compatible translation or passthrough	Use aliases for `ANTHROPIC_MODEL` and subagent models.
Codex	`/v1/responses`	Codex custom providers work well with Aurora's Responses API.
OpenCode and OpenAI-format agents	`/v1/chat/completions` or `/v1/responses`	Point the base URL at Aurora and use a gateway key.
Provider-native SDKs	`/p/{provider}/...` passthrough	Use only when the SDK requires native provider schemas.

Why use Aurora with agents

Aurora gives operators one control plane for:

model aliases and safe model swaps
per-team budgets and usage analytics
audit logs for agent activity
guardrails and workflow policy
fallback, resilience, and provider pools
managed keys instead of shared provider secrets

Setup pattern

Configure at least one upstream provider.
Create stable aliases for agent-facing model names.
Issue a managed API key for the agent or team.
Bind the key to a user_path such as /agents/codex/team-alpha.
Point the agent base URL at Aurora.
Verify requests in usage and audit logs.

See the dedicated Claude Code, Codex, and OpenAI-format agent guides for tool-specific examples.

Recommended paths

Agent type	Preferred Aurora path	Notes
Claude Code	Anthropic-compatible translation or passthrough	Use aliases for `ANTHROPIC_MODEL` and subagent models.
Codex	`/v1/responses`	Codex custom providers work well with Aurora's Responses API.
OpenCode and OpenAI-format agents	`/v1/chat/completions` or `/v1/responses`	Point the base URL at Aurora and use a gateway key.
Provider-native SDKs	`/p/{provider}/...` passthrough	Use only when the SDK requires native provider schemas.

Setup pattern

Configure at least one upstream provider.

Create stable aliases for agent-facing model names.

Issue a managed API key for the agent or team.

Bind the key to a user_path such as /agents/codex/team-alpha.

Point the agent base URL at Aurora.

Verify requests in usage and audit logs.

See the dedicated Claude Code, Codex, and OpenAI-format agent guides for tool-specific examples.