Lovable: Remix No Longer Copies Files by Default
LovableLovable changed the default behavior of remixing a project: files uploaded to the original project's Files tab no longer copy automatically into the new remixed project. Builders with edit access can still bring those files along by enabling "Copy project files to new project" in the Remix dialog, sitting next to the existing chat history toggle. Public remix links are unaffected in scope, still carrying code only, since files and chat history were never available to someone without edit access.
Key Takeaways
- File copying is now opt-in during a remix, reversing the previous default of automatically copying a project's Files tab uploads.
- A new toggle controls the behavior, "Copy project files to new project", visible only to someone with edit access to the original project.
- It mirrors the existing chat history toggle, which already required edit access and stayed off unless explicitly switched on.
- Public remix links are unaffected in scope, still carrying code only, with no path to include files or chat history without edit permissions.
- The change tightens privacy by default, reducing the chance that reference documents or design files travel with a project nobody meant to share.
- Code and settings still copy as before, since the change is specific to the Files tab rather than a project's broader remix behavior.
A Safer Default for Remixing
Lovable changed what happens to a project's uploaded files when it is remixed: files in the original project's Files tab no longer copy over to the new project automatically. Previously, remixing a project could carry along file uploads without the person remixing necessarily intending that, a default Lovable has now tightened.
Files Become Opt-In
Builders with edit access to the original project can still bring those files along by turning on "Copy project files to new project" inside the Remix dialog, a toggle that sits next to the existing option to copy chat history (including any files attached to chat messages). Both toggles are off by default and only appear at all for someone who already has edit access to the project being remixed.
What Public Remix Links Still Do
For anyone remixing through a project's public link rather than as a collaborator with edit access, the behavior is unchanged in spirit but now explicit: a public remix carries over code only. Chat history and Files-tab uploads are excluded entirely and cannot be added after the fact by someone without edit permissions. The change gives project owners more control over what leaves their project when someone else remixes it, particularly relevant for anyone who uploaded reference documents, design files, or other material into the Files tab that was never meant to travel with a public copy.