Team Chat message forwarding (forward / share a message to another channel or DM)
A planned Team Chat feature that forwards, or shares, any message from one channel or DM to another, the way Slack, Teams and Discord let you reshare a message across conversations. The forwarded message would arrive in the target channel attributed to the forwarder with a visible link back to the original, and the feature is gated and not yet visible to users.
What it is
Status: In-development (gated via team-chat-message-forwarding unreleased feature). Not yet visible to users.
Forward (share) any Team Chat message from one channel or DM to another — the way Slack, Teams, and Discord let you reshare a message across conversations. The forwarded message arrives in the target channel attributed to the forwarder, with a visible link back to the original.
Where to find it
There is nowhere to find it yet, and that is honest rather than an omission: the whole feature is gated behind the team-chat-message-forwarding unreleased feature and is not yet visible to users. When it is revealed, the forward action is the one that appears on the per-message hover toolbar in a Team Chat channel or DM, and on the mobile long-press action sheet.
How it behaves
What it will do
Forward (share) any Team Chat message from one channel or DM to another — the way Slack, Teams, and Discord let you reshare a message across conversations. The forwarded message arrives in the target channel attributed to the forwarder, with a visible link back to the original.
Design considerations
- A forward is a NEW message in the target channel (not a symlink). Deleting the original does not remove the forward.
- Attribution: "Forwarded by [Name] from #channel" — similar to Slack's forwarding display.
- Permission: you can forward to any channel you can post in. Private-channel messages forwarded to a public channel should warn (content leak).
- The feature is purely additive — no changes to existing message schema beyond an optional
forwardedFrommetadata field on new messages.
For agents
Existing infrastructure that supports it
- Hover toolbar extension point —
TeamChatHoverToolbar.tsxalready renders per-message actions (react, reply-in-thread, edit, overflow menu). A forward button slots in alongside these, gated by the unreleased-feature visibility check. - Mobile action sheet — the long-press action sheet mirrors the hover toolbar; a forward row would appear there for phone users.
- Message data structure —
ChatMessagecarrieschannelId,id, and full content. A forwarded message can reference the original via these fields. - Cross-channel access — the user's channel list is already loaded; a channel picker (similar to the quick switcher or the new-DM picker) can present forwarding targets.
- Deep links —
omniscio://chat/…links already resolve to a specific message in a specific channel, so the "view original" back-link is a solved problem.
Setting
teamChatMessageForwardingEnabled (boolean, default false) — the unreleased-feature gate. Reveal via Settings > Lab or AMC_SHOW_TEAM_CHAT_MESSAGE_FORWARDING=1.
Related
The surface this action belongs to is described on Team Chat. Its sibling in-development action, translating a message in place, is on Team Chat message translation. Attaching a file to a message, which is a different thing from forwarding one, is on Chat attachments.
Last verified 2026-09-23