Skip to content
@FocusRGB

FocusRGB

Open-source RGB controller that switches lighting profiles with the app or game in focus. Plugin-based, Windows-first. By Devantix.

FocusRGB

Lighting that follows what you're doing. FocusRGB is an open-source desktop RGB controller. It switches lighting profiles automatically depending on the app or game in focus, and it is built around plugins.

🚧 Early development. No release is published yet. Follow the roadmap for progress.

User guides: Visit the FocusRGB Wiki for plugin installation and the SignalRGB setup guide.

Repositories

Repository What it is
FocusRGB The desktop app (.NET 10 and Avalonia), the portable core, the plugin host and the protocol spec
FocusRGB-SDK Official plugin SDKs: .NET (FocusRgb.PluginSdk on nuget.org), with Node and Python planned
FocusRGB-Plugin-SignalRGB Official plugin that lets SignalRGB render FocusRGB profiles
FocusRGB-Plugin-Steam Official discovery plugin that scans installed Steam games and launch executables

How it works

  • Plugins: output, discovery, and integrations run as separate processes communicating over versioned stdio JSON-RPC. Remove a plugin and the app keeps working.
  • Profiles: each profile has one effect and one layout. The app chooses a profile manually, or automatically from an ordered list of application groups. The top matching rule wins.
  • Game frames (planned): game integration plugins read game data in the plugin and emit direct RGB frames; the host accepts those frames only while the bound game profile is active, routing them to output.
  • Local MCP: local Model Context Protocol clients (IDEs and AI assistants) can query state and request profile mutations, with every mutation requiring explicit, single-use user approval in the app.
  • Windows first: the core is portable, so other platforms can follow.
flowchart TD
    subgraph Plugins["Plugins (Separate Processes)"]
        OutputPlugins["Output Plugins<br/>• SignalRGB (today)<br/>• WLED (planned)"]
        DiscoveryPlugins["Discovery Plugins<br/>• Steam (today)<br/>• Epic, GOG, etc. (planned)"]
        GamePlugins["Game Plugins (planned)<br/>• Read game data in plugin<br/>• Emit RGB frames (Slice 20)"]
        CustomPlugins["Your Plugin<br/>(Any language)"]
    end

    subgraph SDK["SDK Layer"]
        DotNetSdk["FocusRgb.PluginSdk<br/>(.NET · nuget.org)"]
        PlannedSdks["Official SDKs (planned)<br/>(Node.js · Python)"]
    end

    subgraph Transport["Transport Layer"]
        Stdio["Versioned stdio JSON-RPC<br/>• Separate process per plugin<br/>• Spec in FocusRGB sdk/spec (spec-vX.Y.Z tags)"]
    end

    subgraph App["FocusRGB Desktop App"]
        PluginHost["Plugin Host<br/>• Install, update, crash restart<br/>• Approval before output resumes"]
        GameCatalog["Game Catalog<br/>(From discovery plugins)"]
        FocusWatcher["Focus Watcher"]
        SettingsProfiles["Settings & Profiles<br/>• Ordered rules (manual override wins)"]
        ActiveProfile["Active Profile & Gate<br/>(Game frames accepted only while<br/>bound game profile is active — planned)"]
        OutputRouter["Output Routing<br/>(One writer per device)"]
    end

    McpClients["Local MCP Clients<br/>(IDE / AI assistants)"]
    Devices["RGB Devices & Hardware"]

    OutputPlugins --> DotNetSdk
    DiscoveryPlugins --> DotNetSdk
    GamePlugins -.->|"Planned"| DotNetSdk
    CustomPlugins -.->|"Planned"| PlannedSdks
    CustomPlugins -.->|"No SDK needed<br/>(direct stdio JSON-RPC)"| Stdio

    DotNetSdk --> Stdio
    PlannedSdks -.->|"Planned"| Stdio

    Stdio <-->|"stdio JSON-RPC"| PluginHost

    PluginHost -->|"Discovered games"| GameCatalog
    PluginHost -.->|"Planned: game frames"| ActiveProfile
    GameCatalog --> SettingsProfiles
    FocusWatcher --> SettingsProfiles
    SettingsProfiles -->|"Selects"| ActiveProfile
    ActiveProfile --> OutputRouter
    McpClients -->|"Every mutation requires<br/>in-app approval"| SettingsProfiles

    OutputRouter -->|"Routes lighting"| OutputPlugins
    OutputPlugins --> Devices
    OutputRouter -.->|"Planned: native output"| Devices
Loading

Contributing

  • Bugs and ideas: open an issue in the main repository.
  • Writing a plugin: plugins communicate with the host over versioned stdio JSON-RPC. The protocol contract is normatively documented in sdk/spec/ and can be implemented in any language. .NET developers can use FocusRgb.PluginSdk on nuget.org; official Node and Python SDKs are planned. Protocol changes start in FocusRGB/sdk/spec/, get tagged (spec-vX.Y.Z), and only then reach SDKs and plugins.
  • Official plugins are repositories in this organization that carry the focusrgb-plugin topic.

FocusRGB is developed and maintained by Devantix. Licensed under MIT.

Popular repositories Loading

  1. FocusRGB FocusRGB Public

    Open-source, plugin-driven RGB profile controller built with .NET 10 and Avalonia. Windows-first with a portable core, automatic app/game profiles, external SignalRGB and WLED plugins, native effec…

    C#

  2. FocusRGB-Plugin-SignalRGB FocusRGB-Plugin-SignalRGB Public

    SignalRGB output plugin for FocusRGB

    C#

  3. .github .github Public

    FocusRGB organization profile and community defaults

  4. FocusRGB-SDK FocusRGB-SDK Public

    Official SDKs (.NET, Node, Python) for writing FocusRGB plugins

    C#

  5. FocusRGB-Plugin-Steam FocusRGB-Plugin-Steam Public

    Steam game discovery plugin for FocusRGB

    C#

Repositories

Showing 5 of 5 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…