Lovable: Cross-Project Referencing
LovableLovable introduced cross-project referencing, a new capability that allows the AI agent to read and reuse implementations from other projects within the same workspace. Using @ mentions in chat, developers can direct Lovable to pull in file structures, source code, and even chat history from any other project, then recreate or adapt that logic in the current one — without modifying the referenced project. Workspace admins retain full control through opt-out and privacy settings.
Sources & Mentions
2 external resources covering this update
Cross-Project Referencing in Lovable
Lovable has introduced cross-project referencing, a workflow-changing capability that eliminates one of the most common friction points in multi-project development: rebuilding the same components from scratch every time.
How It Works
When working in any Lovable project, developers can now reference other projects in their workspace using @ mentions directly in the chat. Lovable's agent reads the file structure, source code, and relevant chat history of the referenced project to understand how a feature or component was originally built. It then recreates or adapts that implementation in the current project — leaving the source project completely unchanged.
Beyond explicit @ mentions, developers can also simply describe what they want ("use the authentication flow from my dashboard project") and Lovable will identify and apply the relevant context automatically.
Why It Matters
For teams and individual developers managing multiple related projects — such as a design system shared across several apps, or a reusable backend integration — this feature dramatically reduces redundant work. Previously, reusing a pattern meant manually copying code or re-explaining the implementation from scratch. Now, Lovable carries the institutional knowledge of an entire workspace forward into every new project.
Privacy and Admin Controls
Lovable built privacy controls directly into the feature. Individual project owners can opt out of sharing their project's context by navigating to Project settings → Cross-project sharing. Workspace administrators have a broader override available under Settings → Privacy & security, where they can disable cross-project referencing across the entire workspace.
This layered permission model ensures that teams with sensitive projects — or enterprises with strict access boundaries — retain full control over what context is accessible across their workspace.