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
Sometimes a transcript comes back wrong and I want to flag it without losing context. Right now the Pipeline Debug view has separate Copy buttons for the raw transcript, the post-processing prompt, and the cleaned transcript, plus an Export Test Case button that zips everything up.
What I keep wishing for is one button that bundles all of that into a pre-filled bug report (raw transcript, the prompt that ran, the final output, and a free-text "this seems wrong because..." field) and either opens a new issue here or posts to a feedback discussion thread.
TestCaseExporter already collects most of this. The gap is the last mile: I have to save the ZIP, come to GitHub, open a new issue, attach the file, and write a description. By that point I have usually given up.
Concretely, a "Report this transcript" button next to Copy Again that:
Builds the same payload Export Test Case already builds
Skips the audio (privacy and size) but keeps prompt + raw + final + screenshot
Opens a pre-filled new issue or discussion in the browser with the metadata inline as a code block
Would also make it easier to surface patterns — "this prompt produces backwards output for input like X" is hard to describe in prose but obvious from a few real examples.
Worth doing, or am I missing a simpler workflow that already exists?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Sometimes a transcript comes back wrong and I want to flag it without losing context. Right now the Pipeline Debug view has separate Copy buttons for the raw transcript, the post-processing prompt, and the cleaned transcript, plus an Export Test Case button that zips everything up.
What I keep wishing for is one button that bundles all of that into a pre-filled bug report (raw transcript, the prompt that ran, the final output, and a free-text "this seems wrong because..." field) and either opens a new issue here or posts to a feedback discussion thread.
TestCaseExporteralready collects most of this. The gap is the last mile: I have to save the ZIP, come to GitHub, open a new issue, attach the file, and write a description. By that point I have usually given up.Concretely, a "Report this transcript" button next to Copy Again that:
Would also make it easier to surface patterns — "this prompt produces backwards output for input like X" is hard to describe in prose but obvious from a few real examples.
Worth doing, or am I missing a simpler workflow that already exists?
Beta Was this translation helpful? Give feedback.
All reactions