Browser extensions for cloud gaming — Stadia's legacy nobody continued

Stadia ran in Chrome. The browser context meant Chrome extensions could enhance the experience. A thriving small ecosystem emerged: extensions for keyboard remapping, automatic CRC fixes for controllers, enhanced statistics displays, screenshot organizers.

Stadia Enhanced, the most popular extension, added features Google hadn't built. Custom controller mappings, stream stats, automatic clip exports. The extension community was a small but engaged piece of Stadia's user base.

GeForce Now: native Windows client and a Chrome client. No formal extension ecosystem. Some unofficial userscripts exist for the Chrome client but not curated or sanctioned.

Game Pass Cloud: runs in browser (Edge, Chrome, Safari) on most platforms. No extension ecosystem. Some Reddit threads of users sharing userscripts but no formal support.

PS Plus Premium streaming: native client primarily. Web access exists but is limited; no extension story.

Boosteroid, Luna: thin extension stories, mostly userscript hacks.

Custom keyboard-to-controller mapping. Some users want specific key bindings the cloud service doesn't offer.

Enhanced stream statistics. Latency overlay, bandwidth meter, codec info. GeForce Now has some of this; others have less.

Auto-screenshot organizers that tag captures with game names, timestamps, locations.

Cross-service unified launcher. A single extension that surfaces Game Pass Cloud, GeForce Now, PS Plus Premium all in one place. Streamlines multi-service users' workflow.

Discord rich-presence integration. Auto-update Discord status with current game from any cloud service.

Cloud services are wary of letting third parties hook into their clients. The security and UX concerns are real. Allowing extensions could open vectors for cheating accusations or stream-quality complaints attributed to the service.

The user base for power-user features is small. The economics of building extensions is uncertain.

Cross-service unification specifically faces competitive resistance. No cloud service wants to be a 'tile in someone else's launcher'.

The Stadia extension community demonstrated demand. Even a niche audience generated several actively-maintained extensions and clear user adoption.

Cloud gaming services that explicitly allow and curate an extension ecosystem could build community loyalty among power users — the demographic with highest retention and word-of-mouth value.

An open-source 'cloud gaming companion' extension that worked across services would be a useful product even if no service officially sanctioned it. The legal and technical questions are surmountable.

By 2027: an unofficial multi-service browser extension exists and has measurable adoption. Probably created by a sole developer rather than a corporate effort.

By 2028: at least one cloud service either officially allows or quietly accepts the extension. Most likely Game Pass Cloud, because Microsoft's browser-extension culture is more accepting than NVIDIA's.

By 2029-2030: extension ecosystems exist around major cloud services in a way that mirrors the Steam extension and overlay ecosystem.

There's an undeveloped opportunity to build cross-service cloud gaming tools as browser extensions. The infrastructure is in place (cloud services run in browsers, browser extension APIs are mature, the audience exists).

The legal risk is real but manageable. As long as the extension doesn't violate ToS in obvious ways (no bypassing payment, no scraping competitive data), the services are unlikely to actively oppose useful tools.

The first developer to build a polished cross-service cloud gaming companion extension that's actually useful will own a niche that no incumbent is competing for.