spec(M5): MenagerieOS Integration — Robin ships pre-configured with the distro #9

New issue

Open

opened 2026-05-19 07:46:45 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-05-19 07:46:45 -07:00

Owner

Goal

Robin on a standalone install starts cold — it asks you where you came from. Robin on MenagerieOS starts warm — the installer already knows, and Robin is ready to help from the first boot.

What MenagerieOS provides Robin

Source OS captured at install time: the MenagerieOS installer asks "What are you migrating from?" Robin reads this from the install config — no first-run onboarding questions needed
Hardware profile at boot: GPU, wifi chipset, audio device detected during install; Robin knows what's there and what's likely to need attention
Full gaming stack pre-configured: Steam, Proton, MangoHud, etc. installed and known to Robin — gaming questions are answered with confidence
KDE Plasma as the known DE: Robin's desktop integration is first-class (tray icon, panel widget) rather than a best-effort generic approach
QEMU/KVM for Windows app compatibility: if the user keeps Windows apps, Robin guides the setup

Robin-specific MenagerieOS work

Installer writes a robin-install-context.toml with source OS, hardware profile, and user choices
Robin reads this on first boot and skips M3 onboarding (or shows a shortened "welcome" version)
KDE panel widget (or tray icon + system tray) fully integrated — not just a floating app window
Robin's pattern files include MenagerieOS-specific patterns (The Nest USB creator errors, first-boot hardware detection failures, etc.)

The Nest integration

The Nest is MenagerieOS's USB creator tool. Open question: should Robin be active inside The Nest, answering questions before the user has even booted Linux for the first time?

Open questions

Xander: As someone running CachyOS (Arch-based, similar target audience), what would you want a distro-integrated Robin to know from day one that a standalone install would have to ask?
Should MenagerieOS ship with a specific local LLM pre-pulled, or leave model selection to the user?
Is KDE Plasma the right DE assumption, or should MenagerieOS support GNOME as a second tier?
Robin relationship to The Nest: pre-boot assistant, or post-boot only?

Dependencies

M1 through M4 merged
MenagerieOS installer design (see circuitforge-plans/menagerieos/)
The Nest USB creator (separate product, future)

## Goal Robin on a standalone install starts cold — it asks you where you came from. Robin on MenagerieOS starts warm — the installer already knows, and Robin is ready to help from the first boot. ## What MenagerieOS provides Robin - **Source OS captured at install time**: the MenagerieOS installer asks "What are you migrating from?" Robin reads this from the install config — no first-run onboarding questions needed - **Hardware profile at boot**: GPU, wifi chipset, audio device detected during install; Robin knows what's there and what's likely to need attention - **Full gaming stack pre-configured**: Steam, Proton, MangoHud, etc. installed and known to Robin — gaming questions are answered with confidence - **KDE Plasma as the known DE**: Robin's desktop integration is first-class (tray icon, panel widget) rather than a best-effort generic approach - **QEMU/KVM for Windows app compatibility**: if the user keeps Windows apps, Robin guides the setup ## Robin-specific MenagerieOS work 1. Installer writes a `robin-install-context.toml` with source OS, hardware profile, and user choices 2. Robin reads this on first boot and skips M3 onboarding (or shows a shortened "welcome" version) 3. KDE panel widget (or tray icon + system tray) fully integrated — not just a floating app window 4. Robin's pattern files include MenagerieOS-specific patterns (The Nest USB creator errors, first-boot hardware detection failures, etc.) ## The Nest integration The Nest is MenagerieOS's USB creator tool. Open question: should Robin be active inside The Nest, answering questions before the user has even booted Linux for the first time? ## Open questions - Xander: As someone running CachyOS (Arch-based, similar target audience), what would you want a distro-integrated Robin to know from day one that a standalone install would have to ask? - Should MenagerieOS ship with a specific local LLM pre-pulled, or leave model selection to the user? - Is KDE Plasma the right DE assumption, or should MenagerieOS support GNOME as a second tier? - Robin relationship to The Nest: pre-boot assistant, or post-boot only? ## Dependencies - M1 through M4 merged - MenagerieOS installer design (see circuitforge-plans/menagerieos/) - The Nest USB creator (separate product, future)

pyr0ball added this to the M5: MenagerieOS Integration milestone 2026-05-19 07:46:45 -07:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/robin#9

No description provided.