# FluentHub: a WinUI3 GitHub client for Windows, built with device flow auth > FluentHub is a C# GitHub client for Windows built on WinAppSdk/WinUI3 with tab support and GraphQL mutations. It ships from the Microsoft Store and builds from source against .NET 10, with no local OAuth credentials required. **0x5bfa/FluentHub** — A stylish yet powerful GitHub client for Windows - Repository: https://github.com/0x5bfa/FluentHub - Stars: 1,253 · Forks: 66 - Language: C# - License: MIT - Published: 2026-09-10 · Updated: 2026-09-10 · Language: en - Canonical page: https://hysenlabs.com/projects/0x5bfa-fluenthub ## What FluentHub replaces on a Windows desktop GitHub's web interface works in any browser, but it does not behave like a Windows application. FluentHub targets that gap. The README describes it as "the stylish yet powerful GitHub client for Windows" and says it "follows Microsoft Design Language", which in practice means a FluentUI interface built on WinAppSdk/WinUI3 rather than a web view wrapped in a window shell. The audience is narrow and specific: developers who already live on Windows 11, want native window management, and want to perform everyday GitHub tasks without a browser tab. The README lists the tasks it covers as "creating issues and pull requests with built-in API mutation". That word, mutation, matters. It means the app writes to GitHub through the GraphQL API, not just reads. A read-only viewer would be a different product; this one is positioned as a replacement for the parts of the web UI you touch daily. Two features get their own bullet points. Tab support is built into the app, so multiple repositories or pull requests can stay open at once. Page navigation is described as preserving history and progress, which suggests a back stack that survives moving between pages rather than resetting. Neither claim is quantified in the README, and there is no published benchmark or usage figure, so treat them as design intentions rather than measured behaviour. ## Device Flow authentication and where tokens live The most concrete design decision in the README concerns credentials. It states plainly that "No local OAuth credentials are required." FluentHub uses GitHub Device Flow with its own public client ID, which means a user does not have to register an OAuth application, generate a client secret, or paste one into a config file before the app will work. Device Flow is the OAuth variant designed for input-constrained devices: the client shows a code, the user enters it in a browser, and the client polls until GitHub issues a token. The README does not describe the polling interval or the code lifetime, so those details are not verifiable from the repository description alone. What it does state is the storage location: user access tokens go into Windows Credential Locker. That is the operating system's credential store, not a plaintext file in the app directory, and the README points to a separate document at docs/credentials.md for the full picture. The trade-off is platform lock-in at the authentication layer. Credential Locker is a Windows API. Any port to another operating system would need a different secret store, and the README gives no indication that one exists. For a Windows-only client that is a reasonable choice; it is also the reason the project cannot simply be recompiled elsewhere. ## Building FluentHub from source on Windows 10 or 11 The README documents a source build rather than a package-manager install. The prerequisites are specific: Windows 10 build 10.0.19041.0 or newer with Developer Mode enabled, Visual Studio with the WinUI application development workload, and the .NET 10 SDK. Developer Mode is not optional for unpackaged WinUI deployment, so enabling it in Windows Settings comes before anything else. The first step is cloning the repository: ```bash git clone https://github.com/FluentHub/FluentHub ``` After cloning, the README says no local OAuth credentials are needed, so there is no client secret to configure before the first run. The authentication section states that FluentHub uses GitHub Device Flow with its public client ID and stores tokens in Windows Credential Locker, with details in docs/credentials.md. The build itself is driven by the solution file. Open FluentHub.slnx, set FluentHub as the startup project, and build with the Debug and x64 configuration. If the build succeeds, the app launches and presents a device-flow sign-in rather than a settings screen asking for a token. A failure at this stage usually traces back to a missing WinUI workload or an SDK version mismatch, since the README pins .NET 10 rather than a range. ## Where FluentHub is the wrong tool The clearest limitation is the platform boundary. FluentHub requires Windows 10 build 10.0.19041.0 or newer. A developer on macOS, Linux, or an older Windows build cannot use it at all, and the README describes no fallback. If your team is mixed-platform, a browser or a cross-platform client covers everyone; FluentHub covers only the Windows subset. A second limitation is scope. The README lists issues, pull requests, dashboard, repository and user pages as the covered surfaces. It does not claim to cover repository settings, Actions workflow logs, code review tooling beyond the pull request page, or organization administration. Anyone who spends most of their GitHub time in Actions or in repository configuration will hit the edge of the app quickly and fall back to the browser. A third issue is versioning. The most recent release listed is 0.9.0, published on 2024-08-10, while the repository's last push was on 2026-09-08. That gap means the Microsoft Store build may lag behind what is on main. The README does not document a rollback path, and it does not state which branch the Store package is built from. If you depend on a specific behaviour, build from source rather than assuming the Store version matches. ## FluentHub against the GitHub CLI and the web UI The obvious alternative for command-line-oriented developers is the GitHub CLI, gh. The difference is not cosmetic. gh is a terminal program that composes with shell scripts and pipes; FluentHub is a graphical WinUI3 application with tabs and a navigation stack. If your workflow is already scripted, gh fits inside it and FluentHub does not. If your workflow is clicking through pull requests and reading diffs, the terminal is the wrong shape and FluentHub is aimed at you. The other alternative is the GitHub web UI itself, which needs no install, runs on any operating system, and always matches the server's current feature set. FluentHub's advantage there is native window management and tab support, plus the fact that it is not competing for space with your browser tabs. Its disadvantage is that it must reimplement GitHub's surfaces, and the README's list of covered pages is shorter than what the website offers. A third option worth naming is a cross-platform desktop client, which trades the Fluent/WinUI3 look for the ability to run on more than one operating system. FluentHub's design language is the reason it exists, so that trade is the whole point rather than an accident. ## Licence, maintenance and upgrade cost FluentHub is MIT licensed, and the repository carries an MIT-License topic alongside the LICENSE file at the top level. MIT is permissive: it allows use, modification and redistribution provided the copyright notice and permission notice are preserved. It does not impose copyleft obligations on your own code. This is a general description of the licence text, not legal advice; read the LICENSE file if you plan to redistribute a modified build. Maintenance is harder to judge from the README alone. The repository is not archived, and the last push was on 2026-09-08, which is recent. Releases tell a different story: 0.9.0 on 2024-08-10, 0.8.60 on 2023-08-22, and 0.8.50 on 2023-08-17. The project also carries a crowdin.yml file and a Crowdin badge, and the README asks for translation help, so localisation is an ongoing activity independent of release cadence. Upgrade cost depends on how you install it. Store users get whatever Microsoft ships and have no control over the version. Source builders must keep Visual Studio's WinUI workload and the .NET 10 SDK current, and the README pins those versions rather than describing a range, so an SDK major-version bump is a real migration event rather than a background update. ## Conclusion Install FluentHub from the Microsoft Store if you want a native Windows GitHub client with tabs and issue or pull request mutations, and build from source only if you have Visual Studio with the WinUI workload and the .NET 10 SDK. Do not adopt it if you work outside Windows 10 build 10.0.19041.0 or newer, or if you need a client that runs on macOS or Linux. Before relying on it, check that the Store listing matches the feature set you need, since the most recent release listed is 0.9.0 from 2024-08-10 while the repository has continued to receive pushes. ## FAQ ### Does FluentHub require me to register my own OAuth app? No. The README states that no local OAuth credentials are required, because FluentHub uses GitHub Device Flow with its own public client ID and stores user access tokens in Windows Credential Locker. ### Which Windows versions can run FluentHub? The README lists Windows 10 build 10.0.19041.0 or newer, with Developer Mode enabled in Windows Settings for a source build. ### What do I need installed to build FluentHub from source? Visual Studio with the WinUI application development workload and the .NET 10 SDK. The README then says to open FluentHub.slnx, set FluentHub as the startup project, and build with the Debug and x64 configuration. ### Can FluentHub create issues and pull requests, or is it read-only? It can write. The README describes performing everyday GitHub tasks such as creating issues and pull requests with built-in API mutation. ### Is FluentHub free to use? The repository is MIT licensed, which permits use, modification and redistribution as long as the copyright and permission notices are preserved. The README does not mention any paid tier. ## Sources - [0x5bfa/FluentHub on GitHub](https://github.com/0x5bfa/FluentHub) - [Issues](https://github.com/0x5bfa/FluentHub/issues) - [License: MIT](https://github.com/0x5bfa/FluentHub/blob/main/LICENSE) - [README](https://github.com/0x5bfa/FluentHub/blob/main/README.md) - [Releases](https://github.com/0x5bfa/FluentHub/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/0x5bfa-fluenthub