Omniscio

Team Chat (built-in channels and direct messages) (part 4)

Part 4 of the Team Chat page: what the feature deliberately does not do and the shortcuts still to come, then the engineering — how messages, threads, pins and reactions are stored and kept honest, how search is built and why it is not switched on yet, and what an operator still has to do to take Team Chat live.

On this page

What it is

This is part 4 of the Team Chat (built-in channels and direct messages) page: the limits of the first version and the shortcuts planned but not built, then the engineering for someone who works on the product — the chat data layout kept identical across desktop and phone, how message search is indexed and why it answers "not switched on yet", and the deployment steps an operator still owes.

Where to find it

The same surface as the parent page: once it is switched on from Settings → Lab → Team Chat, Team Chat appears as a built-in virtual project in the projects sidebar, with the channel and direct-message list in the sidebar pane and the open conversation filling the main panel. It ships dark until then, and the parent page covers finding and enabling it. The limits and planned shortcuts are about the chat window itself; the engineering sections are design notes for someone changing the code.

How it behaves

Limits / not in v1

  • Teammate pickers for a new DM use the live member roster (dmCandidatesFromMembers), so a DM can start as soon as the workspace's members materialize; the deterministic-id open path is fully wired. The member directory (a read-only roster) is built. Inviting by email is available in chat for admins (reusing the workspace bulk-invite path — see "Invite teammates by email" above); removing members still lives in the workspace-setup lane (Settings → User Management).
  • Built v1 surface: create public/private channels + DMs, send / receive / paged history, presence + typing, @mentions (including in public channels), real names/avatars, edit/delete-own, reactions, pins, threads, profile card, member directory, unread badges, the Cmd/Ctrl+K quick switcher, per-channel notification preferences, and right-click channel management (edit name/topic, leave, delete).
  • Built in this wave (v2 — see "New in this wave" above): file uploads / attachments, saved items, custom status, and scheduled send — plus message-surface polish, composer power, wired-in search, and desktop notifications + an unread badge. Editing a message re-parses mentions[] so an added @mention renders as a chip, but does not re-NOTIFY (the notification function fires only on message create — matching Slack).
  • Sending pace — you can send up to 5 messages every 10 seconds in one channel. A send past that is never lost and never silent: the message stays marked failed with Retry (in the inbox its text goes back into the message box), and the notice names the limit, how many you sent and how many seconds until you can send again. Messages the app posts for you — webhooks, routed alerts, PM status updates, membership changes, Mission Control bot posts and your agent's posts — never count toward that pace and are never held back by it.
  • Notifications — the push-to-your-phone fan-out comes from the notification Cloud Function (on an @mention or DM); you control all / mentions / none globally and per channel via Notification preferences above. The message data model carries the parsed mentions[] it needs.

When something goes wrong

Every failure says what happened and what you can do, in plain words. The raw error stays in the app log, never on screen.

  • A load that fails says so and offers a way back. The Scheduled view shows an error with Retry instead of spinning forever. The New DM picker says it could not load teammates, with Retry, instead of claiming nobody else is in the workspace. A conversation whose messages will not load shows Try again instead of "No messages yet", and one you are not allowed to read says "You do not have access to this conversation."
  • Live updates that stop are announced. If Team Chat gives up on a live listener for good, one warning says new messages may not appear, with Reconnect. A working connection never raises it: every listener asks Firebase to report the server confirming data Team Chat already showed, so a quiet but healthy conversation still proves it is live (before 2026-10-30 it did not, and the warning appeared on healthy connections). A brief connection error is retried quietly; an error that will not go away shows that screen's own message (for example Could not load custom emoji) — at once when it can never recover, or when the retries give up — and a loading spinner stops on the first failure rather than waiting. A background sync of your other workspaces that only lost its connection reconnects silently, so only a refusal it cannot retry past says their unread counts may be out of date, at most once every 30 minutes.
  • Channel actions name the channel and the cause. A failed edit, archive, unarchive, leave or delete names the channel and distinguishes "you do not have permission, ask a workspace admin" from "check your connection, then try again". A failed channel delete stays on screen with Try again until you act, because its confirm dialog has already closed. A failed workspace leave or delete says you are still a member, or that the workspace is still there.
  • An unread badge never lies. If the server refuses to record that you read a channel, its unread badge comes back at once instead of staying falsely cleared, and opening the channel again retries.
  • Screen readers hear "Message sent" only when a message really went out, never for a send that was turned down.
  • On a phone, a toast never covers the composer. The composer reserves its space at the bottom, so a send failure shows above the message box.
  • Starting a session and importing have their own notices: see Start a working session from a thread in part 3 and the import wizards (Slack, Discord).

Planned keyboard shortcut enhancements

Current shortcuts cover composing (Ctrl+B/I/E formatting, send-key modes), navigation (Ctrl+Alt+K quick switcher, Alt+Up / Alt+Down / Alt+Shift+Down channel, DM and next-unread stepping, Ctrl+Shift+D jump to date), topics (Alt+Shift+N new topic) and thread management (Ctrl/Cmd+W close, R to focus reply, up-arrow to edit last). Planned: shortcuts for common per-message actions (pin, react, reply, save, copy link) and channel actions (mark as read, mute/unmute, browse channels), for keyboard parity with Slack/Discord.

This is one of five pages describing Team Chat. The parent page describes the feature and what the first version can do. Its four companions are part 2 on the second wave of features and workspaces, part 3 on the phone client, notifications and the smaller surfaces, part 4 on the limits and the engineering behind it, and part 5 on bringing people into a workspace.

Two pages outside this set are worth having open alongside it: cross-org-connections.md for connecting with someone in another organization, and session-starter-bot.md for the bot that starts a Claude session from a channel message.

Last verified 2026-11-15