Phoenix

AgentV keeps completed runs, traces, transcripts, experiments, and indexes in AgentV-owned local or Git-backed artifacts. The supported zero-infra inspection path is the local Dashboard and result artifact tools. Phoenix is optional external trace infrastructure, not the storage or projection target for AgentV artifacts.

Supported Boundary

AgentV does not export or project completed AgentV runs, traces, transcripts, datasets, experiments, or indexes into Phoenix.

Phoenix can still appear in AgentV workflows in two narrow ways:

• As UI inspiration for local trace and session review.
• As an optional external trace database when Codex, Arize, or another hook already emitted spans independently.

When an AgentV run artifact includes safe external_trace metadata, AgentV may link to that external Phoenix session or trace. Dashboard does not read Phoenix sessions, traces, or spans through a server-side proxy; it opens Phoenix as the external viewer when a safe UI URL is present.

Local Inspection

Use Dashboard for AgentV-owned run and trace review:

agentv dashboard

Dashboard reads configured project run sources, local .agentv/results/ workspaces, remote results repositories, trace sidecars, transcripts, and artifact manifests. It does not require Phoenix, the px CLI, Phoenix database tables, or any Phoenix runtime process.

If a run has safe external_trace.ui_url metadata, the run detail page can show an Open in Phoenix link. Missing Phoenix metadata does not affect AgentV run detail because Dashboard reads AgentV artifacts as the canonical source.

External Trace Metadata

AgentV artifacts may carry metadata such as:

{
  "external_trace": {
    "provider": "phoenix",
    "source": "codex",
    "endpoint": "https://phoenix.example",
    "project": "agentv-dogfood",
    "session_node_id": "UHJvamVjdFNlc3Npb246MQ==",
    "session_id": "codex-session-123",
    "trace_id": "phoenix-trace-456",
    "traceparent": "00-11111111111111111111111111111111-2222222222222222-01",
    "ui_url": "https://phoenix.example/projects/agentv-dogfood/traces/phoenix-trace-456"
  }
}

Only safe link and identity fields should be surfaced. Secrets, API keys, authorization headers, raw tool payloads, and local filesystem paths should stay out of external_trace metadata.

Transcript Boundary

AgentV transcript artifacts are not Phoenix-native conversation inputs. Model-call spans may carry cumulative input messages, so treating Phoenix span inputs as a linear transcript can duplicate prior turns and distort the conversation. Keep transcript, index, and storage semantics in AgentV artifacts; use Phoenix only as optional external context when safe metadata points at an already-existing session.

Non-Goals

• No AgentV-to-Phoenix export or projection of completed runs, traces, transcripts, datasets, experiments, or indexes.
• No Phoenix-owned AgentV transcript, index, or storage model.
• No Dashboard runtime dependency on Phoenix or px.
• No Dashboard Phoenix GraphQL/REST proxy or embedded Phoenix session/span UI.
• No direct Dashboard access to Phoenix database tables.
• No Phoenix dataset or experiment creation as part of the zero-infra local path.
• No browser-side exposure of Phoenix API keys, authorization headers, cookies, or tokens.