More than 150 apps, including WeChat and Taobao, have opted out of ByteDance’s Doubao phone assistant autonomous operation, Caixin Global reported. The immediate consequence is limited but plain: the reported autonomous operation cannot be assumed to include apps in the opt-out group. Caixin’s report describes a defined app decision. It does not establish an outcome for the apps, the phone, or every other feature associated with Doubao.
Caixin identifies the relevant consumer device as ZTE’s Nubia NaviX Ultra and says it went on sale September 16. It also places the opt-outs in a data-compliance context. Those details locate the event without widening it: the reported choices concern autonomous operation by Doubao on the device Caixin named, and the report names WeChat and Taobao among the apps that opted out.
Pandaily reported that a 30-day notice period for the SAEP screen-automation protocol had ended. Its headline put the opt-out count at 151 apps. The notice-period result gives the reported decisions a specific setting. It also helps separate the reported autonomous operation from a general claim about what any app can or cannot do in every circumstance.
Doubao Autonomous Operation Has a Reported App Boundary
Taken together, the reports describe a boundary around the autonomous operation at issue. An opt-out means the app is outside that reported operation. That is the useful, ordinary-English meaning of the development. It is not necessary to assume that every app has made the same choice, that each app has given the same explanation, or that the reported boundary answers every question about Doubao or the services named in the coverage.
The distinction matters most in the way the event is described. Caixin’s count is about apps that opted out. It is not a count of all apps, nor a settled inventory of every possible app position. Pandaily’s 151-app headline is likewise a report about the SAEP notice-period result. The two accounts support a focused conclusion: an opt-out group exists in relation to the reported autonomous operation, and that group is large enough to be stated as more than 150 apps.
WeChat and Taobao make the report concrete because Caixin named them. Their inclusion gives readers examples from the reported group, rather than hypothetical apps that might be affected. Still, the scope should remain as narrow as the reporting. Caixin identifies the apps as opt-outs from autonomous operation; it does not provide grounds to generalize from those named examples to their broader functionality, their final policies, or the choices of apps not named in its report.
Caixin’s data-compliance framing supplies the reported context for the opt-outs. It should not be stretched into a claimed motive for every individual app. Nor does it resolve how each app might approach automation in the future. The central point is already clear without those additions: Caixin reported more than 150 opt-outs, named WeChat and Taobao among them, and situated the decisions in a data-compliance context.
The device reference also calls for precision. Caixin named the Nubia NaviX Ultra and gave its September 16 sale date, tying the reporting to a specific consumer device. Recent EastFrontier coverage of a reported standalone Doubao personal agent provides wider product context. This report remains centered on autonomous operation and app opt-outs.
Reports Put the Doubao Opt-Out Group Above 150 Apps
The reported tally requires the same care as the reported scope. Pandaily’s headline used 151 apps after the end of the 30-day SAEP notice period. TMTPost reported that a list changed from 151 to 155 apps. Caixin reported more than 150. The common ground across those accounts is an opt-out group above 150, while the exact number was not identical in each report.
That is why more than 150 is the better formulation for the story. It conveys the scale reported by Caixin without turning one changing count into an uncontested final total. The figure of 151 belongs to Pandaily’s headline. The movement from 151 to 155 belongs to TMTPost’s description of a list. Keeping each number beside its source preserves the difference instead of flattening the reporting into a single, overly certain statistic.
A changing count should not be made to carry more meaning than it can bear. It shows that the published accounts did not present one identical figure. It does not show that all apps reached their positions at the same time, did so for the same reason, or will keep those positions indefinitely. The shared fact remains sufficient: the reporting places the group over 150 apps in connection with Doubao autonomous operation.
Nor should the count turn the named examples into a proxy for every service. The reports identify WeChat and Taobao through Caixin, and they identify SAEP through Pandaily. TMTPost adds the reported 151-to-155 change. Each contribution is specific. Read together, they describe reported opt-outs and an unsettled tally, not a universal statement about app behavior or a complete account of future participation.
A Stable Official List Is the Next Test for ByteDance and Apps
The next test is whether ByteDance publishes a stable official list. A list of that kind would provide a clear reference point for the reported autonomous operation and address the uncertainty visible in the different published counts. Until then, the careful account is straightforward: Caixin reported more than 150 app opt-outs, Pandaily reported 151, and TMTPost reported a list that changed from 151 to 155.
The other test is what the apps do next. They may continue refusing automation, permit a narrower form of it, or later permit it. None of those outcomes can be treated as decided by the current reports. The existing coverage establishes the opt-outs that have been reported, not the final form of app participation.
For readers, the present-day consequence stays close to the evidence. A reported autonomous operation cannot be presumed to cover apps that have opted out of it. That is the boundary described by Caixin, Pandaily, and TMTPost. Whether ByteDance releases a stable official list, and whether apps later permit, narrow, or continue refusing automation, is the next documented test.