Key Takeaways
- Meta Connect 2026 ran September 23–24, with Meta announcing Ray-Ban Meta Audio, Ray-Ban Meta Gen 3, Muse updates, and Meta VR Glasses.
- Ray-Ban Meta Audio starts at $349 and ships October 13, while Ray-Ban Meta Gen 3 starts at $449 and is available now.
- Developer Day changed the platform answer: Wearables Device Access Toolkit 1.0 is now a stable release, while broader submissions and discovery remain curated or forthcoming.
Meta Connect 2026 is over, and the two event days answered different questions. The September 23 keynote settled the hardware story with Ray-Ban Meta Audio, Ray-Ban Meta Gen 3, Muse integrations and Meta VR Glasses; the September 24 Developer State of the Union then changed the developer story by moving Meta’s wearable toolkit beyond its year-long preview phase.
The original version of this page asked whether more glasses were enough to make Meta a real computing platform. That question still matters, but it now belongs after the event recap rather than before it. This update first answers what happened, when it happened and what shipped, then returns to the platform test using the final post-Connect evidence. For a minute-by-minute record of the keynote, Tom’s Guide’s Meta Connect 2026 recap.
Meta Connect 2026 at a Glance: Dates, Keynote and Replay
Meta Connect 2026 ran across September 23 and 24 in Menlo Park, California. Mark Zuckerberg’s main keynote took place on September 23 at 4:00 p.m. PT, while the Developer State of the Union followed on September 24 at 10:00 a.m. PT. Meta now keeps the keynotes and developer sessions available on demand through its Connect hub.
| Item | Confirmed detail |
|---|---|
| Event dates | September 23–24, 2026 |
| Day 1 | Meta Connect keynote — September 23, 4:00 p.m. PT |
| Day 2 | Developer State of the Union — September 24, 10:00 a.m. PT |
| Main themes | AI glasses, Muse, Meta VR Glasses, AI models, developer tools and Horizon |
| Replay status | Keynotes and developer sessions are available on demand |
The two-day format matters because the first day answered the consumer questions and the second day resolved several developer questions that were still open after the keynote. Treating Connect as a single hardware launch now misses a large part of what changed.
Everything Meta Announced at Connect 2026
Meta used Connect 2026 to expand both its hardware portfolio and the software layer around it. The clearest way to read the event is as a portfolio expansion: camera-free AI glasses, refreshed camera glasses, lightweight VR hardware, a physical endpoint for Muse, and new developer paths for AI-glasses experiences.
| Announcement | Confirmed details | Availability |
|---|---|---|
| Ray-Ban Meta Audio | Camera-free Ray-Ban AI glasses; 43g; up to 12 hours; Clubmaster and Burbank; starts at $349 | Pre-order open; ships October 13, 2026 |
| Ray-Ban Meta Gen 3 | 12MP camera; 3K video; six microphones; up to 9 hours; Wayfarer, Aviator and Zena; starts at $449 | Available now |
| Meta VR Glasses | About 100g; next-generation Meta VR hardware; v207 SDKs available now; $1,299.99 | Spring 2027 |
| Muse Charm | Pocket/keychain device for talking to Muse through real-time voice; price not announced | Meta says more information is coming later in 2026 |
| Meta Ray-Ban Display updates | Navigation, Hologram calling, Explore discovery, online ordering and additional markets | Feature rollouts vary |
Ray-Ban Meta Gen 3 is a refinement, not the rumored architectural reset
Ray-Ban Meta Gen 3 is the new camera-equipped, screenless Ray-Ban line. The shipping product uses one 12MP camera, records up to 3K video, adds a six-microphone array, a customizable action button and up to nine hours of battery life. The starting price is $449, and the product is already on sale. The detailed Ray-Ban Meta Gen 3 guide separates those confirmed specifications from earlier dual-camera, chipset and codename reports.
The launch is more incremental than much of the pre-Connect rumor cycle implied. Battery life rises by one hour over Gen 2, the microphone system expands from five to six microphones, and the frame family gains Aviator and Zena alongside Wayfarer. Meta and Ray-Ban still do not publicly identify the processor in the shipping Gen 3 materials.
Ray-Ban Meta Audio creates a camera-free branch inside Meta’s lineup
Ray-Ban Meta Audio is Meta’s first camera-free Ray-Ban AI glasses product. The 43-gram frames use open-ear audio, support calls and Muse, offer up to 12 hours of battery life, and come in Clubmaster and Burbank styles with 23 frame-and-lens combinations. Pricing starts at $349, with October 13 shipping.
The product matters beyond the privacy debate because it gives Meta a screenless, camera-free hardware path instead of forcing every buyer into visual capture. TechCrunch’s Connect floor report described the unreleased Audio model as notably light and comfortable during hands-on demos. The pre-event “Luna” reporting is revisited later in this article, where the rumor record can be compared directly with the final retail product.
Meta VR Glasses move VR toward a glasses-shaped system
Meta VR Glasses are not conventional smart glasses. Meta positions the roughly 100-gram device as the next generation of its VR platform, with hand, eye and voice input and a spring 2027 launch at $1,299.99. The v207 SDKs are already available, so developers can begin testing before the hardware ships.
The category distinction matters because “glasses” now covers several very different computing models inside Meta’s own portfolio: ambient AI eyewear, display glasses and a compact immersive VR system. Lumping them together hides the software and interaction differences developers have to manage.
Muse Charm gives the agent a pocket-sized endpoint
Muse Charm was the surprise hardware reveal. The small keychain-style device provides a real-time voice interface to Muse, giving users another way to reach the agent without wearing glasses or opening a phone. Meta has not published a price and has only said that more information will arrive later in 2026.
Meta AI and Muse: What Changed at Connect 2026?
Muse became the connective layer across much of Meta Connect 2026. Meta had introduced the consumer agent earlier in September, but Connect expanded where Muse can operate, which services it can reach, how developers can build around the underlying model family, and which hardware can act as an interface to the agent.
Muse is coming to AI glasses
Meta confirmed that Muse will come to its AI glasses so users can invoke the agent hands-free and assign tasks by voice. Camera-equipped models can also provide visual context for supported tasks. Connect also broadened Muse across computer use, connectors, glasses integration and additional surfaces for the agent.
The practical shift is from short assistant interactions toward longer-running agent workflows such as planning, shopping, scheduling and task management. The distinction between an assistant that answers prompts and software that can carry out multi-step actions is explored in agentic AI glasses explained.
Muse gained more services, surfaces and identity
Meta announced more shopping and productivity partners for Muse, a dedicated Muse email address and additional personalization options. The company is also extending Muse beyond phone and web into Mac, AI glasses and Muse Charm. The strategic idea is one persistent agent that can follow the user across several hardware surfaces rather than living inside a single app.
That cross-device idea is more consequential than the avatar design. A persistent agent becomes useful only when identity, permissions, connectors and task state survive the move from phone to computer to glasses. Connect established the product direction; the quality of those transitions will become clearer as the features reach more users.
Developer Day expanded the Muse model stack
The September 24 developer program added a separate technical layer. Meta highlighted Muse Spark 1.3 for reasoning and agentic workflows, Muse Code as an out-of-beta multi-agent coding system, Muse Image for generation, Muse Voice Transcribe for speech-to-text and Muse Glimmer, an open-weights 30B-parameter model designed to run on a single GPU or Mac Mini.
Meta Model API is now generally available globally, while Muse Spark 1.3 is available through Oracle Cloud AI Platform and in private preview on Google Cloud. These developer products should not be confused with the consumer Muse agent: the agent is the user-facing service, while the Muse model family and APIs are building blocks for software developers.
What Meta Announced for AI Glasses
Connect did more than add two new Ray-Ban products. Meta now operates three distinct consumer glasses surfaces: camera-free audio glasses, camera-equipped screenless glasses and display-equipped glasses. That hardware spread makes compatibility more important because software cannot assume every frame has the same camera, display or input hardware.
| Hardware path | Camera | Display | Primary interaction |
|---|---|---|---|
| Ray-Ban Meta Audio | No | No | Voice, open-ear audio, Muse |
| Ray-Ban Meta Gen 3 | Yes | No | Camera, voice, audio, Muse |
| Meta Ray-Ban Display | Yes | Yes | Display, voice, camera, Neural Band input |
The hardware split is not automatically fragmentation. A platform can support multiple capability tiers if software can detect those capabilities, fall back cleanly and keep identity and permissions consistent. Connect’s developer announcements suggest Meta is trying to make display and displayless glasses related software targets rather than separate product islands.
Meta Ray-Ban Display gained navigation, Hologram and Explore
Meta Ray-Ban Display received new cycling and public-transit navigation, real-time transit information, Hologram video calling, online ordering and expansion into additional markets. The full Meta Ray-Ban Display review covers the existing $799 hardware and day-to-day trade-offs; Connect mainly expanded software, discovery and availability rather than replacing the device.
Explore is strategically important because it gives users a place on the glasses and in the Meta AI app to discover selected experiences. That is different from a fully open app store, but it closes part of the gap between developers building an experience and ordinary users finding one.
Hearing, audio and privacy features broaden the software roadmap
Meta also announced hearing enhancement for supported glasses, Dolby Atmos Capture, new photo and crop controls, audio-balance options, improved responses and Private Processing for selected cloud workloads. Availability varies by device, market and rollout timing, so these are ecosystem-level software announcements rather than Gen 3-only specifications.
Private Processing addresses one privacy layer: off-device handling of personal context. It does not remove the separate governance questions around camera capture, microphone access, bystander awareness and third-party permissions. Those controls become more important as developer access expands.
Developer Day Changed the Platform Story
The largest factual change since the September 23 version of this article happened on Developer Day. Before the September 24 sessions, Meta’s public Wearables materials still described a developer-preview environment with limited distribution. Connect moved one major layer into a stable release and made the route from building to discovery more concrete.
Wearables Device Access Toolkit 1.0 officially launched
Meta says Wearables Device Access Toolkit 1.0 has officially launched after a year in developer preview, with rollout beginning September 30. The toolkit lets an existing iOS or Android app extend onto supported AI glasses while keeping its mobile codebase, backend and store listing. Current capabilities include camera capture, voice input, motion streaming and supported display or input functions.
One integration now covers display and displayless AI glasses. That point matters because Meta’s catalog is becoming less uniform: some frames have no camera, some have no display, and Display adds Neural Band input. A shared integration model reduces the risk that each frame family becomes a completely separate software target.
Meta’s post-Connect AI-glasses developer stack has three build paths: Wearables Device Access Toolkit 1.0 for mobile extensions, Web Apps for Meta Ray-Ban Display, and Meta AI Connectors in developer preview. Discovery is expanding to Meta Ray-Ban Display and the Meta AI app, while general submission timing remains unpublished.
For developers, the old “preview only” description is no longer accurate, but neither is the claim that Meta now operates an unrestricted wearable app marketplace.
Web Apps and Meta AI Connectors broaden the entry points
Web Apps let standard HTML, CSS and JavaScript experiences run on Meta Ray-Ban Display without a separate native SDK. WebMCP remains in developer preview and allows selected functions inside a web app to be exposed to Meta AI. Meta AI Connectors provide another path, letting a service connect through an API or MCP server so Meta AI can call those tools on glasses, web or mobile.
The three paths solve different problems. Device Access Toolkit extends a mobile app onto hardware. Web Apps create display-native experiences. Meta AI Connectors expose a service to the assistant without shipping a glasses-specific app. The broader entry points lower the barrier to experimentation but make capability detection, permissions and review rules more important.
Distribution improved, but submissions are not fully open yet
Meta says two discovery surfaces are coming: selected experiences on Meta Ray-Ban Display and a curated list of compatible experiences in the Meta AI app. The company also says those surfaces will expand as it begins taking submissions and approving more experiences.
The important limitation is timing. Meta is telling developers to create a Wearables developer account so they are ready when submissions open, which means broad self-service submission is not yet a finished public workflow. Connect therefore moved distribution from “build and test” toward curated discovery with submissions coming, but not to a mature open marketplace.
Meta Connect 2026 Rumors vs. What Actually Happened
Pre-event reporting helped identify likely product directions, but several details changed once Meta published final retail hardware and developer documentation. The useful post-event approach is to retain the rumor record only where it explains what did or did not ship.
| Pre-Connect claim | What happened at Connect | Status |
|---|---|---|
| “Luna” would be a camera-free Meta glasses product | Meta launched camera-free Ray-Ban Meta Audio, but did not publicly confirm the Luna codename mapping | Product direction confirmed; codename mapping unconfirmed |
| Gen 3 could use leaked codenames and possibly dual cameras | Retail Gen 3 launched as Wayfarer, Aviator and Zena with one 12MP camera | Retail product confirmed; several leak details did not carry over |
| A small AI pendant or charm was possible | Meta revealed Muse Charm | Confirmed as a product concept; price still unannounced |
| Wearables would remain a developer-preview stack | Device Access Toolkit 1.0 officially launched after a year in preview | Outdated after Developer Day |
| Open distribution would arrive immediately | Curated discovery surfaces are coming; submission timing is still pending | Partially advanced, not fully open |
The most searched rumor was the camera-free “Luna” project. Connect confirmed the product direction but not the codename. The updated Meta Luna and Audio guide keeps that distinction explicit instead of retroactively treating Luna as an official retail name.
What Meta Connect 2026 Actually Changed
The original version of this article used a six-layer platform test: installed base, developer access, application models, distribution, input and output primitives, and governance. That framework still holds. The difference is that both event days are now complete, so several layers can be scored with final evidence instead of future-tense questions.
Meta already had users; Connect strengthened the software path
Installed base was never the hardest remaining problem. EssilorLuxottica’s FY2025 results reported more than 7 million AI-glasses units sold in 2025 across Ray-Ban Meta and Oakley Meta. Connect widened the hardware portfolio further, but the more consequential change was the route for developers to build across that installed base.
The platform is more credible, but not fully open
A successful smart-glasses product is not automatically a computing platform. The platform question becomes meaningful when outside developers can reliably access hardware capabilities, build against stable application models, reach ordinary users, work with predictable input and output primitives, and operate under clear permission and review rules.
| Platform layer | After Meta Connect 2026 | What remains unresolved |
|---|---|---|
| Installed base | Millions of existing AI-glasses owners plus new Audio, Gen 3 and Display options | Exact adoption by device family and developer-relevant active use |
| Developer access | Wearables Device Access Toolkit 1.0 is a stable release; Web Apps and connectors broaden entry points | Capability differences still vary by hardware |
| Application models | Mobile extensions, Display Web Apps and assistant-level connectors now coexist | Developers still need predictable fallback and versioning across tiers |
| Distribution | On-device and Meta AI app discovery surfaces are coming | General submission timing and approval workflow are not fully published |
| Input / output | Voice, camera, display and Neural Band provide multiple interaction primitives | Some advanced or custom input capabilities remain constrained |
| Governance | Private Processing and developer review mechanisms cover parts of the trust stack | Permissions, discovery review and scale will be tested as third-party software expands |
On September 23, the evidence still supported a “strong consumer ecosystem, incomplete developer platform” conclusion. September 24 changed that assessment materially: Toolkit 1.0 is stable, build paths are broader and discovery is now part of the product roadmap. The remaining uncertainty is openness and scale rather than whether Meta has a real developer stack at all.
Muse is becoming a cross-device operating layer
Muse now appears across phone, web, Mac, AI glasses and Charm, while Meta’s broader device roadmap also puts the agent into VR. The strategic bet is not simply to put AI in glasses; it is to keep the same agent reachable as the user moves between devices. That is a larger ecosystem claim and a harder engineering problem than a single glasses feature.
The remaining question is whether third-party services can participate in that agent layer with enough control, permission clarity and reliability to matter at scale. Meta AI Connectors move in that direction, but they remain in developer preview and do not make the entire wearable ecosystem open by themselves.
The useful conclusion is narrower than the old platform thesis
Meta Connect 2026 advanced Meta’s AI-glasses platform in measurable ways: the company launched a stable wearable toolkit, broadened build paths, added discovery surfaces and tied the hardware family more tightly to Muse. The event did not settle every distribution, compatibility or governance question, so describing the ecosystem as either “closed” or “complete” misses the more useful middle ground.
For consumers, the immediate story is simpler: more glasses types, confirmed prices, a new Gen 3, a camera-free Ray-Ban option, larger Muse ambitions and a new VR product for 2027. For developers, September 24 is the more important date because it changed what can actually be built and how those experiences may eventually reach users.
Meta Connect 2026 FAQ
What is Meta Connect 2026?
Meta Connect 2026 was Meta’s two-day annual product and developer event covering AI glasses, Muse, VR, AI models, developer tools and Horizon. The consumer keynote ran on September 23, followed by the Developer State of the Union on September 24.
When was Meta Connect 2026?
Meta Connect 2026 took place September 23–24, 2026. Mark Zuckerberg’s keynote was held September 23 at 4:00 p.m. PT, and the Developer State of the Union followed September 24 at 10:00 a.m. PT.
What was announced at Meta Connect 2026?
The main hardware announcements were Ray-Ban Meta Audio, Ray-Ban Meta Gen 3, Meta VR Glasses and Muse Charm. Meta also announced Muse integrations, new Meta Ray-Ban Display features, Wearables Device Access Toolkit 1.0, Web Apps, Meta AI Connectors and new discovery surfaces for AI-glasses experiences.
What did Meta announce for AI and Muse?
Meta said Muse is coming to AI glasses and expanded the consumer agent with more connectors, surfaces and personalization. Developer Day highlighted Muse Spark 1.3, Muse Code, Muse Image, Muse Voice Transcribe, Muse Glimmer and the globally available Meta Model API.
Did Meta announce Ray-Ban Meta Gen 3?
Yes. Ray-Ban Meta Gen 3 launched September 23, 2026, starting at $449. It uses one 12MP camera, records up to 3K video, has six microphones, offers up to nine hours of battery life and is available now.
What happened to the rumored Meta Luna glasses?
Meta launched Ray-Ban Meta Audio, a camera-free model starting at $349 and shipping October 13. Pre-event reporting used the codename “Luna” for a camera-free project, but Meta has not publicly confirmed that Luna was the internal codename for the final retail product.
Where can you watch the Meta Connect 2026 replay?
Meta’s Connect developer hub offers the Day 1 keynote, Day 2 Developer State of the Union and individual developer sessions on demand.
What did Meta announce on Developer Day?
Developer Day launched Wearables Device Access Toolkit 1.0 after a year in preview, expanded Web Apps and Meta AI Connectors, introduced new discovery surfaces for AI-glasses experiences, and detailed the Muse model and API stack for developers.
Did Meta Connect 2026 turn Meta AI glasses into an open third-party platform?
Not completely. Meta moved beyond a preview-only developer stack with Toolkit 1.0 and upcoming discovery surfaces, but general submission timing and approval details are still incomplete. The platform is materially more open to building than before Connect without yet functioning like an unrestricted app marketplace.
Editorial update: This page was first published before Meta Connect 2026 and was rewritten after both September 23–24 event days. The September 28 preservation rewrite retains the original page’s strongest platform-analysis entities and ranked query coverage while replacing future-tense claims with confirmed post-event facts.
0 comments