From October 20 to 22, along the banks of Shanghai's Huangpu River, the 2026 Sustainable Global Leaders Conference will return once again. Nobel Prize and Turing Award winners will take the stage to discuss the future and trends of technology, and the popular professor who "rescues" people from anxiety and the era of involution, Macfarlane, will hold a live dialogue with Xiang Biao!
Spots are limited and going fast. Let us join together for the appointment with sustainability! [Click to register] 155 apps have refused to connect to the Doubao Mobile Assistant.
On October 14, the Doubao Mobile Assistant announced that the 30-day public notice period for its "Screen Automation Execution Protocol" (SAEP) ended on October 14, 2026, and that it would gradually open screen automation operation permissions for third-party apps. For apps that have explicitly stated their refusal, the agent will not operate on them. After the public notice period ends, developers may still declare refusal at any time, and the Doubao Mobile Assistant will promptly shut down the related operations.
At the same time, the Doubao Mobile Assistant officially disclosed a latest list of apps that have refused operations, involving a total of 155 apps. The mobile phone products covered by the list are the Nubia M153 and Nubia NaviX Ultra.
According to the list, Tencent and related ecosystem apps account for the largest number, totaling 66, including WeChat, QQ, Tencent Meeting, Yuanbao, Honor of Kings, and WorkBuddy. Alibaba and related ecosystem apps number 23, involving Taobao, Alipay, Amap, Hema, and Qwen. In addition, Kuaishou and related ecosystem apps number 14, Meituan and related ecosystem apps number 11, and EZVIZ and related ecosystem apps number 7.
Apart from the above apps, there are also 34 other independent app products, with DeepSeek, Kimi, Pinduoduo, Xiaohongshu, WPS, Mijia, as well as multiple banks and the three major telecom operators all included.
It should be pointed out that the above 155 apps involve many high-frequency usage scenarios in users' daily lives. To some extent, this may affect the smart experience of the two Doubao AI phones, the Nubia M153 and Nubia NaviX Ultra.
It is reported that on September 14, the consumer version of the Doubao Mobile Assistant was officially released, and the new "Doubao phone" Nubia NaviX Ultra equipped with this version was officially launched on September 16. On September 17, when answering netizens' questions, the Doubao Mobile Assistant mentioned that the SAEP protocol was launched on September 14, and a 30-day rule public notice was simultaneously initiated.
According to the SAEP protocol, third-party apps can independently declare their operating boundaries and clearly allow or refuse the AI assistant to carry out screen automation operations within the app. The Doubao Mobile Assistant currently supports system apps, ZTE apps, ByteDance ecosystem apps, and some third-party apps that have already connected, while other apps temporarily cannot perform GUI operations.
During the SAEP public notice period, that is, before October 15, unauthorized apps could not perform automated operations, including on all models such as the M153, and the automated operations of related apps would be gradually opened after the public notice period ended.
Apart from GUI capabilities, the Doubao Mobile Assistant also provides multiple new AI experiences, including Doubao intelligent services, Doubao shopping, recording summaries, and work tasks.
According to the official introduction of the Doubao Mobile Assistant, the launch of SEAP aims to build a transparent mechanism for cross-app operations of graphical interface agents, allowing developers to clearly declare efficient interaction strategies between their apps and the Agent.
The so-called SAEP is a declaration protocol for GUI Agent operations on third-party apps. It converts app protection requirements into machine-parseable policies, has the system complete Agent identity verification and policy decisions before operations, imposes constraints on key capability paths, and records auditable decisions and execution results.
The problems the protocol solves involve four aspects. First, it allows apps to express operable boundaries. Third-party apps can declare which pages and operations are allowed for Agent access, and which pages or capabilities must prohibit GUI Agent proxy operations. Second, it enables unified adjudication of policy management. The policy management module integrates Agent identity, system security baselines, app declaration policies, and user authorization status to obtain the final decision for this operation. Third, it makes constraints difficult to bypass easily. Restrictions are enforced by key system capability entrances, not relying only on Agent self-discipline. Fourth, it makes behavior traceable. It records who requested what operation, on which app page, at what time, which policy was triggered, and the actual result.
Comments