metadata
pretty_name: Agent Manager session — codex check
license: apache-2.0
language:
- en
tags:
- agent-traces
- agent-manager
- coding-agent
- traces
- tool-use
configs:
- config_name: default
data_files:
- split: train
path: '*.jsonl'
Agent Manager session — codex check
One Codex session, exported from Agent Manager.
Access: public. Anyone with the link can read this trace.
At a glance
- 1 prompts · 1 assistant turns · 0 tool calls
- Trace:
rollout-2026-07-28T05-34-19-019fa737-7c2e-7393-89cf-9d9c60ea3899.jsonl
What's in here
| Path | Contents |
|---|---|
rollout-2026-07-28T05-34-19-019fa737-7c2e-7393-89cf-9d9c60ea3899.jsonl |
the session, native Codex JSONL |
meta/manifest.json |
provenance: harness, session ids, stats, content hash, lineage |
meta/briefing.md |
mechanically generated handoff summary |
meta/redaction.json |
which redaction rules ran and what they caught |
Redaction
Before upload the trace passed ruleset v1: token-shaped patterns, value matching against
this Space's secret-bearing environment variables, and an email rule. Derived artifacts go
through the same pass. file-history-snapshot lines are dropped — they embed full file
contents. Result: nothing matched.
Traces can still contain local paths and command output. Review before relying on this being clean.