--- title: "Android XR: when the assistant is part of the system" url: "https://kyberbot.com/blog/android-xr-assistant-in-the-system" description: "Android XR builds Gemini into the platform, across headsets, glasses and the phone. What changes when the assistant is a layer of someone else's system, and whose it is." --- # Android XR: when the assistant is part of the system October 13, 2026·4 min read·Editorial team Plain display glasses folded beside a round blue compute puck, a small blue assistant core module lifted out of a slot in the puck on a thin stand You are carrying shopping bags and you say to your glasses: tell the plumber I am running late and move him to Thursday. A few seconds later it is done. Somewhere, on the phone in your pocket, an assistant opened your messages, found the plumber, wrote to him, opened your calendar and moved an appointment. You did not see any of it, and that was the point. On Android XR this is the design. Google’s platform for headsets and glasses puts Gemini in as the assistant layer, and the audio glasses Google showed at I/O in May 2026 work with a phone, Android or iOS, while Gemini carries out multi-step tasks on the phone in the background. The glasses are its voice and camera. On [XREAL Aura](https://www.xreal.com/aura), the first priced Android XR glasses with a display, XREAL describes Gemini as able to open apps, navigate the interface and help in Maps. It works, or is about to. The question this post asks is a different one: whose assistant is that? ## The real cause: an assistant inside the system has the system’s loyalties There are two ways to build an assistant. One is a program that works for you and asks the system for what it needs. The other is a layer of the system itself, present in every app, with the system’s privileges and the system’s owner. Android XR chooses the second. That is not sinister. A layer of the system is faster to build, easier to make reliable and much easier to sell. But it means the assistant answers to the company that makes the platform before it answers to you: its policies, its defaults, its account, its updates. Most of the time those interests line up with yours. The cases where they do not are exactly the ones an assistant should be most careful about. ## What changes when the assistant is the platform’s **It has system privileges by default.** An assistant that can open apps and move through the interface can do anything you can do on that device. The permission screens were designed for apps asking to use the camera, not for an assistant acting in your name. **One account behind every body.** Headset, glasses and phone share one assistant, which is convenient. It also means one account holds what all of them saw and heard, and that account is not on any of your devices. **The defaults are the platform’s.** When you ask for directions, a restaurant or an app, the answer comes from inside an ecosystem that has its own services to offer. You may never notice the choice being made. **Background work you do not watch.** Multi-step tasks on the phone are the useful part. They are also steps nobody is looking at, and Google has not published how much of that work runs on the devices and how much in the cloud. **The deal moves with updates.** What the assistant may do, what it keeps and for how long can change in a release you install overnight. **You cannot swap it out.** Whether a different assistant could ever take that layer is the platform owner’s decision, not yours. ## How KyberBot approaches it KyberBot does not run on Android XR, and Kyber does not integrate with it. It is also pre-launch: Gemini works today, and KyberBot is a design. The design starts from the opposite choice. **It works only for you.** KyberBot is a program you run on devices you hold, not a layer of somebody else’s system. Its memory is on those devices, encrypted, and it carries one identity across every body you own, which is the subject of [one assistant, many bodies](https://kyberbot.com/blog/one-assistant-many-bodies). **Permission to act is written down.** What KyberBot may do in your name is a policy you can read and edit (`kyber policy edit`, illustrative). Seeing a screen is one permission; sending, paying, signing or sharing is another, and those stop and ask you. **Background work happens in a cell, on the record.** When a task has many steps, KyberBot hands it to a KyberAgent swarm, as described in [how an assistant hands work to a swarm](https://kyberbot.com/blog/how-an-assistant-hands-work-to-a-swarm). Each agent runs in a KyberCell and every step is logged; KyberAgent compares that with background tasks on Android XR in [agents on Android XR](https://kyberagent.com/blog/agents-on-android-xr). **Work memory and private memory stay apart.** For a business, the company’s data and the employee’s own life should not end up in one account. KYBERIOS looks at that in [Android XR in a small company](https://kyberios.com/blog/android-xr-in-a-small-company). **The body is a separate question.** Which system runs the glasses themselves is covered on KyberDeck in [Android XR and who owns the body](https://kyberdeck.com/blog/android-xr-and-who-owns-the-body), and what a camera at eye level does to memory and bystanders is in [an assistant that sees what you see](https://kyberbot.com/blog/an-assistant-that-sees-what-you-see). ## A test you can run today Ask the assistant on your phone to do something inside another app: send a message, add an event, change a setting. Then try to find a record of what it did, step by step, without asking the assistant itself. If you can only see the result, you cannot see the work. Second, look for where its history is kept and whether you can export it to a file you hold. If the only copy lives in an account, the memory is the platform’s, and you are visiting it. The assistant we are building is on [the homepage](https://kyberbot.com/). - Android XR - Gemini - personal assistant - permissions - trust ## Keep reading - [What the assistant says aloud and what only to you](https://kyberbot.com/blog/what-the-assistant-says-aloud-and-what-only-to-you) - [One home assistant, several people, separate memories](https://kyberbot.com/blog/one-home-assistant-several-people-separate-memories)