apps/docs/content/sdk-features/cursor-chat.mdx
Cursor chat lets users send short messages that appear as bubbles near their cursor. It's designed for quick, ephemeral communication during collaborative sessions—a fast "look here" or "nice work" that doesn't interrupt the canvas workflow.
import { Tldraw } from 'tldraw'
import 'tldraw/tldraw.css'
export default function App() {
return (
<div style={{ position: 'fixed', inset: 0 }}>
<Tldraw
onMount={(editor) => {
// Start chatting programmatically
editor.updateInstanceState({ isChatting: true })
// Or set a message directly
editor.updateInstanceState({
chatMessage: 'Hello from the canvas!',
})
}}
/>
</div>
)
}
Cursor chat only appears when collaboration UI is enabled. On desktop, users press / to open the chat input, type their message (up to 64 characters), and press Enter to send. The message follows their cursor for a few seconds, then fades away.
Chat state lives in instance state with two properties:
| Property | Type | Description |
|---|---|---|
isChatting | boolean | Whether the user is actively typing |
chatMessage | string | The current message (max 64 characters) |
Read the current state with Editor#getInstanceState:
const { isChatting, chatMessage } = editor.getInstanceState()
Update it with Editor#updateInstanceState:
// Start chatting
editor.updateInstanceState({ isChatting: true })
// Update the message
editor.updateInstanceState({ chatMessage: 'Looking at this shape' })
// Stop chatting and clear the message
editor.updateInstanceState({ isChatting: false, chatMessage: '' })
Both properties are ephemeral—they don't persist to storage or survive page reloads.
When a user starts chatting:
CursorChatBubble component renders an input field at the cursor positionpointermove eventschatMessage updates in instance stateisChatting becomes falseMessages time out after 5 seconds while typing, or 2 seconds after the user stops.
The default keyboard action for cursor chat is /. You can find it under the action ID open-cursor-chat:
import { Tldraw, useActions } from 'tldraw'
function ChatButton() {
const actions = useActions()
return (
<button onClick={() => actions['open-cursor-chat'].onSelect('menu')}>Open cursor chat</button>
)
}
Inside the chat input:
| Key | Action |
|---|---|
Enter | Clear input (if content exists) or stop chatting (if input empty) |
Escape | Stop chatting |
In multiplayer sessions, chat messages synchronize automatically through presence records. The chatMessage field in TLInstancePresence contains the message other users see:
import { InstancePresenceRecordType, Tldraw } from 'tldraw'
// Creating a remote user's presence with a chat message
const peerPresence = InstancePresenceRecordType.create({
id: InstancePresenceRecordType.createId(editor.store.id),
currentPageId: editor.getCurrentPageId(),
userId: 'peer-1',
userName: 'Alice',
cursor: { x: 100, y: 200, type: 'default', rotation: 0 },
chatMessage: 'Check out this arrow!',
})
editor.store.mergeRemoteChanges(() => {
editor.store.put([peerPresence])
})
The presence derivation automatically includes the local user's chatMessage from instance state. Changes broadcast to other users automatically.
You can replace the default chat bubble by providing a custom CursorChatBubble component:
import { Tldraw, TLUiComponents, useEditor, track } from 'tldraw'
import 'tldraw/tldraw.css'
const CustomCursorChat = track(function CustomCursorChat() {
const editor = useEditor()
const { isChatting, chatMessage } = editor.getInstanceState()
if (!isChatting && !chatMessage) return null
return (
<div
style={{
position: 'fixed',
bottom: 20,
left: '50%',
transform: 'translateX(-50%)',
padding: '8px 16px',
background: editor.user.getColor(),
borderRadius: 8,
color: 'white',
}}
>
{isChatting ? 'Typing...' : chatMessage}
</div>
)
})
const components: TLUiComponents = {
CursorChatBubble: CustomCursorChat,
}
export default function App() {
return (
<div style={{ position: 'fixed', inset: 0 }}>
<Tldraw components={components} />
</div>
)
}
For customizing how remote users' chat messages appear, override the CollaboratorCursor component instead. See Cursors for details.
Cursor chat requires:
editor.store.props.collaboration !== undefined)Check availability before triggering chat programmatically:
const hasCollaboration = editor.store.props.collaboration !== undefined
const isTouchDevice = editor.getInstanceState().isCoarsePointer
if (hasCollaboration && !isTouchDevice) {
editor.updateInstanceState({ isChatting: true })
}