OpenGlasses Becomes Avenkin, Adds Locked Field Assist Blur

The third-party iPhone app that lets RAY-BAN META and Oakley Meta owners SWAP in a non-Meta AI has a NEW name. OpenGlasses is NOW Avenkin, and the developer’s own README says it is “the same app: your settings, API keys, conversations and subscription carry over.” The more CONSEQUENTIAL change sits in the PAID tier: according to Mixed News, code MERGED on OCTOBER 4 adds recorded jobs to Field Assist with a FACE BLUR the WEARER CANNOT switch off.

Ray-Ban Meta Gen 2 Wayfarer smart glasses with polarized lenses, showing the camera and capture LED in the frame corners
Ray-Ban Meta Gen 2 Wayfarer. Avenkin uses the glasses’ camera and microphones through Meta’s own integration. Photo: ItzANormalFioko via Wikimedia Commons, CC BY-SA 3.0.

A rename, dated in the project’s own plan

The rename plan in the project’s GitHub repository RECORDS the work as BUILT on September 30, 2026. A follow-up entry dated October 1 says SIRI now “answers to Avenkin only,” after the alternative app name that kept “Ask OpenGlasses” working was WITHDRAWN on the owner’s instruction that “it should all be avenkin.”

One INCONSISTENCY survives. The README STILL tells users that “OpenGlasses” reaches the app through Siri, which CONTRADICTS the October 1 note. Field Assist, the PROFESSIONAL tier, becomes “Field Assist, powered by Avenkin.” The app is published by Skunk0 at Skunkworks NZ Ltd, and the README states it is “Independent of Meta and Anthropic.”

Face blur that overrides the wearer

Mixed News reports that the October 4 merge lets an ORGANISATION REQUIRE BLURRED faces on recorded Field Assist jobs. In that case EVERY recorded segment passes through the app’s ON-PHONE blur before the file is SEALED and sent, REGARDLESS of the wearer’s own face-blur setting. FRAMES the blur cannot process are DROPPED and counted, and the sealed recording carries both the fact of the blur and the number of discarded frames.

The CAVEATS are the developer’s OWN. Per the development notes quoted by Mixed News, the blur “has run only over a small movie made in a test”: NO real recording has been blurred, and its speed on a phone is UNKNOWN. The default build “has no office transport and so offers no recording.” Where recording is enabled, it sits behind a CONSENT prompt, is STORED with the job, and is NEVER written to the photo library.

Visitors at the Ray-Ban and Meta smart glasses booth at the 2025 Bild Expo presented by B&H Photo
The Ray-Ban and Meta booth at the 2025 Bild Expo. Bystander privacy remains the central objection to camera glasses. Photo: Tzim78 via Wikimedia Commons, CC BY 4.0.

Local models, with a stated limit

Outside the paid tier, the README says Avenkin can run compatible LOCAL models through Apple MLX or llama.cpp, import GGUF FILES, and pair them with SenseVoice speech recognition and Kokoro voices for an ON-DEVICE conversation with “no cloud API key required.” Mixed News notes the project’s own WARNING that choosing a local model alone does not make the WHOLE conversation local, and that with glasses the app still RELIES on Meta’s integration, so the CAPTURE LED behaviour is set by Meta, not Avenkin.

Who can actually run it

VERY FEW owners. Avenkin is source-available under BSL 1.1, NOT open source: non-commercial use is permitted, the license CONVERTS to Apache 2.0 on MARCH 24, 2030, and COMMERCIAL use needs a separate licence. The documented install route is a SOURCE build on a Mac with XCODE 26 or newer; the README does NOT assume an App Store download or a public TestFlight. It also says its security engineering is “documented against” SOC 2, ISO 27001, ISO 27701 and ISO 42001. Those are FRAMEWORKS it maps to, NOT CERTIFICATIONS the project says it holds.

Why it matters

Bystander privacy is the ISSUE that keeps FOLLOWING CAMERA glasses, from NORWAY’S proposed restrictions to retailer suspensions in the Benelux. A blur that an EMPLOYER can enforce and the wearer cannot DISABLE is a MEANINGFUL design choice for FIELD and CLINICAL deployments. Until it runs over a REAL recording on a real phone, though, it is an ARCHITECTURE, not a PROVEN safeguard.

Sources: Mixed News; Avenkin README on GitHub; Avenkin rename plan.

Leave a Comment