What the Steam beta note changes for Proton
The October 7, 2026 Steam beta, as three outlets quote it, runs non-Steam Windows binaries in Proton by default on Linux. The stable client has no date in those notes.
The short version
Windows binaries registered as non-Steam games now run in Proton by default on Linux, according to the beta notes quoted by Phoronix, TechPowerUp, and BetaNews. Stable has no date.
What happened
On October 7, 2026, Valve posted a Steam client beta that Phoronix, TechPowerUp, and BetaNews all describe the same way. Windows binaries registered as non-Steam games now run in Proton by default on Linux. BetaNews quotes the release note: Windows binaries registered as non-steam games will now run in Proton by default. Before this build, those outlets say, a person had to pick a compatibility tool by hand. The page filing that note, as the outlets quote it, is Futureweb.
What the note covers
The sentence is about Windows binaries added to Steam as non-Steam games, on Linux, in the beta client. It is not a claim about Windows games bought from Steam, which already had a Proton path, and it is not a claim about the stable client. BetaNews says the beta remains opt-in and that no date has been given for the change to reach stable. Phoronix describes the same default and says the beta also fixes a failure to launch after the target binary is changed with the Browse button. The desk is Open source.
What the outlets add beside the default
BetaNews describes a second repair: Steam's Stop button could not close a game that an outside tool had started, and this beta resolves that. It also says the notes do not say whether shortcuts created before the update pick up the new default or only new shortcuts do. This page leaves that gap open. TechPowerUp's report matches the default itself. A question about what a license obligates, for the code under a project, is what a license obligates.
Why it matters on this desk
Proton is the compatibility layer Valve ships for Windows programs on Linux. A default in the client is a software default. Filing it on the hardware desk would confuse a client checkbox with a processor. The check a reader can perform is the sentence the three outlets attribute to the October 7 notes. What a version number has to mean, when a client build carries one, is what a version number has to mean.
What this page does not have
This page's source box cites the three outlets that quoted the notes. It does not cite a separate Valve blog post, because the accounts point at the client beta notes rather than a long company essay. If those notes change, the sentence changes with them. A software desk that files release notes as the document, in a different case, is Software.
What the hand-picked path used to be
BetaNews says that before this build a Windows executable added as a shortcut did not route through Proton automatically. The person set a compatibility tool in the shortcut's properties. The beta's change is that the default is now Proton, so the hand step is no longer required for the case the note describes. The note, as quoted, does not say the person is forbidden to choose a different tool. This page does not add that prohibition.
What to watch next
The stable client's release notes are the next document. A date there would move the default out of the opt-in beta. A note that limits the default to newly added shortcuts would close the gap BetaNews flagged. Another outlet repeating the same quoted sentence does not. The October 7 beta is the change this paper has.
What would change the sentence
A correction in a later beta, or a stable note that words the default differently, replaces the quotation. A Valve post that explains the shortcut-age question would let this page stop saying the notes are silent. Until then the agreement among Phoronix, TechPowerUp, and BetaNews is the default itself, and the silence on old shortcuts is part of the record.
What stays a client default
What stays specific is one sentence in an October 7, 2026 Steam beta: Windows binaries registered as non-Steam games run in Proton by default, on Linux, in an opt-in build. Two related launch and stop fixes are in the same notes, as the outlets describe them. It is not a hardware announcement. It is not a promise about the stable channel. The three outlets agree on the default. They do not invent a stable date, and neither does this page. Phoronix places the build on the night of October 7 and describes it as a better default for Linux users who add Windows programs by hand. TechPowerUp reports the same automatic Proton choice. BetaNews is the account that quotes the note's sentence and that flags the unanswered question about older shortcuts. A reader can treat the default as agreed and the shortcut-age question as open. That split is the whole story. Filing it as a hardware launch would invent a chip the notes do not mention. The wire item sat on a hardware list because the headline said binaries. The dependency is the client. Proton, as the outlets describe it, is the layer the Steam client already uses to run Windows programs on Linux. The news is the default, not a new release of that layer's source tree. No stable-channel date appears in the three accounts. The beta stays opt-in until a later note says otherwise.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
What did the October 7 Steam beta change for non-Steam Windows binaries?
Phoronix, TechPowerUp, and BetaNews report that Windows binaries registered as non-Steam games now run in Proton by default on Linux. The notes are quoted by those outlets.
Does the Steam beta note say the Proton default has reached the stable client?
No. BetaNews says the build is an opt-in beta posted October 7, 2026, and that no date has been given for the stable client.
Which Linux fixes do the outlets attribute to the same Steam beta?
BetaNews describes two: non-Steam games failing to launch after the target binary is changed with the Browse button, and the Stop button failing to close a game started by an outside tool.
Do the notes say whether older non-Steam shortcuts pick up the Proton default?
BetaNews says the notes do not say whether the default covers shortcuts created before the update or only new ones. This page does not guess.
Why is the Proton default filed on the open-source desk?
The change is in the Steam client, and Proton is the compatibility layer the client uses. It is not a new chip, so it is not a hardware brief.