metadata
pretty_name: Agent Manager session — opencode chk
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'
extra_gated_heading: Request access to this agent session
extra_gated_prompt: >-
This repository holds a coding-agent trace. Agent traces can contain source
code, local file paths, command output and other context from the machine that
produced them. Access is granted per user so the owner can see who has read
the session.
Agent Manager session — opencode chk
One opencode session, exported from Agent Manager.
Access: gated. The repo and this card are listed publicly, but the trace itself requires per-user approval.
At a glance
- 1 prompts · 1 assistant turns · 0 tool calls
- Trace:
ses_053816c47ffexP5QoMUR12Xj2q.jsonl
What's in here
| Path | Contents |
|---|---|
ses_053816c47ffexP5QoMUR12Xj2q.jsonl |
the session, native opencode 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.