What happens when an AI tool is sold, renamed or shut down?

AI tools change hands and change shape faster than most software. In 2026 alone, several coding tools that many learners used were shut down, folded into a bigger product, or repackaged after a sale. None of this means you chose badly. It means that any tool you build with today should be one you could leave tomorrow.

What happens to you depends on the kind of change. Here are the four common ones, with real examples from this year.

Four ways a tool can change under you

1. It shuts down with a deadline. Google's Firebase Studio, a browser-based app builder, is being retired. Google announced the sunset on March 19, 2026; since June 22, 2026, nobody can create new workspaces or sign up. On March 22, 2027, the service closes and any data left in it is permanently deleted. Apps already deployed on Firebase keep running, because the backend services (database, login, hosting) are separate from the editor. Google points users to Antigravity for code-first work and to Google AI Studio for browser prototyping, and provides migration steps for both.

2. It stops abruptly, open source or not. Roo Code was a popular open-source coding agent for VS Code. Its repository was archived on May 15, 2026, the same day the extension was shut down, and it is now read-only. The page suggests two alternatives: ZooCode, a fork started by its community, and Cline, the project Roo Code was originally built from. Open source helped here: the code still exists, and others can carry it on. But your setup, saved modes and habits still had to move.

3. It is replaced by a successor. Google's Gemini CLI, a terminal coding agent, now serves mainly enterprise Code Assist customers. According to its README, free individual users and Google AI Pro and Ultra subscribers were moved to a new tool, Antigravity CLI, on June 18, 2026. The old tool still works for some accounts, but it isn't tuned for the newest Gemini 4 models.

4. It is sold or renamed, and the deal changes. The old Windsurf pricing page now forwards to Devin's pricing page, where Cognition sells an editor called Devin Desktop. Cursor's pricing page now bundles xAI's Grok models and features of the X social network into its plans, and bills other companies' models, such as Claude and GPT, at API list price. If you chose a tool for its price or its model lineup, a change of owner can change both.

What you lose, and what you keep

The table shows what is at risk in each case, and what protects you.

How do you avoid getting locked in?

Lock-in is the cost of leaving. It is low when everything you made can be carried out in standard formats, and high when your work only makes sense inside one product. A few habits keep it low.

Own your code in git. Whatever builder or agent you use, make sure the code lands in a repository you control, with regular commits. Most app builders offer GitHub sync; turn it on before the project matters. If a tool offers no export at all, treat it as a place for experiments, not for something you plan to keep.

Keep your instructions portable. Write project rules in an AGENTS.md file at the root of your repository. It is plain Markdown, and many agents read it, including Codex, Cursor, Jules, Kilo Code and GitHub Copilot's coding agent; Claude Code can import it from its own CLAUDE.md. When you switch tools, your rules come with you.

Separate the builder from the backend. Prefer setups where your database, login and hosting are services you could reach without the AI tool, such as your own Supabase or Firebase project. That is why Firebase Studio users keep their deployed apps: the editor is closing, the backend is not.

Avoid depending on one model. Tools that let you choose among several model providers, or bring your own key, make it easier to absorb a price change or a model being dropped.

Watch for the warning signs. A new owner, a sudden plan change, a "migration" page or a repository that stops getting updates are your cue to check your exports, not to panic. Firebase Studio gave a year of notice, but not every project will be that generous, so an export you already have beats one you plan to make.

A good test is simple: if this tool disappeared tomorrow, could you open your project in another editor, point a different agent at it, and keep going within a day? If yes, you are free to enjoy the tool for as long as it lasts.