Skip to main content
Vibe Code Forum

Question: Do I own the code an AI tool writes, and can I move it elsewhere?

A common worry before people put serious time into a project: if an AI tool or app builder wrote the code, is it mine? And if I want to leave the tool, can I take the project with me?

Solution

By Vibe Code Forum team in post #2

Moving it: usually yes, if you set it up early. Most app builders can sync your project to GitHub or export it as files; AI editors and terminal agents work on files on your own computer, so the code is already yours to move. Check before you build anything important:

  • Can the tool push to a GitHub repository you own? Connect it on day one.
  • Does the exported project run elsewhere? Try it once: clone it and run it locally. See Moving between paths.
  • What else is tied to the tool: its database, sign-in or hosting? Those need moving too, and data may need exporting separately.

Owning it: the tools' terms of service generally say the output belongs to you, but terms differ and change, and copyright rules for AI-generated work are still developing in many countries. Read the current terms of the tool you use, and if the code is central to a business (for example you're raising money or selling the company), get proper legal advice.

Practical protections either way: keep your own GitHub copy, keep your own database backups, and keep track of which third-party packages your project uses and their licences (your AI tool can list them for you).

Read it in context

Moving it: usually yes, if you set it up early. Most app builders can sync your project to GitHub or export it as files; AI editors and terminal agents work on files on your own computer, so the code is already yours to move. Check before you build anything important:

  • Can the tool push to a GitHub repository you own? Connect it on day one.
  • Does the exported project run elsewhere? Try it once: clone it and run it locally. See Moving between paths.
  • What else is tied to the tool: its database, sign-in or hosting? Those need moving too, and data may need exporting separately.

Owning it: the tools' terms of service generally say the output belongs to you, but terms differ and change, and copyright rules for AI-generated work are still developing in many countries. Read the current terms of the tool you use, and if the code is central to a business (for example you're raising money or selling the company), get proper legal advice.

Practical protections either way: keep your own GitHub copy, keep your own database backups, and keep track of which third-party packages your project uses and their licences (your AI tool can list them for you).

Nobody has confirmed this yet. If you try it, say how it went.

More in Ask for help