Skip to content
DCC · DATA COMPLIANCE CHINA China data law, for overseas counsel.
§ TAG · GUI-AGENT

Filed under gui-agent

Every brief tagged "gui-agent".

  • § 01 · AI-AGENTS

    The Agent Authorization Standoff After SAEP: Li Wenlong on Why 155 Apps Refused the Doubao Phone Assistant, and the Case for Reasonable, Non-Discriminatory, Reciprocal Interoperability Rules

    On October 14, 2026 the Doubao phone assistant announced that the 30-day public notice period for its Screen Automation Execution Protocol (SAEP) had ended, and published a list of 155 apps that had refused GUI automation: 66 from Tencent's ecosystem, 23 from Alibaba's, plus Meituan, Kuaishou, Xiaohongshu, banks and AI apps. Li Wenlong (李汶龙, 科技利维坦) asks whether they refused because the protocol is unsound or because of the politics of agent authorization. He walks through SAEP's design: policy declared in AndroidManifest.xml and through a ContentProvider, three scopes (App, Activity, Intent), seven restriction fields and four system decisions (ALLOW, BLOCK, CALL_USER, CLARIFY). He finds it a real access-control scheme whose weak point is that rule-making, interpretation and enforcement sit with one party. He then reads the refusals through the Prisoner's Dilemma, the Stag Hunt and asymmetric games, sorts refusals into three kinds (security and compliance, structural distrust, and security used as a pretext against competitors), argues that anti-monopoly-style mandatory access is unjustified at this stage, and proposes a floor of shared rules built on reasonableness, non-discrimination and functional reciprocity. The essay predates MIIT's Notice 工信厅信管〔2026〕42号, which has since made app developers' declared consent a condition of agent invocation.

    ai-agents · saep · doubao
  • § 02 · AI-AGENTS

    Does China's Phone Agent Now Need Two Consents? 数据何规 Reads MIIT's Agent Terminal Notice as a 'Dual Authorization' Rule

    A full translation. MIIT's Notice on Strengthening the Network Access Management of Agent Terminal Equipment (工信厅信管〔2026〕42号), published November 6, 2026, provides that 'without a declared consent, an agent shall not forcibly invoke or call up the app'. 数据何规 reads this as a dual authorization (双重授权) rule: a phone agent that operates an app for a user needs the user's authorization and the app's consent. The author argues that the rule on distribution and invocation is not confined to pre-installed agents, but that its practical weight falls on system-level GUI agents such as the Doubao phone, not on 'remote control' agents that run tasks in the cloud or on a PC. The piece defends Doubao's 30-day opt-out protocol (SAEP) as a Robots-style boundary declaration, and recalls that the Weibo v. Maimai judgment, (2016)京73民终588号, made platform authorization a separate requirement, while SPC Guiding Case No. 263, (2019)沪73民终263号, held a user-authorized linked-account data transfer not to be unfair competition. The author sets Amazon v. Perplexity beside these as a 'whose tool is it' test, and predicts the rule will be adjusted if platform refusals keep a phone-agent ecosystem from forming.

    ai-agents · dual-authorization · agent-terminal
§ SUBSCRIBE

The Monday brief.

One short email every Monday. New briefs on Chinese data-compliance rules from the previous week, with the source law cited.

Opt-in only. Unsubscribe anytime by replying "unsubscribe" to any issue.

SUPPORT DCC

Keep the publication free to read. Suggested support is $19.99, or choose your own amount.

Support →