Lantide Data

Back to Learning Center

Use @ to Point Precisely at Data and Analysis Artifacts

Read time: ~5 minutes · Series: Analyst practice · Next: Plan → annotate → Execute → Report


@ points; it does not paste content into chat

When a workspace has several Plans, Reports, or tables with similar names, typing @ and selecting an object adds one indivisible chip. The Agent receives a verifiable workspace identity, so it knows exactly what you mean.

A mention does not open a tab, put the entire document or data rows into model context, or grant extra permission. It only makes this turn precise; the Agent still reads schemas, documents, or runs queries only when the task requires it.

What you can mention

  • A Project, Plan, Report, HTML Report, or Reference
  • A saved SQL tab (not a temporary SQL tab)
  • A cached table, materialized MCP table, or table from a connected database
  • A queryable file or worksheet in the initial folder, an Additional folder, or a Cloud folder

You cannot create a mention for a whole workspace or data source, OS files, annotations, or deleted/archived objects. Select a queryable table or file instead, or describe it in text.

Three ways to insert one

  1. Type @ in the chat input. Choose a recent object or keep typing to search.
  2. Drag a supported sidebar item into the chat input.
  3. Right-click a supported sidebar item and choose Add to chat.

Use / to select, Enter or Tab to insert, and Esc to close the list while keeping the text you typed. A message supports up to ten mentions; Backspace or Delete removes one whole chip.

When it helps most

  • Deliverable: “Use @Q3 Report to shorten the summary and retain limitations.”
  • Data: “Compare @orders and @refunds date coverage; do not create a Plan yet.”
  • Evidence: “Check whether @clean_orders SQL can fan out, then write the recommendation into @Revenue Plan.”

Important analysis conclusions still belong in a Plan, SQL, and Report. Mentions solve “which object does this turn mean?”—they do not replace reviewable deliverables.

Copy, paste, and invalid objects

Copying within the same workspace preserves usable mentions. Pasting into another workspace, or referring to a deleted or archived object, safely degrades that chip to plain text. If an object becomes invalid while sending, the Agent does not start; remove the chip and search again.

Next