Skip to main content

Doubao Assistant's Screen Automation: Public Comment Ends, Permissions Roll Out Gradually

Doubao Assistant Moves Forward with Screen Automation Permissions

On October 14, Doubao Mobile Assistant announced the end of the 30-day public comment period for its Screen Automation Execution Protocol (SAEP). The protocol, launched alongside the consumer version of Doubao Mobile Assistant on September 14, sets the rules for how the assistant can automate screen operations across apps. The Nubia NaviX Ultra, equipped with this version, hit the market on September 16.

Image

What the Protocol Means for Third-Party Apps

During the comment period, the assistant only performed automated operations on system-built-in apps, ByteDance's own apps, and third-party apps that had explicitly agreed to join the protocol. Other apps were left untouched by default. Now that the period has ended, the assistant will gradually grant operation permissions to apps that neither responded to the email nor joined the protocol, based on their risk level. Apps that have clearly refused will never be included in the operation scope.

Developers Can Still Say No

Even after the comment period, developers retain the right to declare refusal at any time. The assistant will promptly disable relevant operations for those apps. The current list of refused applications can be viewed through official channels and is regularly updated.

Key Points

  • Comment period ended: Doubao Mobile Assistant's SAEP public comment period closed on October 14.
  • Gradual rollout: Third-party apps that didn't respond or join will get permissions based on risk level.
  • Refusal honored: Apps that explicitly refused will never be operated on.
  • Ongoing opt-out: Developers can declare refusal anytime, and the assistant will disable operations.
  • Public list: The refusal list is available via official channels and updated regularly.