Skip to main content

WednesdayAI Glass

WednesdayAI Glass is an iOS app for Even Realities G2 glasses. It is a GPLv3 hard fork of MentraOS with faceclaw custom firmware (CFW) support: on stock firmware it uses the stock G2 driver and a text display; on faceclaw CFW (Faceclaw/<n>) it renders the full WednesdayAI HUD (dashboard, launcher, assistant view and glance widgets). WednesdayAI agents are the assistant.

Support snapshot

  • Role: gateway client app (wednesdayai-glass-node), node + operator roles.
  • Gateway required: yes.
  • Install: dev build or internal TestFlight.
  • Transport: the app connects to the gateway over wss:// (for example via Tailscale Serve).

Pairing

  1. On the gateway host, print a setup code:
  2. In WednesdayAI Glass, open Settings → WednesdayAI → Pair with gateway and scan the QR (or paste the setup code).
  3. The first connect redeems the setup code and approves the pairing silently, so there is no wednesdayai devices approve step. The app shows the gateway host once it is connected.
The setup code is single-use and expires. Reconnects do not need it: the gateway mints device tokens at first connect and the app reuses them. If the device was removed or pairing must be redone, generate a fresh setup code.

What the client may do

The setup code stores the wednesdayai-glass-node bootstrap profile: roles node and operator. Pairing approval mints the operator device token with the profile’s scope set — operator.read, operator.write and operator.approvals — and the node token with no scopes. The operator socket connects with those three scopes, and the node socket connects with role node, no scopes and a canvas capability. operator.approvals covers only your own exec approvals. The app receives, and may resolve, an exec approval only when its session belongs to the person the device is linked to in session.identityLinks. It never sees another person’s approvals, approvals without a session or for an unowned session, or any approval while the device is not linked to a person. The app cannot decide or rate learning proposals and lessons. Node commands (invoked by agents and the Control UI, answered on the node socket): These glass.* commands are granted by the device’s attached accessories (plan C3): an attached glasses accessory grants them, plus every glass.tool.* command the node declares (ADR 2242 D4). Attach and detach via device.accessory.* take effect on the live node session without a reconnect. The accessory:g2 connect cap is accepted for one release as a deprecated alias — the gateway auto-attaches a cap:glasses accessory on the verified device and logs the deprecation once per device. A deviceFamily containing glasses still grants them as a separate deprecated alias for one release (ADR 0107 D3). gateway.nodes.denyCommands still wins. Tokens minted by this bootstrap profile never include operator.admin, operator.pairing or operator.talk.secrets. The client id is identity metadata, not an authorization ceiling: an administrator-approved pairing request for the device can still grant it more. An invalid or revoked token on either socket clears both tokens and the app reports unpaired without retrying; re-pair with a fresh setup code.

Glance widgets

Plugins contribute dashboard widgets with api.registerGlanceWidget(...) (see Plugins). The app pulls them with the gateway method glance.widgets.list (scope operator.read):
Each widget is rendered server-side (5 s timeout), normalized to at most 6 lines of 64 chars, and cached for the plugin-declared refreshMs (default 300 s). Response:
A widget whose render throws or times out reports { "lines": [], "error": "unavailable" } for 30 s. A widget whose render returns null is omitted until its next refresh.

Device management

Revoke both roles (operator and node) to cut the device off fully. revoke prevents subsequent reconnects but does not close an existing connection: restart the gateway (or otherwise close its socket) for immediate containment. After remove, the app must scan a new setup code to pair again. See devices and qr.

Troubleshooting

  • Setup-code mismatch (bootstrap_profile_violation): the setup code was issued for a different client id, for example the default wednesdayai qr code instead of wednesdayai qr --client wednesdayai-glass-node. Print a fresh code with the right --client and pair again; the refused token is neither consumed nor device-bound.

Notes and limits

  • Custom firmware flashing is initiated from the app (Settings → Device → Firmware) and voids the glasses warranty; reinstalling stock firmware from the app restores stock behavior.
  • A transcription provider must be configured on the gateway for voice turns.