Open-source project
unknownskl/greenlight avatar
unknownskl/greenlight

Greenlight is a thin wrapper whose own docs stop at the v2 desktop build

Greenlight is an open-source client for xCloud and Xbox home streaming made in Typescript.

2,930 stars185 forksTypeScriptMIT

At a glance

What is it?
UnknownSKL's Greenlight wraps another repository to put xCloud and Xbox home streaming into a desktop window on four platforms, and what the project documents about itself is uneven: three install routes, a key map, a debug overlay, and a build guide that only reaches the v2 workspace while eight workspaces and a v3 script chain sit behind it.
Who is it for?
Greenlight is worth a look if you already stream from a console or xCloud account and want a windowed desktop client with keyboard bindings and an on-screen stats overlay, rather than something to build on.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 6 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • unknownskl/greenlight2,930 ★ · +47
Star history
Repository2026-10-042026-11-15
unknownskl/greenlight2.9k2.9k

47 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Three install routes and a wrapper around a different repository

Greenlight is described as an open-source client for xCloud and Xbox home streaming, written in Javascript and Typescript, and more precisely as an application wrapper around xbox-xcloud-player, which is a separate repository. It runs on Linux, macOS, Windows and Steam Deck. A disclaimer states that Greenlight is not affiliated with Microsoft, Xbox or Moonlight, and that all rights and trademarks are property of their respective owners. Three install routes are offered: Flathub, under the application id io.github.unknownskl.greenlight; pre-compiled binaries from the releases page; and compiling from source, which points back to the Local Development section. One thing is not in the repository at all. The changelog link resolves to https://unknownskl.github.io/greenlight/docs/desktop/changelog, a page under a docs site rather than a file or a release body, so release notes are published as a website and the tags carry no notes of their own.

The documented build reaches only the v2 desktop workspace

The local development path asks for NodeJS and Yarn, then four commands:

bash
git clone https://github.com/unknownskl/greenlight.git
cd greenlight
yarn
yarn desktop dev
yarn desktop build

The last two lines are the ones that matter for scope. In package.json the desktop script expands to yarn workspace greenlight-desktop, so the documented dev and production builds drive the v2 window package and nothing else. The same file also defines desktopv3 as yarn workspace greenlight-desktop-v3. So the repository contains a third-generation desktop package with its own entry point, while the written guide never mentions it. A reader following the steps end to end gets a v2 application and no indication that a v3 one exists in the workspace list.

The v3 chain builds three packages and tests two

The scripts around the desktop entries show how much sits behind them. build:depsv3 is written as yarn logger build and yarn player build and yarn platform build, in that order, so the player depends on the logger and the platform package before it can be built. build:pages runs that chain and then builds pages, and deploy:pages runs yarn pages deploy. test:v3 is narrower still: yarn logger test and yarn platform test, two commands against two packages. The workspace list holds eight entries, packages/logger, player, pages, platform, platform-playground, desktop, desktop-v3 and docs. That leaves six workspaces with no test script wired at all, including the player that the build chain compiles and the two desktop packages the project actually ships. What runs on every change is named in the badge row at the top of the page instead, two workflow files called build_desktop.yml and build_docs.yml, plus four copies of one identical SonarCloud new-code badge pointing at the same project id. So the check surface is a desktop build, a docs build and a code-quality scan, and the unit test script covers two of eight packages. The repository also carries 235 open issues against 2875 stars, and the newest tag, v2.4.2, was published 2026-06-05, a day apart in intent from v2.4.0 and v2.4.1 which landed 2025-12-10 and 2025-12-11, while pushes to the default branch main-v2 continued to 2026-09-21.

A yarn 1 pin sits next to a yarn 2 configuration file

The root holds .DS_Store, .github/, .gitignore, .nvmrc, .vscode/, .yarnrc.yml, LICENSE, README.md, images/, package.json, packages/, tsconfig.base.json and yarn.lock. The tooling baseline is pinned in one place and left loose in two others. package.json declares packageManager as [email protected] with a sha512 hash appended, which is the Yarn classic line, while .yarnrc.yml in the tree is the configuration filename Yarn introduced after 1.x. The setup steps ask for Yarn without naming a version, and ask for NodeJS without naming one, even though .nvmrc sits in the root carrying the intended Node version. The same manifest is marked private, so no package here is arranged for registry publishing, and it also carries the human-facing description of the project as a streaming application for Xbox and xCloud. Translations are handled outside the tree as well, through a Poeditor.com invite link carrying a project id, which fits a root listing with no locale directory in it. A committed .DS_Store and a checked-in .vscode/ directory point at the workstation the project is developed on, and tsconfig.base.json at a TypeScript setup shared by the packages under it.

The feature list qualifies rumble to xCloud and stops there

