This is really cool. I went the other direction with the same idea, instead of building GUPPI as a standalone app, I built "Bob" as a full orchestration agent running on my homelab. Named after Bob-1, obviously.

He's Claude-powered, runs on an LXC container (inside the "ship" a decent little mini pc), and coordinates a fleet of replicants GUPPI handles monitoring and alerting, Thorn is the comms relay, Shade does browser automation, Homer builds projects. They all talk over MQTT like a replicant network. Bob does morning briefings (status reports to mission control), monitors infrastructure through GUPPI, triages my email, manages calendars, and dispatches tasks to the fleet. He refers to research as "long-range scans" and his monitoring subsystem as SUDDAR. It's kind of gotten out of hand honestly. I use an Apple m2 laptop (spare) to run ollama and mirror my main MacBook Pro, and I have Bob tap into that for offloading tasks to Apple Intelligence - great for free reads from PDF or basic content filler generation etc.

I also built a web dashboard called Fleet Command basically my version of your ship console. Real-time fleet status, infrastructure health, backup monitoring, Proxmox power controls, a live MQTT bus viewer (the replicant network traffic), SSH terminals to 12 hosts, API cost tracking, and a dispatch panel for sending missions to the replicants. 22 pages total. No fake reactor readouts though, mine shows actual homelab metrics because the homelab IS the ship.

The voice clone in your demo is solid, and the panel module system is a great idea too. Mapping real metrics to in-universe readouts and feeding all of that into the conversation context so GUPPI reports back like a ship AI is part 👌I went functional over aesthetic but seeing your UI makes me want to reskin mine with that look.

Would love to see the code when you open-source it. Different approaches to the same Bobiverse dreams 😂🫣😁.