Targets Configuration

Targets define which agent or LLM provider to evaluate. They are configured in .agentv/targets.yaml to decouple eval files from provider details.

Structure

targets:
  - name: azure_base
    provider: azure
    endpoint: ${{ AZURE_OPENAI_ENDPOINT }}
    api_key: ${{ AZURE_OPENAI_API_KEY }}
    model: ${{ AZURE_DEPLOYMENT_NAME }}

  - name: vscode_dev
    provider: vscode
    workspace_template: ${{ WORKSPACE_PATH }}
    judge_target: azure_base

  - name: local_agent
    provider: cli
    command_template: 'python agent.py --prompt {PROMPT}'
    judge_target: azure_base

Environment Variables

Use ${{ VARIABLE_NAME }} syntax to reference values from your .env file:

targets:
  - name: my_target
    provider: anthropic
    api_key: ${{ ANTHROPIC_API_KEY }}
    model: ${{ ANTHROPIC_MODEL }}

This keeps secrets out of version-controlled files.

Supported Providers

Provider	Type	Description
azure	LLM	Azure OpenAI
anthropic	LLM	Anthropic Claude API
gemini	LLM	Google Gemini
claude-code	Agent	Claude Code CLI
codex	Agent	Codex CLI
pi-coding-agent	Agent	Pi Coding Agent
vscode	Agent	VS Code with Copilot
vscode-insiders	Agent	VS Code Insiders
cli	Agent	Any CLI command
mock	Testing	Mock provider for dry runs

Referencing Targets in Evals

Set the default target at the top level or override per case:

# Top-level default
execution:
  target: azure_base

evalcases:
  - id: test-1
    # Uses azure_base

  - id: test-2
    execution:
      target: vscode_dev  # Override for this case

Judge Target

Agent targets that need LLM-based evaluation specify a judge_target — the LLM used to run LLM judge evaluators:

targets:
  - name: codex_target
    provider: codex
    judge_target: azure_base  # LLM used for judging

Workspace Template

For agent targets, workspace_template specifies a directory that gets copied to a temporary location before each eval case runs. This provides isolated, reproducible workspaces.

targets:
  - name: claude_code
    provider: claude-code
    workspace_template: ./workspace-templates/my-project
    judge_target: azure_base

When workspace_template is set:

• The template directory is copied to ~/.agentv/workspaces/<eval-run-id>/<case-id>/
• The .git directory is skipped during copy
• Each eval case gets its own isolated copy

Cleanup Behavior

By default:

• Success: Workspace is cleaned up automatically
• Failure: Workspace is preserved for debugging

Override with CLI flags:

• --keep-workspaces: Always preserve workspaces
• --cleanup-workspaces: Always clean up, even on failure

cwd vs workspace_template

Option	Use Case
cwd	Run in an existing directory (shared across cases)
workspace_template	Copy template to temp location (isolated per case)

These options are mutually exclusive. If neither is set, the eval file’s directory is used as the working directory.