Phone HUD mode
Install Glasses Copilot to your phone for a full-screen HUD-style experience.
On iPhone: open Safari -> Share -> Add to Home Screen.
Phone Bridge and Even G2 are separate targets.
Phone heartbeat proves app-to-phone bridge connectivity only. Real Even G2 HUD rendering requires an Even Hub SDK/runtime display adapter.
To see messages in the glasses, install/run the Even Hub app located at apps/even-g2-insait-hub. Do not mark Glasses Display ready until that app renders on the actual Even G2 HUD.
PWA Bluetooth is only readiness and testing. Even Hub Companion is the SDK bridge path for real glasses rendering.
Live Copilot is ready on Supabase.
Live Copilot is the flagship workflow. InSAiT accepts pasted or live technical questions, detects app context, uses registry knowledge, then delivers short senior-dev cues to Browser HUD, mock ring controls, Phone Bridge, and future glasses paths.
Supabase-backed demo flow can run, but production blockers remain.
This build uses Supabase/Postgres for app state and session persistence. Hardware can still be simulated until real glasses/ring adapters are connected.
Use the app in this order for a Supabase-backed proof run.
Run the supported Supabase-backed proof loop.
Say Hey InSAiT to choose menus, apps, modes, or task prompts.
Tune and test mock gestures before hardware.
Use Google Maps for places, ETAs, and short location cues.
Open the PWA companion display.
Check browser BLE availability without assuming glasses support.
See demo/production readiness and blockers.
Temporary phone controller for glasses workflows
This is the bridge layer until real glasses SDK/BLE integration is added.
Use browser voice or manual transcript while native microphone bridge is pending.
Live Copilot can send short cues to Browser HUD and phone display paths.
Pairing and heartbeat status are surfaced in the existing Phone Bridge runtime.
Capacitor/native wrapper can add background BLE, secure storage, and SDK access.
Even G2 glasses pairing assistant
This scanner only proves phone/browser Bluetooth access, not full glasses integration.
Platform hint: Unknown platform
Your phone may be paired to the glasses already, but Chrome does not let websites automatically use Android's system Bluetooth connection. You must grant this website permission to a Bluetooth device. After that, this site may reconnect to previously allowed devices where the browser supports it.
Looks only for BLE advertisements named like Even G2_32_R_8563F4 or Even G2_32_L_A4DC2D.
Previously allowed for this web app. This is not Android's paired-device list.
No devices have been allowed for this website yet.
No GATT service discovery has run yet.
This may show unrelated/unknown devices. Use only for debugging.
Recommended next step: build the Capacitor Android bridge so the app can use native Bluetooth APIs and, if available, Even's SDK/protocol instead of relying only on browser Web Bluetooth.
What is real now vs prepared for later
What it means: Durable app state, learning, sessions, phone bridge, and GitHub knowledge now use Supabase/Postgres.
Why it is okay now: Browser HUD, mock ring controls, registry knowledge, and Phone Bridge remain usable while real hardware is simulated.
What unlocks it later: Run DB write/read proof and keep migrations applied in the deployed environment.
What it means: The registry is available, but repo-backed file evidence may not exist yet.
Why it is okay now: The copilot can still explain app boundaries from the canonical registry.
What unlocks it later: Connect GitHub, map repos to apps, run safe indexing, and verify retrieval.
What it means: The adapter path is prepared, but no real SDK/hardware bridge is active.
Why it is okay now: Browser HUD and Phone Bridge are the real display targets for this build.
What unlocks it later: Add a real Even G2 SDK/phone bridge integration and validate rendering on hardware.