You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: Export a session with its content, in replay formats #1925
agentop export and GET /v1/export (#1830, #1831, core/sessionexport) write a content-free NDJSON record per event, by design
(#1854, R7). Replay tools need the content and a format they already load:
Inference-Perf wire JSONL: one line per call, with the raw request,
the raw response or SSE, status, start time and duration. See
kubernetes-sigs/inference-perf, datagen/replay/wire_trace_converter.py.
OTel GenAI semantic conventions, as Inference-Perf's OTel replay and
our evaluators load them.
The archive already holds every field these need (the raw capture, ttfbMs, durationMs).
Proposal
A content export, separate from today's content-free path, writing wire
JSONL or OTel GenAI per session.
Local only, and redacted by default (feat: Redact recorded content before it leaves the archive #1921). It writes the session id
explicitly, because Inference-Perf reads it from session_id, x-client-request-id or x-litellm-session-id, and not from X-Claude-Code-Session-Id.
@mrsabath: #1854's R13 says content "is refused by an export path rather
than offered as a flag". How should a content export sit next to it: its own
command or route, or a Tier 3 section in the spec? We'd also build on #1906
(session names, tool names, listing the archive).
Proposal (agreed with Hai, 2026-11-17): format and disk
Storage stays the archive's block-dedup segments. Wire JSONL and OTel are
generated only on export, and compressed.
A content export gets its own command and its own route, not a flag on agentop export or a ?content=1 on /v1/export. docs: Spec the session event export #1854 R13 rules out a flag; it doesn't rule out a content export elsewhere. Today's export stays shareable because it never has prompts, and a separate verb keeps that unconditional.
The route refuses non-loopback requests. The session API has no auth and is loopback by design, so a content route reachable through a port-forward would be a different exposure.
docs: Spec the session event export #1854 keeps 7.3 and gains a pointer to this issue. This issue gets its own spec, because wire JSONL and OTel are not the content-free record schema that 7's tiers describe.
Activity
michaljacovi commentedon Nov 17, 2026
Design input from @mrsabath (Slack, 2026-11-17):
agentop exportor a?content=1on/v1/export. docs: Spec the session event export #1854 R13 rules out a flag; it doesn't rule out a content export elsewhere. Today's export stays shareable because it never has prompts, and a separate verb keeps that unconditional.Assisted-By: Claude (Anthropic AI) noreply@anthropic.com