The short answer
The retired feature is the Quest window inside Qoder IDE. The Editor continues. Choose the separate Qoder app if your workflow depends on task execution or mobile remote control, then check imported history and account benefits before relying on it. This guide explains the official notice; it is not a hands-on migration test.
First identify the affected workflow
Qoder’s notice sets October 15, 2026 at 23:59 UTC+8 as the retirement time for the IDE Quest window. It says the Editor window, including AI chat, Agent and Expert features, continues. Mobile devices connected through the old Quest window lose that remote-control connection.
Our advice: identify the client and window you actually use before changing tools. A feature retirement is a reason to examine that workflow, rather than evidence that every client or the whole product has ended. If Editor features cover your work, keeping that workflow may avoid an unnecessary migration.
Use the existing account and import path
The official path is to install the separate Qoder app on your usual computer and sign in with your existing account. Qoder says subscription benefits and credit balance sync without a new purchase. Import during onboarding or from Settings → Personal → Data Import.
For mobile control, the notice directs users to enable Settings → Mobile in the new app. For old Quest conversation history on mobile, it says to import first, then switch Mobile off and back on. Follow the linked notice if the current interface differs.
Verify a small migration before switching your routine
The following is our suggested acceptance check, not a claim that we performed it: record your current client version, account and remaining credits. Preserve a copy of the local material you need using the product’s supported export or backup path before changing clients.
After import, inspect one conversation you recognize and open one representative workspace. Confirm that the expected context is present and the account shows the benefits you expected. If you use a team account, ask its administrator to verify the relevant workspace permissions.
Try one bounded, non-confidential task. Inspect the resulting diff and run your own checks; record the credits consumed. Reconnect one mobile device and verify the specific remote workflow you need. Keep that evidence separate from impressions about the new interface.
If history, benefits or a connection are missing
Stop the affected workflow and note which acceptance check failed. Useful support context includes the client version, import stage and expected versus observed result. Remove private source code and account secrets from any screenshots or logs before sharing them.
Use the support destination linked in the official notice for account-specific recovery. This article cannot establish that an individual account has migrated successfully. Recheck current plan limits before expanding usage; a successful data import is not a performance or cost benchmark.
Sources & method
The official Quest retirement notice was read on November 13, 2026. Product scope and migration instructions are attributed to Qoder; the acceptance checklist is SOTA’s assessment. No software installation, account migration, credit purchase or output-quality test was performed.
How SOTA reviews projects · Suggest a correction · Download the evaluation checklist
