Relay — a shared spatial work queue for two Spectacles users (CLAD Hackathon, Week 3: Connect)

[u/Havalz]

Two people, two places, one shared work queue floating in the space between them.

Relay turns a work queue into something you read at a glance instead of scroll through: height means urgency, distance means how long something's waited, colour means who owns it. No lists, no filters — the space itself carries the meaning.

Pinch a card to claim it. It rises, turns your colour, settles into your lane — and on your partner's screen it dissolves, gone the instant you take it. No duplicate work, ever. Or grab it and pass it directly across the space into their hands, which might be the most literal way to say "Connect" I could think of: something leaving you, arriving with someone else.

A few things worth calling out:

- Real backend, not staged data — a live Supabase database, host-authority networking so only one client ever talks to it, and Gemini batch-triaging the whole queue at once (a single item asked in isolation has no scale and always comes back "priority 3" — batching gives it something to compare against).

- A companion web page — no glasses required. Anyone can drop a task in, set its priority, and watch it land live in both headsets within seconds.

- Six languages, same queue — each person reads it in their own, translated once and cached, never re-translated.

- Fully built through CLAD — Claude Code driving Lens Studio end to end. The prompt log is in the repo, failures included: an early attempt at soft ground lighting that the preview just wouldn't render, cut once the evidence was in, and rebuilt as solid glass geometry instead.

Repo (code + full CLAD prompt log)

Demo video

Companion page

Built for Week 3 of the CLAD Summer Hackathon (Lenslist × SPECS). Happy to talk through any of the architecture — the sync/ownership model in particular was the trickiest part to get right.