Your game session,in context.
CodenameKratos is the Altered Brilliance gaming hub: a Windows desktop companion designed to connect game sessions, local device signals, paired experiences, and the player’s own performance review.
Bring the context of play closer to the player.
CodenameKratos is the PC Module behind the Altered Brilliance gaming hub: a Tauri/React Windows desktop application that brings game library, session, performance, analytics, feed, and notification surfaces into a single local companion. Its architecture includes an active-session tracker, system readings, local-network pairing, and optional HUD surfaces.
The session is more than a scoreboard.
The desktop foundation is organized around useful player surfaces rather than an invisible data pipe.
Track the active game
The native layer can bind a session to an active window, recognize focus changes, and pause the tracker when the session no longer has the intended context.
See the machine as part of play
Live application plumbing can surface action pace alongside CPU, memory, and GPU usage so a session is not interpreted in isolation.
Pair the experience deliberately
The current architecture includes local discovery, a handshake flow, WebSocket updates, companion launch prompts, and HUD/prompt windows.
Sensitive signals need an explicit boundary.
The source application contains telemetry, optional capture, audio, and vision-oriented experiments. That does not make any of those inputs a default entitlement. Before broader release, each capability needs clear activation, visible state, purpose limits, retention rules, support documentation, and privacy/legal review.
NO SILENT CAPTURE
Camera, microphone, screen, and input capabilities must be separately discoverable and consented to before any public release.
A CLEAR SESSION STATE
People need to know when a session is running, paused, connected to another device, or has ended.
USEFUL SETTINGS
Performance, diagnostics, and usage controls belong in a readable settings surface—not buried in a background service.
Desktop foundation
Tauri desktop shell, session UI, local persistence, system integration, and companion-facing views establish the product surface.
Consent and reliability
Permission design, state indicators, secure transport, data handling, error reporting, and release QA need completion before public claims expand.
A real hub experience
Distribution, signing, updater strategy, supported-device definitions, and customer support must exist before the hub becomes a general download.
Make the desktop layer work for the player.
Request desktop-access updates. Public availability will follow a clear privacy, permission, and reliability release boundary.