NA
GitHub issue · microsoft/vscode #326098
Not sure, recorded
It arrived
Type: Bug Got this by error VS Code version: Code 1.119.0 (8b640eef5a6c6089c029249d48efa5c99adf7d51, 2026-05-05T11:23:50-07:00) OS version: Windows_NT x64 10.0.26100 Modes: System Info |Item|Value| |---|---| |CPUs|13th Gen Intel(R) Core(TM) i5-1345U (12 x…
Nothing else looked like it
Written reports are grouped when their wording is close enough, first by shared words, then by meaning. It became a problem of its own, and the model read it on its own.
A model labelled it, once
Everything the model returns is below. It does not decide what happens next.
- Kind of problem
- error
- How bad
- medium
- How sure
- In one sentence
User reports an unspecified error in VS Code 1.119.0 on Windows, providing system info but lacking specific error details or reproduction steps.
The rulebook decided
Read top to bottom; the lit rule matched first.
- severity is criticala person looks first
- confidence at or above 0.9acts on it alone
- confidence at or above 0.7drafts it for approval
- severity is higha person looks first
- anything elserecords it as unsure(the rule that decided this case)
When it acts alone, it sends a ticket only for crashes, errors, slowdowns and feature requests. Anything else it is sure about is routine, and dropped.
Rule 5 matched: confidence 0.60 is below 0.7 and nothing forces a human to look.
Not sure, recorded
Too unsure to act and nothing forces a human. Recorded as unsure, on purpose.