Google is shutting down Opal, its experimental visual builder for AI mini apps, on November 17. The editor and interactive runner are going away, along with the related feature called Gems made by Labs. Google says existing workflow files will remain in Google Drive, but it will not automatically move those workflows into a replacement.
That distinction matters if you built something other people use. A saved workflow contains instructions you can recover. It is not a working service after the runner closes. A good handoff preserves both the text and a record of what the app did, so someone can tell whether a replacement works the same way.
Document the workflow while you can see it
Google for Developers recommends opening Opal and copying prompts or custom instructions before the cutoff. Start with the workflows you would actually miss. On one page for each, record who uses it, what they provide, which steps transform the input and where the result goes. If one step consumes a file or a response from another step, write down that dependency rather than assuming it will be obvious later.
For example, a mini app that turns a rough meeting agenda into a briefing might accept an outline, group topics and format the briefing for distribution. Save the instructions for each of those steps separately. Record whether it should leave missing dates blank or flag them for review. Those details matter more than a screenshot of the final text. If you take a screenshot of the diagram, use dummy input and keep the image in an approved workspace.
Keep one representative input and one acceptable output, both free of sensitive information. Add a second example of an input that should be rejected or sent back for clarification. A workflow without an example can look complete on paper while the rebuilt version invents a missing deadline or puts an answer in a form the next step cannot use.
Where to look after the editor shuts down
The Opal FAQ says the files are kept under My Drive, in a folder named Opal. After the visual service ends, Google says you can download a workflow file and open it in a plain text editor to recover prompt text. Check you are signed in to the Google account that created the workflow, particularly if you switch between personal and work profiles.
If you are working from a downloaded file rather than the editor, read through the steps before copying them into another service. Give each step a name and find out which inputs it needs. Do not assume a tool mentioned in an old instruction is available in the replacement, or that access to a document carries over. List any external links and destination permissions separately so they can be checked without moving the original files.
Pick a replacement based on what needs to run
Google points users toward skills in Gemini for reusable chat instructions and Google AI Studio for more involved prototyping. Gemini Apps Help says ordinary Gems transition to skills on separate dates depending on account type. That automatic transition is not an Opal migration. A skill can be a reasonable fit for a person who wants to reuse a checklist or a writing format inside chat. It is not the same as restoring a shared mini app with inputs, a sequence of steps and an output destination.
Rebuild the smallest useful part first. If the app previously transformed an outline into a briefing, recreate that transformation and test it with the saved examples before reconnecting anything else. Review what happens when the input is blank, when information conflicts and when the model returns an unexpected format. If a step sends a message or updates a file, keep that step manual until the rest of the process produces consistent results.
Finally, tell existing users where the replacement lives and what it does differently. Give someone responsibility for the workflow and set aside a copy of the new instructions and sample tests. If the visual runner shuts down before you have time to rebuild, the immediate fallback can be a documented manual checklist, not a hurried attempt to replace all of the old app at once.



