There is currently no way to read a report inside VS Code.
The only surface is the tree item's tooltip, built from the id plus the culprit line (extension.ts:83-99) — it does not even include the headline. Everything that makes an st/1 report worth having (the story, the distilled stack, mdc, fields, captured, seen, env) is invisible unless you Copy-for-AI and paste it somewhere else, or open errors-ai.log by hand and scroll.
The JetBrains plugin has had a detail pane since day one — a splitter showing the full report block — so this is also the biggest parity gap between the two.
What to do
Register a stacktale.showReport command backed by a TextDocumentContentProvider on a stacktale: scheme:
- a stable URI per report id, so re-opening reuses the tab;
- read-only, with
language: "log" for basic coloring;
- content is the report's
block, which is already parsed and stored on StReport.
Then make it the item's default click, and move jump-to-culprit to an inline action in view/item/context next to the existing copy action. Opening the report first and jumping second matches how the JetBrains plugin reads: select, read, navigate.
Verify
F5, click a report built from the rich-report golden file in the main repo, and confirm the story, stack and mdc sections are all visible in a read-only tab. npm run compile clean under strict TS, npm test green.
There is currently no way to read a report inside VS Code.
The only surface is the tree item's tooltip, built from the id plus the culprit line (
extension.ts:83-99) — it does not even include the headline. Everything that makes anst/1report worth having (thestory, the distilledstack,mdc,fields,captured,seen,env) is invisible unless you Copy-for-AI and paste it somewhere else, or openerrors-ai.logby hand and scroll.The JetBrains plugin has had a detail pane since day one — a splitter showing the full report block — so this is also the biggest parity gap between the two.
What to do
Register a
stacktale.showReportcommand backed by aTextDocumentContentProvideron astacktale:scheme:language: "log"for basic coloring;block, which is already parsed and stored onStReport.Then make it the item's default click, and move jump-to-culprit to an inline action in
view/item/contextnext to the existing copy action. Opening the report first and jumping second matches how the JetBrains plugin reads: select, read, navigate.Verify
F5, click a report built from the
rich-reportgolden file in the main repo, and confirm the story, stack and mdc sections are all visible in a read-only tab.npm run compileclean under strict TS,npm testgreen.