侧边聊天连接

Side-chat connections

每次与 Muse 的对话都有一个聊天 UUID。已连接的消息应用是侧边聊天(side chat)的传输通道;传输通道绝不会创建第二份对话记录,也不会为另一个聊天的回复选择接收人。

Every conversation with Muse has a chat UUID. A connected messaging app is a

transport for a side chat; the transport never creates a second transcript or

chooses the recipient of another chat's reply.

可用性
Availability

在协助连接之前,先读 `~/docs/chat-connections/<provider>.md`。只有可用的提供方才有指南。缺少目录意味着这个 Muse 当前没有任何可用连接。`chat.connection_status` 提供当前状态;提供方不可用错误是针对这个 Muse 的。仅凭已连接状态不能证明消息在正常流动。

WhatsApp 是目前宣传的提供方。Discord 和 SMS 没有这种连接。通过配对手机发短信见 `~/docs/calls-texts-notifications.md`。在配对的 Mac 上使用信息(Messages)见 `~/docs/devices/mac_app.md`;那是独立的设备能力。

Read `~/docs/chat-connections/<provider>.md` before helping with a connection.

Only available providers have guides. A missing directory means none are

available on this Muse right now. `chat.connection_status` supplies current

state; an unavailable-provider error is specific to this Muse. Linked status

alone does not prove messages are flowing.

WhatsApp is the advertised provider today. Discord and SMS have no such

connection. Texting through a paired phone is covered in

`~/docs/calls-texts-notifications.md`. Working with Messages on a paired Mac is

covered in `~/docs/devices/mac_app.md`; it is a separate device capability.

连接流程
Connection flow

使用提供方指南中的官方安全应用链接。应用现有的 Messaging Channels 界面使用同一流程,在客户端更新前可能仍保留该名称。二维码、配对工件(pairing artifact)和 Connect 按钮归应用所有。状态查询和断开使用 `chat.connection_status` 和 `chat.disconnect`,以 `provider` 为参数。支持的偏好设置在用户自己的 Muse 聊天中用 `chat.configure_connection` 配置。

Use the provider guide's official secure app link. The app's existing

Messaging Channels screen uses this same flow and may retain that label until

the client updates. QR codes, pairing artifacts, and Connect buttons belong to

the app. Status and disconnect use `chat.connection_status` and

`chat.disconnect`, with `provider` as the argument. Supported preferences use

`chat.configure_connection` from the user's own Muse chat.

消息归属
Message ownership

回复属于接纳用户消息的那个聊天。运行时(runtime)在执行前捕获该 UUID 和当前的绑定权限;模型不选择回复的界面。`chat.send_message` 不能从另一个聊天向提供方对话推送一次性消息。在提供方侧边聊天中创建的计划任务投递到那里;在主聊天中创建的任务留在主聊天。重连不能把排队中的工作重定向到替代账户。

各提供方的能力不同。WhatsApp 连接是一对一的,不暴露用户的其他消息或个人发送身份。关于媒体、群组支持、偏好设置和结构化批准,请查阅各自的指南。

A reply belongs to the chat that admitted the user message. The runtime

captures that UUID and the current binding authority before execution; the

model does not choose the reply surface. `chat.send_message` cannot push a

one-off message into a provider conversation from another chat. A scheduled

task created in a provider side chat delivers there; a main-chat task stays in

main chat. Reconnection cannot redirect queued work to a replacement account.

Provider capabilities differ. The WhatsApp connection is one-to-one and does

not expose the user's other messages or personal sending identity. Consult

each guide for media, group support, preferences, and structured approvals.