When to use it. A real-time messaging interface that supports sending and receiving messages over MeshSocket. Ideal for device-to-device communication, command logs, or interactive chatbots.
Type
chat
Default size
4 rows × 4 columns
Symbol
bubble.left.and.bubble.right.fill
Docs
Docs complete
Search for it as
messages
conversation
assistant
ai
talk
inbox
Rendered by the app
Fields
12 fields you can set on a chat control. Every control also takes the shared fields (id, position, span, sync, action).
Fields
Field
Type
Default
What it does
Titlelabel
text
—
The name shown above the chat
Shows this text in the chat's header bar.
configconfig
object
—
Chat settings grouped together
Holds the chat's options (target, typing dots, receipts, reactions, replies, images, history, color) in one object.
allowClearconfig.allowClear
on / off
—
Lets you wipe the chat from here
Shows a Clear Chat menu in the header that empties this device's messages only; other people's windows are untouched.
Imagesconfig.allowImages
on / off
—
Lets people attach pictures
Turns image attachments on or off for this chat.
Reactionsconfig.allowReactions
on / off
—
Lets people react to messages
Adds a React choice to the long-press menu and shows emoji reactions on messages when on.
Repliesconfig.allowReplies
on / off
—
Lets people reply to a message
Adds a Reply choice to the long-press menu and shows replies in threads when on.
historyCountconfig.historyCount
number1–50step 1
—
How many messages are kept
Keeps only this many of the latest messages (1 to 50, default 50) in the window and in history sent to peers.
Read receiptsconfig.showReadReceipts
on / off
—
Shows when messages are delivered
Shows delivery and read marks under your messages when on.
Typing dotsconfig.showTypingIndicators
on / off
—
Shows when someone is typing
Shows animated typing dots while the other side is typing when on.
systemMessageEventsconfig.systemMessageEvents
string[]
—
Events that show as notices
Lists event names meant to appear as system notes in the chat; the app does not act on it yet.
targetconfig.target
text
—
Who to chat with
Sends your messages to the named MeshSocket peer as a private companion chat; leave it empty to chat with the whole channel.
Colorconfig.tint
color
—
The chat's accent color
Sets the accent color used by the chat bubbles.
Emits and receives
What this control sends when you use it, and what it can show or follow when data arrives.
Emits
Emits
Sends
When
Type
What it sends
When you send a messagemessage
submit
string
the message text
It goes to the MeshSocket peer named in Target, or to the whole channel when Target is empty
Example: Sample A
Receives
Receives
Takes
From
Type
What it does
linesshow
hub
json
a reply broadcast with its text and an optional sender name
the reply is added to the bottom of the conversation, shown under the sender name or the Target name
Example: {"text": "Sample A"}
Sample
The placeholder value the editor shows before real data arrives.
Long-press any message bubble for an iMessage-style menu: Copy (the message text),
Reply (when allowReplies), React (emoji, when allowReactions), and Delete
(removes it from this device's window only). The old tap-to-reveal reaction bar is gone —
reactions now live in this menu.
Clearing the window
Two independent ways to wipe the log:
Local — the header's Clear Chat menu (shown when config.allowClear is true, the
default) empties this device's window only. It does not notify peers.
Server-driven — the channel/companion authority clears every member's window by
emitting a chat_clear frame. In channel mode it rides the shared broadcast multiplexer
like every other chat frame; in companion (config.target) mode it arrives as a broadcast:
Incoming — the companion replies with a broadcast the chat listens for:
"broadcast": { "event": "chat_response", "text": "the reply" }
The optional name / sender.name / from field on the broadcast sets the reply's display name; otherwise it falls back to the target name.
The companion (server side) must wait for the MeshSocket welcome before routing — connect, wait_until_ready(), then wait for the welcome event before sending.
Without config.target (channel mode) the chat sends a chat_message event and listens on chat_message for the whole channel.