Mentions
Reference for the @ and # mention menus inside a canvas document.
Canvas documents support the same @ and # mentions you use in
messages, so a doc can link to people, other canvases, spaces, and
tasks without leaving the editor.
@ — people and agents
Type @ anywhere in the document. The menu shows everyone you can
mention from the current workspace.
| Type | Example | What it does |
|---|---|---|
| Teammate | @alice | Inserts a chip linking to the person's profile |
| Agent | @claude | Hands the document to the agent so it can read or edit |
You only see people and agents that exist in your workspace and that
you have access to. Group mentions (@design-team) are supported in
messages but not yet inside canvas documents.
# — spaces, canvases, boards, and tasks
Type # to reference another resource. The menu surfaces results from
across the workspace, scoped to what you can see.
| Type | Example | What it does |
|---|---|---|
| Space | #design | Inserts a chip; click to navigate to the space |
| Canvas document | #Project plan | Opens the document in-place |
| Canvas database | #Roadmap | Opens the database in-place |
| Board | #Roadmap | Opens the board for that group or space |
| Task | #Refactor onboarding or #DES-12 | Opens the task in a modal without leaving the document |
How task search works
Tasks match in two ways:
- By display id (typeahead, prefix-only) — typing
#DESlists every task in theDESgroup; typing#DES-12narrows to tasks whose number starts with12(DES-12,DES-123). - By title (substring) — typing
#refactormatches any task whose title contains "refactor".
Archived tasks are hidden from the menu. You only see tasks that you have access to (member of the owner group, or member of any space hosting a board the task is cross-posted to).
Pasting a link turns into a mention
You don't have to type @ or # to mention something. Paste a link
to a Monad space, canvas, agent, or thread and the document swaps the
URL for the matching mention chip automatically — same chip you'd get
from the menu. (DM permalinks stay as plain hyperlinks for now — they
don't have a chip representation yet.)
When you paste a thread URL, you get a chip that links to the thread. If the URL points to a specific reply inside the thread (the "Copy link to message" link on a reply), the chip reads "Reply in #channel" instead of "Thread in #channel" and clicking it jumps straight to that reply.
The auto-conversion is skipped when the link reads as code:
- The pasted text is wrapped in matched backticks (
`https://…`). - The cursor sits inside an inline code span or a code block already.
- You're mid-typing a code span — you typed an opening backtick, then paste, and you intend to type the closing backtick afterwards. As long as there's an unclosed opening backtick before the paste point, the link stays plain.
Any other shape — a bare link, a link preceded by a stray unmatched backtick that you're not turning into a code span, a link with surrounding whitespace — still converts.
If the link points somewhere you can't see (a private space, an archived canvas), the paste falls back to a regular hyperlink.
Hover and click behaviour
Hovering a chip shows a preview card. Clicking:
- A person chip opens their profile.
- A space chip navigates to the space.
- A canvas chip opens the document or database in-place.
- A board chip opens the board it points at — the same one a cross-posted task would land on.
- A task chip opens the task detail modal — your document stays open behind it, so you can pop a task open without losing your caret position.
- A thread chip navigates to the thread in its space or DM. If the chip targets a specific reply, you land on that reply with the usual highlight.
If you no longer have access to the resource, the chip stays in place and the preview explains what happened.