Omniscio

Team Chat follow a thread — get told about the replies you care about

- Follow a thread and every new reply in it notifies you — in a channel, in a DM, or from inside the thread itself. - Unfollow it and it goes quiet for you, even on a message you wrote, until someone @mentions you again. - You follow automatically when you start a thread, reply in it, or are @mentioned in it — the way Slack does it. - The state is yours alone and saved on your account, so it is the same on every computer and it survives a reinstall.

On this page

Where the control is

Two places, both one click:

  • The bell in the thread header. A ringing bell means you follow the thread; a crossed-out bell means you unfollowed it; a plain bell means you have not said either way.
  • Follow thread / Unfollow thread in any message's action menu — the hover toolbar's ⋯, or the right-click menu. It appears on a message that is part of a thread (a reply) and on a channel message that already has replies.

What it changes

A thread reply notifies you when:

  • someone @mentions you in it — always, even in a thread you unfollowed,
  • the reply is on a message you wrote,
  • you follow the thread,
  • or the thread is in a DM and you have not unfollowed it.

And it does not notify you when you unfollowed it, whatever else is true, unless the reply names you directly.

How it is stored (for developers)

Follow state is two bounded lists on your OWN saved/{uid} doc, in the same tenant root as the rest of your chat data:

Field Meaning
followedThreadKeys Threads you follow. Key is <channelId>/<threadId>.
mutedThreadKeys Threads you explicitly unfollowed.

Both are capped at 200 entries. Keeping "followed" and "unfollowed" apart is what makes "unfollowed stays quiet even though you replied before" expressible — absence alone cannot carry both meanings. The Firestore rules let only the owner write that doc, its existing desktop listener already syncs it to every surface, and the Cloud Function's reply fan-out reads the same fields through two indexed collection-group queries, so the notification cost is the number of followers of a thread, never the size of the channel.

  • Pure rules — src/shared/team-chat/thread-follow.ts (the key, the lists, the toggle plan, and reading a reader's state).
  • Client writes — src/renderer/src/features/team-chat/data/chat-thread-follows.ts, driven by useThreadFollow and the TeamChatThreadFollowButton.
  • Notification decision — decideReplyNotify takes the reader's state, and threadFollowStateOf is applied by the live watcher, the while-closed sweep, and the background sync alike, so every surface agrees.
  • Server fan-out — firebase/functions/src/team-chat/thread-follows.ts adds followers to the reply push list, drops unfollowed readers, and auto-follows the parent author and anyone @mentioned.
  • Auto-follow on reply — sending a reply follows that thread for you, best-effort, so a failed follow never fails the message.

The one keyboard entry point

toggleFollowThread semantics live in setThreadFollow(db, workspace, uid, channelId, threadId, follow, current); the UI hook useThreadFollow(channelId, threadId) exposes the same toggle for any future shortcut or the Topics lane.

Known limits

  • The server's follower lookup needs its two collection-group indexes on saved (followedThreadKeys, mutedThreadKeys). Until they are live, the lookup is skipped and notifications behave exactly as they did before follow existed — nothing breaks, followers are just not added server-side.
  • Following is per thread, not per channel; muting a whole channel is still the channel bell.
  • The phone app has no follow control yet; it sees the same state once it reads the same fields.

Last verified 2026-11-20