OcuClaw: One Human, a Fleet of Agents · Customer Stories
Hi, it's us, Fly.io. We hate these things as much as anyone, but the<br>marketing gods demand conversion metrics.
We set analytics cookies to measure traffic and ad conversion on our marketing and docs<br>pages. These cookies only cover logged-out visits, never what you do in the dashboard.
Read all about it in our<br>Privacy Policy.
Reject
Accept
Need a Logo?
View Our Brand Assets
Open main menu
Author
Name
Daniel Botha
Image by
Annie Ruygt
Your agent lives on your glasses and your phone stays in your pocket. That is OcuClaw in one line. The glasses are Even Realities’ G2: a small display projected into each lens, the two combining into a single floating screen in front of you, driven by a ring on your finger that swipes, scrolls, and taps. OcuClaw is the app that puts an AI agent on them. An agent, not a chatbot, and the difference is the point. A chatbot can only talk. An agent can use tools, work through a multi-step job on its own, and come back with the result. So you get an answer with your hands full, or capture a thought mid-walk and have it filed somewhere real before you are home, or check how a coding job is going, all without taking your phone out. It began as a client for OpenClaw, an open runtime for that kind of agent, and it now speaks Hermes Agent too. It ships on Even Hub, Even Realities’ app store for the glasses, and it is built by Matthew Ford, an independent developer who was among the twenty selected for the pilot program that opened the platform up.
The interesting part is what it takes to build. An agent that lives on a pair of glasses is not something you can test by running a program and looking at it. The whole stack has to be alive at once, with glasses on the other end of it, before anything you see means anything. That is a lot of computer to point at a single branch, and Ford, working alone, wanted several branches moving at once. So each branch got a computer of its own.
What is the “Fleet Control Center” specifically, and how is it different from just using OcuClaw on its own?
OcuClaw is the product. The Fleet Control Center is the factory. An OcuClaw change isn’t one program to test; it’s a Kotlin app, an OpenClaw plugin, a Hermes Agent plugin, and a relay that all have to be exercised together through a G2 simulator before you can trust it. The Fleet Control Center manages a fleet of “boxes,” each one a complete, isolated copy of that whole stack living in its own Sprite. From one screen, or from my phone, or my glasses, I can wake a box, hand it a task, watch its live glasses render, or park it back to sleep.
Each box is built to serve a pair of smart glasses. Most days that’s the G2 simulator it carries, its render streamed out of the box to my screen; when I want the real thing, my actual glasses connect to the box instead. Same box, same branch, either client.
The site mentions Overview mode, Cockpit mode, and a Phone lane. Can you describe what each one is for, in the words you’d use with a new user?
Overview is the fleet at a glance. Every box is a tile: parked ones sit cold, armed ones show a live thumbnail of whatever their glasses display is rendering right now. It’s the “is anything on fire, is anything done” screen.
Cockpit is climbing inside one box. You get the live glasses render and the app UI side by side, with real input. Your taps and swipes become actual input on that box’s simulator, so you’re driving the stack as if it were running natively on your phone/glasses.
The Phone lane flips the roles. The box’s simulator steps aside and your physical phone becomes the client, connected over a private tunnel. Now you’re testing the real phone-plus-glasses experience against whatever branch that box is running. Real taps on the ring, real voice input, real agent, through the lens.
Who is this actually for? How many people or teams use it today?
One human, plus a fleet of AI agents. That’s not an embarrassing admission, it’s the whole point. I’m a solo developer who works like a team. I dispatch coding tasks to boxes, each box’s agent writes and builds and validates in the simulator on its own, and I review the PRs that come back. And the fleet does more than feature work. Agents on the boxes pull in user-submitted bug reports and come back with proposed fixes that are already e2e-tested in the simulator (ocuclaw.com/triage). Others monitor the OpenClaw and Hermes Agent release logs, check each release against my code, and hand me an “act / check / watch” list per release so I can keep up with the pace of both projects. OcuClaw itself has beta testers on real hardware, but the fleet is my personal factory.
Before this system existed, how did you build and test G2 glasses apps? What did the day-to-day look like?
One laptop, one simulator, one OpenClaw...