Doubao and Qianwen Kill Their Agent Builders — Here's How to Rescue Your Workflows

On July 4th, Doubao and Qianwen almost simultaneously announced that their agent features would be taken offline on July 15th. I had previously built three daily automation workflows using Doubao's agents, and my first reaction upon seeing the announcement was "it's over." After calming down, I spent a day researching alternatives. This post organizes my migration thoughts as a reference for others similarly affected.

First, let's clarify: what is being shut down

What's being taken offline is the user-defined agent feature — the kind of "personal assistant" you build within Doubao/Qianwen using a combination of Prompt + Knowledge Base + Tools.

What is NOT being shut down: Doubao and Qianwen's basic chat functions remain, and their model APIs remain. It's just the "agent" product form that is disappearing.

Key timeline:

Date	Action
7/4	Doubao and Qianwen simultaneously issue shutdown notices
7/15	Agent feature officially closes
7/15-10/15	Historical data can be viewed and exported
After 10/15	Data is cleared and unrecoverable

So if you are using agents, you should start exporting data and migrating now. Don't wait until July 14th.

---

The 3 workflows I had affected

Let me talk about the 3 things I built with Doubao's agents. None are complex, but I used them every day:

Workflow 1: Daily Report Generator

Feed the day's Git commits and JIRA statuses to the agent, and it generates a paragraph of daily report text for me. Used once before leaving work each day, saving about 10 minutes.

Workflow 2: Technical Documentation Translation Assistant

Throw English technical documents at it, and it translates according to my set glossary. Better than using a direct translator because it understands context, making technical term translations more accurate.

Workflow 3: Code Review Assistant

Paste a diff in, and it provides review comments based on my configured review rules (naming conventions, error handling, performance issues). It can't replace manual review, but it helps me do a first pass to catch obvious problems.

---

Alternative solution comparison

Spent a day researching several directions, organized into a table:

Solution	Suitable Scenario	Pros	Cons	Cost
Coze	The closest alternative to Doubao agents	Similar interface, low migration cost, ByteDance's own product	Uncertain if it will also be shut down	Free/Paid
Dify	Developers wanting more control	Open-source, self-hostable, powerful workflow orchestration	Requires setting up your own server	Open-source free, cloud version paid
Claude Code + Skills	Developer daily workflows	Use directly in the terminal, seamless integration with code environment	Requires Claude subscription	$20/month
Self-built API calls	Teams with development capability	Fully controllable, no fear of future shutdowns	Requires writing and maintaining your own code	Pay per token

My choice

Original Workflow	Migrated To	Reason
Daily Report Generator	Claude Code + Custom Skill	I'm already working in the terminal, no need to switch
Technical Documentation Translation	Dify self-deployed	The glossary needs persistence, Dify's knowledge base feature handles this
Code Review Assistant	Claude Code /review	Built-in functionality is sufficient

---

Migration operation guide

Step 1: Export your agent data (Do it now!)

Both Doubao and Qianwen provide an export window, but only until 10/15. It is recommended to export now:

Things you need to save:

• The agent's System Prompt (most important, this is the "soul" you spent a long time tuning)
• Knowledge base files
• Valuable content from historical conversations
• Tool configurations and API connection methods

Step 2: Choose an alternative platform

Choose based on your technical ability:

Your Situation	Recommendation
Don't want to tinker, want the most similar experience	Coze
Have a server, want full control	Dify self-deployed
Mainly used to assist programming	Claude Code + Skills
Only use occasionally, don't want to spend money	Basic chat functions of each platform are sufficient

Step 3: Rebuild the workflow

Adapt the exported System Prompt to the new platform. In most cases, no major changes are needed — the core Prompt is universal and can be used on another platform just as well.

---

A deeper question

Doubao and Qianwen shutting down their agents simultaneously serves as a wake-up call for everyone using AI platforms:

Workflows you build on someone else's platform can disappear at any time due to the platform's decisions.

So my principles now are:

1. Keep a local copy of core Prompts and configurations. No matter what platform you use, store configuration files on your own computer.
2. Use open-source solutions whenever possible. With Dify, Claude Code Skills, at least the code and configuration are in your hands.
3. Don't put all your eggs in one basket. Have at least a Plan B for critical workflows.

---

Finally

In 10 days (7/15), the agents will be shut down. If you are still using Doubao or Qianwen agents, the most important things to do now are just two:

1. Export your Prompts and knowledge bases
2. Choose an alternative and start migrating

Don't wait until the last day to find out your data is gone.

Are you using Doubao or Qianwen agents? Where do you plan to migrate? Let us know in the comments, and see what good alternatives everyone else has.