Coding agents in your glasses

Development preview. This page documents our current implementation and firmware layout. It does not establish a completed physical-device test or general public availability.

The code stays on your Mac

There are three parts to the experience. The coding agent runs on your Mac, with the repository and tools available to that session. A bridge on the Mac relays supported session information to the E1O iPhone app. The phone connects to the glasses, where you can inspect the information made available for that session.

1. MacThe agent, repository and commands.
2. PhonePairing, connection and session coordination.
3. GlassesA compact view of session state and supported responses.

Putting the laptop to sleep interrupts the computer side of that chain. The glasses do not take over execution. Keep the Mac awake and online, and keep the phone connected. A connection failure must not be mistaken for an agent finishing its work.

Observation and control depend on the session

The bridge supports several ways of reading session state. A structured agent session can expose explicit events and response controls. A supported terminal session can expose a smaller set of controls. A session whose terminal the bridge cannot address is observe-only, with responses handled on the Mac.

This difference matters when choosing a workflow. Seeing a status update does not prove that you can approve every prompt from the glasses. Before stepping away, check the session’s control mode and try one harmless request from beginning to end.

The private-alpha setup flow

1. Get access to the compatible E1O phone app, glasses and Mac bridge. These components are not offered as a general public download on this page.
2. Start the bridge on the Mac that will run your coding sessions. Its setup checks the local runtime and available coding-agent tools.
3. In the phone app, open Sessions and choose Pair this Mac. Complete the pairing with the short-lived code shown by the app.
4. Open a supported session and inspect its reported mode. Some sessions require hooks or a bridge-managed terminal to make prompts actionable.
5. Ask the agent a harmless question. Confirm that the session update appears on the phone and glasses, then check where a response must be entered.
6. Keep the Mac awake. If the session stops updating, return to the phone or Mac to inspect the connection before acting on old information.

A useful first test

Use a disposable repository and ask the agent to explain a small function without editing it. Confirm the displayed session is the one you selected. Then try a request that requires an explicit response, and verify that the answer reaches that same session. This separates readable status from working interaction.

Check interruptions too: disconnect the phone, let the Mac sleep, and end the session on the computer. The view should make the resulting state clear. Those are validation steps for an alpha test, not a claim that a new physical run has been completed for this page.

What remains to be demonstrated

We still need a published end-to-end recording on physical glasses, including a real session, a response and a connection interruption. We are not publishing latency, battery-life or every-terminal compatibility claims based on the firmware preview.

The architecture and setup sequence above were checked against E1O’s current Mac bridge documentation on September 8, 2026. For the public product explanation, see what runs where. Tell us which agent and terminal you use when requesting early access.