Doubao and Qianwen Kill Their Agent Builders — Here's How to Rescue Your Workflows
Two major Chinese AI platforms killing their agent builders on the same day is a stark reminder that proprietary AI platforms can deprecate core features without recourse. Developers who built production workflows on these services now face a hard deadline to export their data and rebuild elsewhere, and the same risk applies to any closed agent platform.
ByteDance's Doubao and Alibaba's Qianwen both announced on July 4 that their user-defined agent features will go offline on July 15, with all data permanently deleted after October 15. The shutdown kills any personal assistant built with Prompt + Knowledge Base + Tool combinations on those platforms. One developer's daily report generator, technical translation assistant, and code review helper all broke overnight.
Four replacement paths exist: Coze offers the most similar experience with the lowest migration cost but carries the same platform risk. Dify provides an open-source, self-hosted alternative for teams that want full control. Claude Code with custom Skills integrates directly into a terminal-based developer workflow. A self-built API pipeline offers maximum control at the cost of maintenance overhead.
The simultaneous shutdown exposes a structural risk: any workflow built on a proprietary AI platform can vanish with a single product decision. The immediate priority is exporting System Prompts, knowledge bases, and tool configurations before the October 15 data wipe deadline.
The simultaneous shutdown by two competing platforms suggests a coordinated product strategy shift, not a coincidence, which raises questions about the viability of agent builders as a product category in China's AI market.
Platform risk is not theoretical — it has a hard deadline. The October 15 data wipe means procrastination carries permanent data loss, not just inconvenience.
The migration paths reveal a split: non-technical users get funneled to another proprietary platform (Coze), while developers can escape to self-hosted or terminal-native tools, widening the gap between those who can own their infrastructure and those who cannot.
The discussion centers on helplessness over platform dependency and a practical migration question. One thread sees the shutdowns as an inevitable chokehold, while a separate exchange asks for a better way to handle multi-language translation now that free agents are gone; the author points to self-hosting on Dify as the path forward.
So no matter what you do, you're still getting choked by the neck, huh.
Yeah, no way around it. They've made their move.
For the technical documentation translation assistant, it's exactly the same usage. On my side I also need three-language mutual translation. Without a free agent I'll have to spend tokens. Every time I have to use a glossary as context. Is there a better way?
You can refer to the technical solution in my article and deploy it yourself on Dify.
How's the user count, bro? Can we have a chat? [strength]
Sure thing.