Ronin / Software
One companion. Host-local choices.
Ronin uses one shared companion codebase and firmware protocol across Windows and Linux. Linux is the primary platform, initially Bazzite on the BC250; the Windows laptop is the first physical test host.
What has actually been checked
| Area | Recorded evidence | Limit |
|---|---|---|
| Windows display and USB | Live USB telemetry, native navigation/Home and display scene/audio controls physically checked. | Display Sleep/Wake changes the panel, not the host computer's power state. |
| Reviewed application actions | User-accepted focus checks for the configured Windows targets, plus documented launch cases. | These checks do not establish reliable launch/focus for every installed program. |
| Automatic connection | Windows UART0 unplug/replug to the same laptop socket returned telemetry without manual Connect. | The serial-less bridge uses host-local topology plus a verified firmware handshake; reconnect does not arm actions. |
| Linux | Shared pure-code and loopback checks have passed. | Physical USB, desktop focus, Bazzite, Gaming Mode and real application launch remain unverified. |
Your programs, your page
Windows checks within the recorded scopeDiscovery makes drafts
The companion can discover local installed programs and suggest an editable starter page. Startup discovery and setup suggestions do not install, launch, focus, save configuration or arm targets automatically.
The six-app Windows page is an example profile, not a fixed supported-program list. New targets need host-local review and their own real launch/focus checks.
A standalone display direction
The launcher is intended for whichever supported Windows or Linux host the display is connected to. Normal launcher use must not depend on a BC250, LED/wake board or telemetry service.
Shared profiles retain layout and intent; OS-specific paths, sensors, serial permissions, startup and desktop focus belong in host adapters. General standalone setup and broader host coverage still need testing.
Bitfocus Companion integration
The official engine has a local-only Windows Docker smoke test, and the Ronin Satellite adapter has a counter-only proof through the app's sole USB owner. Guarded source handoff is separate from ordinary reviewed Ronin profiles.
This does not establish general Bitfocus integration, a deployed Linux service or physical Linux control. Elgato software is not a prerequisite for normal Ronin use.
Separate plans from working controls
Not implemented or physically verified- Physical ARGB control of the two Matchstick channels still needs firmware, harness and output verification.
- Gamepad host startup and suspend wake need the standby hardware path and real BC250/BIOS/kernel tests.
- AI/voice sessions, automatic context switching and held shortcuts remain planned.