Extending MustardOS

MustardOS is built around data and small launch boundaries, so the most common additions need no changes to the frontend at all.

Systems Add systems and launch choices through your own manifests under MUOS/info/manifest.

Folder Aliases Add alternative folder names through a system's friendly list.

Catalogues Add artwork and other catalogue assets under the system's catalogue name.

Themes Add themes as a .muxthm package.

Overrides Set per-content launchers, governors and controls through the assignment flow.

Visual Presets Add Pickles visual presets through the downloadable manifests and creator folders.

External Software Add a dedicated launcher script, with explicit preparation and clean up where needed.

Task Toolkit Add your own maintenance scripts with progress, questions and error reporting on the device screen. Web Dashboard API Read the device status and drive File Management, History, Collections, Remote View and the controls from your own scripts. Editors and Tools Browser tools for core manifests, friendly names and Activity Tracker history. They never upload or keep your files.

Rules for developers

These rules keep your additions compatible with normal frontend and shutdown behaviour:

• Keep identifiers stable.
• Replace persistent files atomically.
• Keep user input out of shell interpolation.
• Restore every device resource a launch changes.