Void Desk is a controller-first handheld environment in the wider QWASAR-Env ecosystem. It brings navigation, system tools, connectivity, media, diagnostics and optional desktop sessions into one interface while keeping the host firmware's native boot and recovery paths intact. The Symbiotic Layer is the architectural direction: integrate with the host firmware through supported interfaces while keeping boot, recovery and uninstall paths reversible. Void Desk remains an application-level integration, not a replacement firmware image today. The installed handheld application directory remains Void-Desk/, and the muOS launcher entry point remains mux_launch.sh for compatibility with existing installs.
Important
This repository contains active development, not a v12 release. The latest published handheld package is v10.2.0 (11 August 2026). The v10.5.4-NEXUS development line remains under review; PR #66 is a draft. v12 is a product and architecture blueprint, not an installable package.
Note
Current implementation: Pygame is the reference handheld frontend. LÖVE is experimental and is not feature-equivalent. muOS 2606.0 Andromeda is the current packaging target; compatibility with another firmware/device pair needs its own validation.
| I want to… | Go to |
|---|---|
| Explore the visual documentation portal | QWASAR Field Portal · Interactive Asset Atlas · QWASAR Studio concept |
| Publish or maintain the portal | Field Portal publishing guide |
| Understand the project | Documentation home |
| Quick answers and first steps | Wiki FAQ · What is Void Desk? · First steps |
| Test the desktop version on Linux | PC testing guide · PC bundle notes |
| Install the latest published package | Installation guide · Releases |
| Explore the v12 direction | v12 blueprint |
| Check firmware and controller compatibility | muOS compatibility matrix |
| Understand runtime and source layout | Architecture |
| Develop or contribute | Development guide · Contributing |
| Browse technical source docs | Documentation index · Wiki source archive |
Void Desk is the handheld client. QWASAR-Env is the broader ecosystem of shared contracts and future companion products; these are different layers, not different firmware distributions.
| Layer | Responsibility | Reality today |
|---|---|---|
| Void Desk | NEXUS interface, handheld tools, frontend engines and lifecycle | Current product |
| muOS host adapter | Application runner, device paths, storage, input and clean exit | Current target: 2606.0 Andromeda / validated H700 combinations |
| Local service | Typed bridge for system status, jobs, network and selected host actions | Present; ownership and API coverage are being consolidated |
| QWASAR-Env contracts | UI composition, profiles, capabilities and module metadata | Partially implemented; frontend adoption differs |
| QWASAR Studio / Link | Browser workbench and PC companion | Roadmap concepts; not released services |
QWASAR Studio direction: the intended Studio experience is one web app bringing Module Forge, Layout Designer, Release Composer and Community Library together. This is a roadmap description, not a claim that Studio is already released. APT package recipes target only the optional Debian/Ubuntu desktop image; the muOS handheld package does not run APT or install Debian desktop packages on the host firmware.
The v12 blueprint proposes eight destinations grouped by user intent. RT:WORKSHOP combines the old Workshop and Toolbox responsibilities into two satellites: SYSTEMS and TOOLS. UPLINK owns connectivity, remote access and synchronisation. SETTINGS becomes the control cockpit for appearance, input, device/OS, identity and QWASAR configuration.
The following PNG files in resources/ are menu and hub icons, not screenshots of application screens. They are the visual identity assets used to represent Void Desk destinations.
| WORKSHOP | SETTINGS | THE FORGE | START SESSION | RT:TOOLBOX |
|---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
| NETSPHERE / UPLINK | muOS APPS | MEDIA VAULT | INFO | END |
|---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
These are existing project assets. The NEXUS v12 diagram above is a proposed navigation map, not a screenshot.
🖥️ Actual screen reference — THE FORGE
This is a screenshot of the THE FORGE screen, not an icon:
The separate resources/the_forge.png file shown in the navigation icon grid above is the THE FORGE hub icon.
| Component | Path | Role |
|---|---|---|
| Handheld launcher | mux_launch.sh |
muOS application lifecycle and frontend launch |
| Pygame | desk/ |
Reference handheld UI |
| LÖVE | love/ |
Experimental frontend; parity is incomplete |
| Local service | service/voiddesk_service.py |
Background bridge for selected host capabilities and jobs |
| UI contracts | data/qwasar_ui_manifest.json, schemas/ |
Declarative interface and validation |
| Profile resolver | tools/qwasar_profile_resolver.py |
Validates profiles and writes an effective snapshot |
Warning
Profiles are declarative configuration, not executable plugins. The module-system documents define a contribution/trust contract; they do not mean arbitrary third-party executable modules are safe or fully supported.
A button map can depend on firmware release, handheld model, SDL controller GUID and firmware input behaviour. The v12 design resolves release + device + controller, then maps physical inputs to semantic actions such as CONFIRM, BACK, START and QUICK_PANEL.
| Firmware line | Status reviewed 12 Nov 2026 | Policy |
|---|---|---|
| 2606.0 Andromeda | Current muOS release listed by the project | Main packaging target; validate exact device/GUID profile |
| 2601.0 Jacaranda | Archived | Explicit legacy profile family |
| 2601.1 Funky Jacaranda | Archived variant | Separate metadata until equivalence is proven |
| 2612 Supernova | In development; not a stable release | Preview only; never auto-certify a mapping |
| Other / unknown builds | Varies | Safe generic fallback + manual calibration |
See muOS firmware compatibility. Release discovery is informational: a new release must never silently replace the active input map.
Download the .muxapp release asset from GitHub Releases; do not use the source-code ZIP as an installer.
- Copy the package to
SD1/ARCHIVE/. - On the handheld, open Applications → Archive Manager and install it.
- Launch Void Desk from Applications.
The installed application root remains Void-Desk/ for compatibility. Do not rename it manually.
Prerequisites: Linux, Python 3.10+, a graphical session and terminal. The desktop launcher may create .venv_desktop on first launch.
git clone --recurse-submodules https://github.com/SilverCrow2323/Void-Desk-Project.git
cd Void-Desk-Project
python3 voiddesk.pyUseful options:
python3 voiddesk.py --py
python3 voiddesk.py --love
python3 voiddesk.py --engine py
python3 voiddesk.py --engine love
python3 voiddesk.py --repair
python3 voiddesk.py --help| Guide | What you will find |
|---|---|
| Documentation home | Reading paths and complete topic index |
| v12 blueprint | Product structure, Uplink, Workshop, Settings, services and acceptance gates |
| muOS compatibility | Firmware matrix, device detection and controller mapping |
| Architecture | Launch flow, services, frontends and source ownership |
| Tool catalog | Source-grounded feature inventory |
| Visual identity | Product UI style, palettes and accessibility |
| Documentation style guide | Callouts, diagrams, images and expandable content |
| Development guide | Build, tests, screenshots and hardware validation |
| Visual capture workflow | PNG capture, asset inventory and privacy review |
| Security policy | Security reporting and safe-operation boundaries |
The QWASAR Field Portal in site/ is the intended visual reading experience. The technical source remains version-controlled in docs/ and wiki-source/; the live GitHub Wiki is optional and is not required to use or publish the site.
python -m compileall -q BUILDCHECK.py voiddesk.py bin desk service outdesk voidcast_addons assets
pytest -q
python BUILDCHECK.pyA passing CI run is not physical handheld certification. A release claim must identify the device and firmware tested and cover startup, controller input, the changed feature, failure states, clean exit and return to muOS.
- Keep the native muOS frontend and recovery path available.
- Do not replace the host bootloader or patch protected firmware binaries.
- Keep local host-control services within a trusted local boundary.
- Never place passwords, API keys, pairing tokens or private identifiers in exported profiles or screenshots.
- Treat archives, playlists, profiles and add-ons as untrusted input.
- Make deeper integration reversible, backed up and removable.
The void is not empty. It is infrastructure.










