---
pretty_name: Verizon Codex Trace
configs:
- config_name: sessions
  data_files:
  - split: train
    path: sessions/*.jsonl
tags:
- agent-traces
- codex
- computer-use
- verizon
---

# Verizon Codex Trace

A sanitized Codex session trace of GPT-5.5/Codex working through a Verizon billing and trade-in support flow.

The trace includes the original JSONL session structure, assistant/user turns, tool calls, shell output, selected Computer Use browser screenshots, and the Verizon live-chat/bill context needed to understand the agent's work.

## What's included

- One saved Codex session JSONL under `sessions/`
- Assistant messages, user messages, tool calls, and tool outputs
- Selected Verizon screenshots from bill pages and live chat
- Shell/tool output where it helps reconstruct the workflow

## Redactions

The trace was sanitized before upload.

Removed or redacted:

- top-level system/developer/local `AGENTS.md` instructions
- Gmail search queries, email tool results, and Gmail metadata
- email addresses, phone numbers, partial phone fragments, street address, account IDs, session IDs, URL query strings, and trade order IDs
- unrelated browser screenshots and unrelated browser context
- hidden Computer Use accessibility trees for retained screenshots

Intentionally retained:

- selected Verizon screenshots that show the useful bill/chat flow
- names and dollar amounts where they are part of the visible support/billing story
- shell/tool outputs that are not personal or unrelated

## Notes

This is a real-world agent trace, so it is best treated as a workflow/debugging artifact rather than a polished benchmark. Verizon UI, logos, and bill/chat screenshots appear only as captured browser context from the session.