[mrmcpowned]

Publishes a warning for the OBS 33.0.0 focus regression.

id	obs-33-background-input
severity	warning — the overlay still works, and there are two ways out
startsAt	2026-10-23T22:20:29Z, the OBS 33.0.0 release
endsAt	empty, ongoing

Facts, and where they came from

• OBS 33.0.0 published 2026-10-23T22:20:29Z; OBS 32.2.2 published 2026-08-14T22:43:31Z. Both confirmed against the GitHub releases API.
• obsproject/obs-studio#14083 is open, titled "Controller inputs not being read in browser source after OBS loses focus", filed against 33.0.0, and reproduces against app.gpv.gg.
• A correction: the first link was given to me labelled "OBS 32.3.3" pointing at the 32.2.2 tag. There is no 32.3.3 release — the API 404s on that tag — and the workaround names 32.2.2, so the label is now "OBS 32.2.2 release" to match where it points.

Two judgement calls worth a look

• The body notes that running as administrator is a Windows notion and says macOS users should go straight to the downgrade. The upstream report is from a macOS user, so "run as administrator" would be dead advice for exactly the person who filed it.
• Link order puts the 32.2.2 release first, because the dashboard banner shows the workaround plus the first link, and the workaround ends on the downgrade.

Checked

• node build.mjs passes; every field is inside its limit (summary 380/500, title 66/120, workaround 73/200)
• Index card and detail page rendered locally in both colour schemes

🤖 Generated with Claude Code