Repository navigation
Export a thread as a self-contained, redacted bug report #394
Description
From the agent-debugging research: one-click export of a thread (transcript, tool calls, diffs, environment, agent versions) as a single redacted HTML file for sharing with vendor issue trackers or teammates. Secret redaction reuses the privacy gateway (#295). Low effort, high differentiation — reporting an agent bug today means screenshotting a terminal.
Activity
currentbits commentedon Aug 18, 2026
Round 21: OpenCode desktop now exports a full session transcript as JSON from the UI, and the product site advertises share links.
Stay local-first. Do not stand up a Solenta-hosted share URL (that is Origin-adjacent). The steal is: one "Export" on the thread menu that writes JSON + a self-contained HTML you can gist or attach to a GitHub issue. #394 already says redacted bug report — add the JSON/HTML pair as the format, and do not invent a cloud link.
currentbits commentedon Aug 18, 2026
Round 18 intel: Devin Local shipped Share Conversation (changelog 2026-08-10) with a concrete sanitization recipe worth copying for the redacted export: system prompts and tool definitions dropped, secrets redacted, paths normalized, then a team-visible link. The path normalization step is easy to forget and matters for bug reports (home-dir usernames leak). For Solenta's self-contained HTML export: strip provider system prompts/tool schemas (they bloat the file and leak adapter internals), run a secret scan over tool output, rewrite absolute paths to repo-relative.
Redact secrets and personal data from prompts before they reach a clo…