China's Interim Measures for the Administration of AI Anthropomorphic Interactive Services take effect July 15, 2026 — and rather than retrofit their consumer agent products to comply, ByteDance and Alibaba are just turning them off. We've already covered the regulation itself. What matters now, with two days on the clock, is what happens to the data: your agent configs, your chat histories, and whether there's anywhere to put them.
The regulation, briefly#
The measures were issued in April 2026 by the Cyberspace Administration of China (CAC), jointly with the National Development and Reform Commission, the Ministry of Industry and Information Technology, the Ministry of Public Security, and the State Administration for Market Regulation (AI News). They target services that simulate a person's personality, thinking patterns, and communication style for sustained emotional interaction — companion bots, not workplace copilots.
The operational teeth: providers must nudge users about session length after roughly two continuous hours of use, escalate warnings if they detect signs of overdependence or addiction, and provide an unobstructed, instant way to exit the interaction (AI News). Those requirements sit directly against the design goal of an agent meant to remember you and keep you coming back. Reviewing every user-generated companion agent for compliance, at the scale Doubao and Qwen operate, apparently wasn't a July-15-feasible project — so both platforms are pulling the feature instead of fixing it (Quartz).
Ahead of the deadline, Chinese regulators have been clearing the field: reporting on the run-up describes a pre-deadline sweep of thousands of non-compliant AI agents — impersonation bots, inappropriate role-play, and unauthorized data collection — as platforms and authorities move ahead of enforcement (Bloomberg).
Doubao: a real, dated window#
ByteDance's Doubao is shutting off its agent-creation and agent-run features on July 15. But it isn't deleting on the spot. Users keep read-only access to their agent configurations and chat histories through October 15, 2026 — after that, the data is processed according to ByteDance's privacy policy and becomes unrecoverable inside the app (Tech Times).
ByteDance is also pointing users toward Maoxiang, a separate app, as the place to rebuild agents and resume conversational features (Quartz). There's no bulk export tool and no automatic transfer — read-only viewing is what you get, and recreating an agent in Maoxiang is a manual rebuild, not a migration.
Qwen: no window at all#
Alibaba's Qwen moved faster and gave less notice. Humanlike, user-created agent functions were disabled around July 10; the wider Qwen agent services go dark on July 15, alongside Doubao (BigGo Finance). Unlike ByteDance, Alibaba has not announced a grace period, a read-only window, or any migration destination — agent configs and chat histories are on track for permanent deletion with no stated recovery option (AI News).
If you or your users have anything running on Qwen's consumer agent layer, treat the export window as already closing, not two days out.
The founder takeaway#
If you built a product, a workflow, or a customer-facing bot on top of either platform's C-side agent tools, you are on someone else's clock right now, and the two clocks run differently:
- Doubao: pull everything before October 15. Read-only access is not the same as safety — screenshot, export, or copy configs and chat logs while you still can, then plan the Maoxiang rebuild as a separate project.
- Qwen: assume there is no window left. Check whatever access you still have today.
The transferable lesson isn't really about China. It's about where agent memory lives. Any founder building on a platform-hosted agent — one where the persona, the conversation history, and the "relationship" state live in someone else's database — is exposed to the same failure mode: a policy change, a regulatory deadline, or a product pivot can turn years of accumulated context into read-only data with an expiration date, or into nothing at all. If your product's value is partly the agent's memory of a user, the portability of that state — can you export it, can you re-host it, can you reconstruct it elsewhere — is not a nice-to-have. It's the thing that determines whether a shutdown notice is an inconvenience or an extinction event for what you built.
