Relay

Glasses that run your coding agents, remember your day, and answer when you ask.

Relay One is smart glasses for people who already live inside AI agents. Your Claude Code session keeps going after you stand up. Your day gets recorded, transcribed and searchable. Your agent can finally answer "what did I decide about this yesterday?"

This repository is the whole stack: the BLE protocol, the SDK, the host apps, and everything you need to build on it or run it yourself.

relay-vert-nu.vercel.app · Preorder — $249

---

Why this exists

Raw egocentric video is already a commodity — Build AI gave away a million hours of it. Meta Ray-Bans can see and hear. Neither can touch your repo, run your tests, or remember what you promised someone in a hallway.

The gap is not perception. It's continuity: an agent that was present for your day and can act on it.

What's here

glasses/protocol/     BLE protocol codec — all 92 commands, 92 tests, Python
glasses/bridge/       TypeScript transport interface + hardware-free mock
apps/sdk/             @relay/sdk — build apps for Relay One
apps/android/         Always-on capture service (Kotlin)
tools/                Device probe and session capture instruments
docs/                 Architecture, app platform, protocol notes

Start without hardware

The mock is protocol-accurate and encodes real device timing, so you can build and test a full app before your glasses arrive.

git clone https://github.com/luthor007/relay
cd relay/glasses/bridge
npm test          # 66 tests, no hardware required

import { MockTransport, FakeClock } from "@relay/glasses-bridge";

const clock = new FakeClock();
const glasses = new MockTransport({ clock });

const connecting = glasses.connect();
await clock.advance(800);
await connecting;

glasses.on("wear", (worn) => console.log(worn ? "capturing" : "stopped"));

The mock is deliberately inconvenient. A full-size photo really does take ~84 seconds over BLE; fetching an hour of audio really does take an hour unless you open the Wi-Fi access point. A mock that resolves instantly produces a UI that lies about latency and has no error states.

Write an app

Apps run on your own box, not on the developer's server. The author never receives your transcript and never pays to host anything.

import { defineApp } from "@relay/sdk";

export default defineApp({
  async onTrigger(ctx) {
    const meeting = await ctx.memory.recentEpisode({ kind: "meeting" });
    if (!meeting) return ctx.say("No meeting found in the last hour.");

    const summary = await ctx.agent.ask(`Summarise:\n\n${meeting.transcript}`);
    await ctx.memory.write({ kind: "note", title: "Standup", body: summary });
    await ctx.say("Saved.");
  },
});

Declare what it needs in relay.json and it becomes a tool your agent can call:

{
  "id": "dev.you.standup-notes",
  "permissions": [
    { "scope": "memory.read", "reason": "To read the meeting you just left." }
  ],
  "triggers": [{ "type": "phrase", "match": "wrap up the standup" }]
}

Full guide: docs/APP-PLATFORM.md · Working example: apps/sdk/examples/standup-notes

Run it yourself

You never have to pay us. Everything needed to run the agent runtime, the memory pipeline and the app host on your own machine is here and MIT licensed. The hosted tier rents you a box that is already set up and awake when you are not at your desk — that's convenience, not a gate.

Notes from reverse-engineering the hardware

Some of this was expensive to learn and is written down so nobody has to learn it twice:

• The CRC-16 variant is not the one the vendor spec implies. The spec's own appendix reproduces Linux lib/crc16.c, whose caller always passes init 0 — that would be CRC-16/ARC. Disassembling the shipping framework shows mov w8, #0xffff. It's CRC-16/MODBUS. Init 0 makes the glasses reject every frame with no useful error. → glasses/protocol/crc.py

• There is no Wi-Fi station mode. Across all 109 pages of the protocol, the only Wi-Fi commands configure the device's own hotspot. The glasses can never reach the internet on their own, which makes the phone bridge structural rather than optional. → docs/ARCHITECTURE.md §2

• Storage isn't the constraint; transfer is. 4 GB holds 2–23 days of audio, but moving one day over BLE takes 16 hours to a week. Sync has to ride Wi-Fi, which is why it's a nightly ritual and not a background trickle. → docs/APPS-SCOPE.md §3

Privacy, plainly

• The indicator LEDs are lit while recording, and there is no API to disable them. There never will be.
• Transcripts live on your box, encrypted at rest, exportable and deletable.
• Audio is discarded after transcription by default. Keeping a recording of someone's entire life is a liability with no matching benefit.
• Recording law varies. Quebec, California, Illinois and others require every party to consent. Complying where you live is on you.

Status

Pre-launch. Founders Edition units ship in 6–8 weeks.

Protocol codec	working, 92 tests
Transport + mock	working, 66 tests
App SDK	types and manifest validation, 13 tests
Android capture service	written, not yet compiled
iOS host app	not started
App runtime	design only

Nothing above is dressed up as further along than it is. See docs/ for what is verified against hardware and what is still an estimate.

Licence

MIT. Build a competitor with it if you like.

The vendor SDK for the underlying M01 Pro hardware is proprietary to Shenzhen QC.wireless and is not included here. Everything in this repository is our own implementation, written from the published protocol documentation.

---

Built by UU Lab, a trade name of Jappuie Inc., Québec.