Skip to main content

​
What is BYOA?

BYOA (Bring Your Own Agent) lets you choose which Agent runtime powers Manager’s Workers. Instead of only using Verdent’s default Agents, Worker tasks dispatched by Manager can run on an Agent you already use or are licensed for.
Looking to use your own provider API key with Verdent’s built-in agents instead? See BYOK.

​
Supported Agent Types

AgentDescriptionPrerequisites
Built-in AgentDefault Agent provided by VerdentNone
Claude CodeAnthropic’s Claude Code CLINode.js installed (for npx)
CodexOpenAI Codex CLICodex CLI installed and OpenAI environment configured

​
Use Cases

  • Access specific models — Expose model versions not included in Verdent’s default set through the model selector.
  • Team standardization — Use a shared enterprise license so team usage is billed centrally.
  • Familiar workflow — Keep your existing Claude Code or Codex experience while letting Manager dispatch Worker tasks to it.

​
Quick Access

  • BYOA settings: Settings → Models → CLI Agents
  • Model selection in Manager chat: turn off Auto mode in the input box to pick a Task Model
  • API keys configured in BYOA are stored locally only and are never uploaded to Verdent servers

​
Codex

Codex is OpenAI’s coding agent CLI. Unlike Claude Code, Codex does not require an API key inside Verdent — it uses the authentication already set up in your local Codex environment.

​
Prerequisites

  • Codex CLI installed (codex must be available on your PATH)
  • Codex CLI authenticated and usable in your terminal

​
Setup Steps

1

Open CLI Agents settings

Go to Settings → Models → CLI Agents.
2

Add Codex if missing

If the Codex card is not visible, click Add CLI Agent. Verdent scans your system PATH for the codex command.
3

Enable Codex

Turn on the Codex toggle.
4

Select models

Verdent automatically detects available models. Select the ones you want to use.

​
Model Discovery

Codex models are dynamically discovered. After launching Codex, Verdent fetches available models via its /models API. If new models are added on the Codex side, click Refresh Models to update the list.

​
Authentication

Verdent does not manage Codex authentication. Codex relies on your local shell environment (typically OPENAI_API_KEY or its built-in login flow). As long as codex works in your terminal, the integration works.

​
Claude Code

Claude Code is the most feature-rich Agent in BYOA and supports multiple providers. You can connect Anthropic, OpenRouter, Zhipu GLM, and others, and switch between them in the model selector.

​
Prerequisites

  • Node.js installed (only npx is required)
Verdent launches Claude Code via: 
npx -y @agentclientprotocol/claude-agent-acp
No global installation is required.

​
Setup Steps

1

Open CLI Agents settings

Go to Settings → Models → CLI Agents.
2

Add Claude Code if missing

If the Claude Code card is not visible, click Add CLI Agent. Verdent detects npx.
3

Enable Claude Code

Turn on the Claude Code toggle.
4

Add a provider

Click Add provider and select a provider (for example, Anthropic).
5

Enter credentials

Enter the API key. Default values are auto-filled.
6

Test and save

Optionally click Test Connection, then click Save.
After saving, models under the provider appear in the model list. Enabled models are selected by default but can be toggled manually.

​
Supported Providers

Claude Code supports multiple providers. You can configure several at once, and all models appear in the selector.

​
Anthropic

Official Anthropic API for Claude models.

​
OpenRouter

Unified API access to multiple model providers. You can override Role Models to route to other OpenRouter models (for example, google/gemini-2.5-pro).

​
Zhipu GLM (China)

​
Zhipu GLM (Global)

​
Kimi

​
Moonshot

Kimi and Moonshot both provide Kimi K2.5 but use different endpoints and authentication. Choose based on where your key comes from.

​
MiniMax (China)

​
MiniMax (Global)

​
Xiaomi MiMo

​
Xiaomi MiMo (Token Plan)

​
Anthropic-Compatible (Custom Endpoint)

For any service compatible with the Anthropic API format.
  • Auth: API Key or Token (switchable)
  • Base URL: manually configured
  • Models: manually specified
Use this if your provider is not listed but supports Anthropic-compatible APIs.

​
Advanced Options

In the provider configuration panel, expand Advanced Options to access a JSON editor:
  • Role Models mapping:
    • ANTHROPIC_DEFAULT_OPUS_MODEL
    • ANTHROPIC_DEFAULT_SONNET_MODEL
    • ANTHROPIC_DEFAULT_HAIKU_MODEL
    • CLAUDE_CODE_SUBAGENT_MODEL
  • Custom environment variables (for example, API_TIMEOUT_MS)
Most users don’t need to modify these — defaults work well out of the box.

​
Using BYOA Models in Manager

After configuration:
1

Disable Auto mode

Turn off Auto mode in the chat input.
2

Open Task Model

Open the Task Model dropdown.
3

Select a BYOA model

Pick any enabled BYOA model. Worker tasks will run using that model.
Models appear as:
  • GPT-5.4 Codex-CLI (from Codex)
  • Claude-Opus-4.7 ClaudeCode-CLI (from Claude Code)
Hovering shows details such as CLI source, model name, and provider.

​
Security & Privacy

  • Local storage only: API keys are stored locally and never uploaded.
  • Claude Code keys: stored securely, not written to plain config files.
  • Codex authentication: fully managed by your local environment; Verdent does not access OpenAI keys.

​
FAQ

​
CLI Agent not detected?

Ensure commands are available in PATH:
  • Claude Code requires npx (Node.js installed)
  • Codex requires the codex CLI installed
Run: 
which npx
which codex

​
Test Connection failed?

  • Verify API key
  • Check base URL
  • Ensure network access to the API endpoint
  • Check proxy configuration if used

​
Provider added but models not visible?

  • Ensure Claude Code is enabled
  • Ensure provider models are toggled on
  • Restart Verdent if needed