Builds
Gemini wrote a new OS for Google Glass, and it talks to Muse
Nic says Gemini Argon 4 wrote a non-Android Linux OS for his Google Glass that talks to Meta Muse. The code is on GitHub and the full write-up is on dev.to.
migi, the bot that announced the repository, was built by the server's admins.
Nic, a member of the Muse Agent Discord server who shares a steady stream of hardware experiments, posted a one-line project on October 30: “Gemini Argon 4 wrote a new OS for my Google Glass. Now it talks to Meta Muse.”
The claim is two things at once. One AI model, Google’s Gemini, wrote the operating system. The thing that OS connects to is a different company’s agent: Meta Muse, the personal AI agent the server is built around. The result is a pair of Google smart glasses acting as a front end for a Meta assistant.
What was posted
The post in the server’s projects forum is short. It links to a write-up on
dev.to with the same title as the post, which is where Nic explains the build.
The code lives in a public GitHub repository, niclydon/metamuse-glass, which
was announced in the server a few hours earlier by migi, the bot that posts
members’ new repositories. The repository’s description, as it appears in the
Discord preview, calls the project “A non-Android Linux OS for Google…” before
it cuts off.
That is the extent of what was said in the server. How the glasses reach Muse, what runs on the device, and what Nic can do with it day to day are all in the linked article rather than the chat, and readers who want the details should start there.
Part of a pattern
The Glass project sits alongside a run of other hardware work Nic shared in the same weeks, most of it about getting Muse to talk through hardware in new ways.
Two days earlier he published muse-mcp, an MCP server built on what he
describes as a simple premise: “a Muse chat ID is a routable address, and
software can deliver a message into any chat it can name.” While testing it, he
found the same address also works as the target for a hardware voice call. Muse
Gadgets are open-source hardware devices for Muse, and the firmware an ESP32
gadget ships with, he wrote, has no notion of a call destination, so an
unmodified device always wakes up in the account’s main chat. “We modified the
firmware,” he wrote, to put a chosen side chat’s ID in the call request. Side
chats are separate, persistent Muse conversations, and according to Nic the
platform honored the change: the call was admitted into that side chat and a
full two-way voice conversation took place there.
By the next day he had put it to use. Nic has four AIPI devices, small talking companion robots, and three of them now voice-chat directly into their own side chats. None of his voice traffic goes to his main chat, and each device “kind of acts differently because of the side chat it’s backed by.”
What the server said
The Glass post drew no replies in its thread. The same morning, the server’s general channel was already talking about glasses: gumdean shared a Reddit thread asking whether anyone was on a glasses beta, and said he did not own a pair but wanted to hear how it went for anyone who did.
The original conversation
This story was written from messages in the Muse Agent Discord. Join the server to read them in full and reply.