Five items make up the feature list: stream video and audio from the Xbox One and Xbox Series, support for gamepad controls, rumble support on xCloud, keyboard controls, and a built-in online friends list, which the text spells build-in. Three of those are bare nouns with no detail behind them. The one claim carrying a condition attaches rumble to xCloud specifically, which leaves the console path with no statement about haptics either way, so a buyer comparing the two services has a feature named for one of them and nothing for the other. The online friends list gets its own section described as a way to see which of your friends are online, useful for checking quickly whether anyone is up for a game. That section says nothing about where the list comes from, how often it refreshes, or whether it covers the whole account.

Steam Deck support arrives as a bug report and a key remap

The Steam Deck paragraph is short and hedged: the application is reported to be working on the Deck with some small bugs and side-effects. Neither the bugs nor the side effects are named. The only remedy offered is a mapping, telling the user to map one of the Steam Deck back buttons to the N key to simulate the Xbox button. In the key map, N is bound to Nexus, the Xbox button. So the Deck path depends on the player configuring a remap outside the application, and the application binds none of those buttons itself. Nothing on this page describes a Deck-specific package, a controller profile, or a list of known faults, and the Flathub id io.github.unknownskl.greenlight is the only packaged route named for any of the four supported platforms.

Triggers land on plain characters and no key closes the window

The key map is a plain list. Dpad handles direction controls. A, B, X and Y are taken by the letter keys, with Backspace mapped as B and Enter mapped as A. Nexus, the Xbox button, is N. Left Bumper is the left bracket, Right Bumper the right bracket, Left Trigger a hyphen and Right Trigger an equals sign. View is V and Menu is M. Two consequences follow. Mapping Enter and Backspace to face buttons is harmless while a game holds input and wrong the moment a text field does, and the statistics overlay is bound to the tilde key without appearing in the map at all. More awkward, nothing in the map exits the application. The documented way out is clicking the Xbox logo at the top-left, which asks you to confirm to close the window, so quitting needs a pointer.

The debug overlay is the project's own telemetry, with a caveat attached

Pressing the tilde key brings up a statistics view during a stream, and the project asks for it with issues: when possible, always provide this information if it is related. The layout is described corner by corner. Bottom-left holds the status, described as although not always accurate. Top-right holds the FPS of the video and audio decoders including the latency. Bottom-right holds debug information about the buffer queues and other information that is useful for debugging, which the text spells perposes. So the hedge sits on the number closest to the corner and not on the decoder figures, and the request to attach the output means contributors are the ones generating the diagnostic record. No threshold is given for queue depth, no legend says what a healthy buffer looks like, and no explanation is offered for why the status line is described as unreliable.

Editorial conclusion

Greenlight is worth a look if you already stream from a console or xCloud account and want a windowed desktop client with keyboard bindings and an on-screen stats overlay, rather than something to build on. Before you rely on it, check four things yourself: that the wrapper relationship to xbox-xcloud-player is still what the description claims, since that is where the streaming work lives; what the releases page actually contains after v2.4.2 from 2026-06-05, given that pushes continued to 2026-09-21 without a new tag; whether the desktop-v3 workspace is the direction the project is heading, given the default branch is still main-v2; and the Steam Deck caveats the project calls small bugs without listing them. The disclaimer that it is not affiliated with Microsoft, Xbox or Moonlight is worth reading as written.

Frequently asked questions

How do I install Greenlight on macOS?

Two routes are named: a Flathub install under the application id io.github.unknownskl.greenlight, or a pre-compiled binary from the releases page. The project states it runs on Linux, macOS, Windows and Steam Deck, and compiling from source is a third route that goes through Yarn. No per-platform build matrix is given.

Does Greenlight need my Xbox credentials to stream?

The optional argument --connect=<value> is documented as starting the stream once the user is authenticated, with an F000000000000000 format for console and xcloud_<title> for xCloud. Nothing on this page describes the sign-in flow itself, so how authentication happens is left outside what the project documents.

Why is the default branch main-v2 when a desktop-v3 package exists?

The branch name and the script names follow the same split: the default branch is main-v2, yarn desktop runs the greenlight-desktop workspace, and yarn desktopv3 runs greenlight-desktop-v3. The written steps cover only the v2 pair, yarn desktop dev and yarn desktop build, so the v3 workspace has scripts without a documented run command.

How do I turn on the Greenlight streaming stats overlay?

Press the tilde key. The bottom-left corner shows a status the project calls not always accurate, the top-right shows the FPS of the video and audio decoders including latency, and the bottom-right shows debug information about the buffer queues, which the project asks you to include with an issue when it is related.

Is there a keyboard shortcut to close Greenlight?

The key map has the Dpad, A, B, X, Y, Backspace as B, Enter as A, Nexus as N, the bumpers on bracket keys, the triggers on hyphen and equals, View on V and Menu on M, with no binding for exiting. The documented way out is clicking the Xbox logo at the top-left, which asks you to confirm before closing the window.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. unknownskl/greenlight on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/unknownskl-greenlight.svg)](https://hysenlabs.com/projects/unknownskl-greenlight)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/unknownskl-greenlight.svg)](https://hysenlabs.com/projects/unknownskl-greenlight)

Was this useful?