ByteDance's agent phone goes on sale Sep 16 — and apps get a veto
ByteDance stopped demonstrating its phone agent and started shipping it. The consumer version of Doubao Phone Assistant is now official, the first handset carrying it goes on sale this week, and the part that matters beyond one device is a consent protocol that lets third-party apps refuse the agent outright.
ByteDance released the consumer version of Doubao Phone Assistant, with the first device shipping it — ZTE's Nubia NaviX Ultra — open for pre-order and on sale September 16. The assistant is built on the Doubao app and integrated with phone makers at the system level, and the release moves it from the technical preview shown in December 2025 to something pitched on stability and daily usability. The concrete capabilities: multiple wake methods including voice and a dedicated AI key that carries fingerprint authentication, so once the owner is verified the assistant can act without a second unlock; screen context understanding, so a user pointing the camera at a room can ask Doubao to find matching furniture within a stated size and budget without screenshotting or switching apps; local retrieval across photos, SMS and notes when the user asks — ByteDance's own example is looking up when a travel permit expires; and real task execution, such as confirming a saved address, choosing a vehicle class and placing a ride order. The "operates the phone" GUI capability that drew the most attention in the preview version ships as a Beta.
The interesting sentence is about boundaries. Alongside the release, ByteDance published SAEP — the Screen Automation Execution Protocol — and opened a 30-day public notice period on its rules. Under SAEP, a third-party app declares whether screen automation by the assistant is allowed inside it or refused, and ByteDance says it will not automate inside apps that explicitly opt out. Framed as an invitation to partners to build an "open, regulated" mobile AI ecosystem, it is really the first written settlement of a fight the whole industry has been avoiding: who authorises an agent to act inside someone else's interface? Apple and Google route that through system-level intents and app functions that the developer exposes on their terms; Meta put its consumer agent inside a sealed VM. ByteDance, which owns no mobile operating system licence to hand out, is instead proposing a vendor-authored truce between the assistant and the app economy — while keeping the drafting pen. On privacy it says collection follows "reasonable necessity" and user control, with a tiered, graded agent-protection system governing what the assistant may touch, and a full white paper on the product site.
We flagged the hardware in early September — Huang declares 'AGI has arrived' — and Nvidia's chips are the footnote — and the Nubia pairing first appeared here alongside DeepSeek's hiring push — DeepSeek opens 150 engineering roles — and makes agent fluency mandatory. This is the same consent-layer question Chinese payments rails raised last week — Visa, Mastercard and Ant want one trust layer for AI agents — arriving on the one device nobody can sandbox away.
What to watch: whether SAEP's rules survive the 30-day notice period unchanged, and which major Chinese app refuses first. An agent phone whose most useful skills are blocked by the country's dominant super-apps is a demo again, not a product.
If your bank app could tell your phone's agent "not in my house," is that consent or a wall around the whole category? Tell us in the comments.
