File References (@ Mentions)

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want File References (@ Mentions) working in a real project rather than a sandbox.

   Set up File References (@ Mentions) in this project — mention code files directly in chat with @ to scope agent context. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Refactoring a single component

   The record lists this as one of the jobs File References (@ Mentions) is meant for, so it is a fair first test of whether it fits your app.

   In this project, use File References (@ Mentions) for refactoring a single component. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   File References (@ Mentions) is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses File References (@ Mentions) before I publish. Check @-mention any file in the project and scope agent reads to selected files, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Asking targeted questions about one file

   A second job the record lists for File References (@ Mentions), useful once the first path works.

   Extend this project so File References (@ Mentions) also covers asking targeted questions about one file. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is File References (@ Mentions)?

  File References (@ Mentions) is Lovable's Editor feature: Mention code files directly in chat with @ to scope agent context. Typing @ in chat lets users pick specific code files to reference, scoping the agent's reads and edits to the chosen files rather than the whole project.

• Is File References (@ Mentions) GA or in beta?

  File References (@ Mentions) is generally available (GA) on Lovable.

• What Lovable plan includes File References (@ Mentions)?

  File References (@ Mentions) is available on all Lovable plans.

• When did File References (@ Mentions) launch?

  File References (@ Mentions) launched on Dec 23, 2025.

• Revert and Edit MessagesSame category, also GA · Nov 2025
• Themes and Design ViewSame category, also GA · Nov 2025
• Design TemplatesSame category, also GA · Feb 2026