Doubao has officially released the consumer version of its mobile assistant, keeping its system-level partnership model with handset makers intact. The first mass-produced device tied to the assistant, Nubia NaviX Ultra, had already been announced and is scheduled for release and sale on Sept. 16. One of the most disputed features, the assistant’s ability to operate a phone on a user’s behalf, has not been removed and remains available in beta. At the same time, Doubao introduced the SAEP screen automation operation declaration protocol, which allows third-party apps to decide whether AI can read the screen, tap controls, and carry out actions inside their apps. If an app explicitly refuses, Doubao will stop automated operations there. BlockBeats also cited a July report by LatePost saying the new generation of Doubao phones will no longer rely on direct GUI-based operation of super apps from Alibaba and Tencent. Instead, Doubao will only be able to access related data and functions if those apps voluntarily open MCP services. In this setup, MCP governs API-style access offered by apps, while SAEP defines the limits for screen reading and simulated taps. Both mechanisms now coexist.
Doubao has officially launched the consumer version of its mobile assistant. The product still works as an AI assistant built through system-level partnerships with smartphone makers, and the first mass-produced device tied to it, the Nubia NaviX Ultra, had previously been announced for release and sale on Sept. 16.
Phone operation feature remains in beta
The phone-operation feature, which had drawn the most controversy earlier, has not been removed. It remains available in beta.
SAEP and MCP now exist side by side
Doubao also introduced the SAEP screen automation operation declaration protocol. Under that framework, third-party apps can set their own rules on whether AI is allowed to read screens, tap elements, and perform actions inside the app. If an app explicitly declines, Doubao will not continue automated operations there.
BlockBeats, citing a July report by LatePost, said the new generation of Doubao phones will no longer directly operate super apps from Alibaba and Tencent through GUI-based interaction. Doubao will only be able to call related data and functions after those apps actively open MCP services.
In this arrangement, MCP refers to interfaces that apps voluntarily open to Doubao. SAEP, by contrast, governs how far developers allow Doubao to go when it relies on screen reading and simulated taps to operate an app. The two mechanisms are now in place at the same time.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
