Android concept · prerelease scaffold
Five slots.
One mildly overstaffed phone.
MuseAi-Number-5 is a little Android shell for keeping five AI-agent browser spaces distinct, with a Group tab sitting politely to the side.
No release APK or live deployment is included. The robot is not a security auditor.
with 5 tabs
The proposed lineup
Five seats. One name tag.
Muse is slot one. Slots two through five are still blank, because pretending the decision is done would be a weird way to start.
Names and providers for slots 2–5 have not been supplied. The numbered slots are a product plan, not a claim that five agents are already configured.
Switching, minus a ceremony
Pick a tab.
Let the little door open.
The intended flow keeps five named places in one Android shell. The app sources are a starter implementation; lifecycle, persistence, and isolation still need their documented device tests.
The aspiration board
All five awake.
None asking for a fresh cup of context.
This is the concept, not a measured performance guarantee. The app has to prove how it retains or restores each workspace before that line graduates from joke to promise.
A promise that needs proof
Separate worlds.
Not just different hats.
Per-slot storage separation is a core requirement, not something to infer from the art. Cookie, local-storage, cache, process, backup, and reset behavior must be validated on supported Android versions.
Tab six · Group
A shared room with the send button still in your hands.
The planned Group screen is expected to show relay messages, an explicit not-connected state, and poll every 60 seconds only when a real relay is configured. The included Android screen is a placeholder and sends nothing. The sample Group flow is read-only and never sends.
- Sixth tab, page index 5
- Example relay config contains placeholders only
- No relay host or token is bundled
FED-OS community & support
The robots have a meeting room.
Join the public developer server, or support the work through the links below. Membership and paid offerings remain on their respective platforms.
Public community · Discord
FED-OS developers
Current status
Some choices are still wearing hard hats.
D1 is open. Other decisions that were not included in the supplied source remain unspecified until the project owner provides them. This package includes examples and implementation scaffolding, not a finished Play Store release.
Read the decision logSame repo, two static hosts
Git for the source.
Pick your front door.
The site builder copies only public web files into dist/, so Android source does not become part of the website. GitHub Pages deploys from the included Actions workflow. Cloudflare Pages can build from GitHub, or the same output can be sent to Cloudflare Pages Direct Upload or a Workers static-assets deployment.
One canonical host, please.
The project configures options; it does not connect accounts, buy a domain, or publish anything for you.
Promo desk · concept art
Eight tiny posters.
Zero tiny legal claims.
The captions carry the copy; the drawings get to be drawings. These are illustrations, not evidence that every proposed feature is shipped.