Valve has closed three AI-written Proton bug reports in four days
Valve's Proton maintainer has closed three bug reports in four days with the reporter's use of AI tools raised in each closing comment, and the bluntest of the three leaves nothing to interpret. "Your choice to use AI tools has resulted in an excessively wordy mess" is how it was put on October 18, closing a report about an Enshrouded dedicated server running under Proton.
Enshrouded's dedicated server is the subject of the report Valve closed on October 18, and nothing in the closure concerns the game itself. Image: Keen Games GmbH
They are issues 10282, 10280 and 10263 on Valve's Proton tracker, closed on October 18, 17 and 15. None of them records AI as the reason it was shut: two went as duplicates and the third was sent upstream to Wine first.
In the Enshrouded case Valve says the report would normally have been transferred into the existing one for that title, and the wordiness is why it was not. What Valve asked for instead was a note on the older report in the reporter's own words, with a Proton log from a mainline build.
The second report had a real finding in it
Issue 10280 described how Proton translates OpenXR layers, and Valve closed it as a duplicate while asking how else to read it than "you told your AI tool to create a testcase as an excuse to re-post your issue report". Valve also told the reporter that the original feedback was no less valid for having been filed on the game's compatibility report.
The third is the mildest and the only one where AI is a footnote. That report was redirected to upstream Wine to be reproduced and triaged there first, with a link to Wine's own developer FAQ on code written by a large language model, which is the page the same account cited over an LLM-assisted crash fix on October 3.
A fourth report was closed two minutes after that one with a line pointing at it, and says nothing about AI at all, so the count is three rather than four.
Enshrouded's Steam page gives October 15, 2026 as its release date, three days before the report about its server was shut. Image: Keen Games GmbH
An LLM-written report was fixed in the same week
The counterweight sits on the neighbouring tracker and it is not a small one. The Steam overlay freeze that hangs Linux games on alt-tab is tracked in a report filed on October 3 that states in its own body that "the report has been written by the llm too", in a disclaimer that also says "all the steps were executed entirely by me".
Valve treated it as a report. The maintainer labelled it the day it arrived and renamed it on October 16 to the assertion it fires, later reports were merged into it through the middle of the month, and on October 17 it was closed as completed, writing that the bug the reporter had described was fixed.
What that report carried is the material a triager can act on: a reproducible crash with an assert, a client build number and logs. The three closed ones were a long second copy of a report already filed, a long second copy of a finding already filed, and a Wine bug Valve wanted reproduced upstream first.
Valve's own VR showcase runs on SteamVR, which the second of the three reports says was rejecting every frame affected by the OpenXR fault. Image: Valve
Valve has published no rule about any of it
There is no posted Proton policy on AI-written reports, and nothing here is a rule: it is three comments from one Valve member account on one tracker in four days. The practical reading for anyone whose game has broken is what those three comments ask for, and Valve's own issue template asks for the logs anyway.
One report per unofficially supported title, a Proton log from a mainline build, upstream Wine first where the bug belongs there, and the description in whatever words are yours. A model can help an owner get to that log, and on the evidence of these four days it is the length, not the authorship, that gets a report closed.
