Presence Indicators
Show who else is on this screen right now.
What it adds
Live avatars of the other users currently viewing or editing the same record.
What your agent is told to do
5
What your agent is told to do
5-
1
Have each client heartbeat its presence on a short interval and treat presence as expiring state, not as a flag toggled on connect and off on disconnect.
-
2
Expire an entry after a couple of missed heartbeats. Crashed tabs, killed apps, and sleeping laptops never send a disconnect.
-
3
Collapse a user's multiple tabs and devices into one avatar. Three of the same face means the plumbing is leaking, not that three people are here.
-
4
Scope presence to the record and the workspace, and check the viewer's permission before revealing that someone is present.
-
5
Do NOT present presence as a lock. It tells the user someone else is here; it does not prevent a conflicting edit, and implying otherwise causes lost work.
Edge cases it handles
6
Edge cases it handles
6- Tabs in the background should throttle or stop heartbeating, so an idle tab does not report an attentive user.
- Presence is a privacy surface. Some users and some plans must be able to browse without broadcasting it, and that setting must be honoured.
- When the realtime transport is down, hide the indicator entirely rather than showing a stale roster that says nobody is here.
- Cap the visible avatars and roll the rest into a count — a busy record can have dozens.
- Do not leak identity beyond what the viewer can already see; a name or avatar is still an information disclosure.
- Viewing and editing are different signals. If you show both, keep them visually distinct.
Definition of done
8
Definition of done
8- Presence is heartbeat-driven and expires without an explicit disconnect.
- Ghost entries clear within seconds of a crashed or sleeping client.
- Multiple tabs and devices for one user render as a single avatar.
- Presence is scoped by record, workspace, and viewer permission.
- Users can opt out of broadcasting their presence.
- The indicator hides when realtime is unavailable rather than showing stale data.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Voice Notes
Voice Notes
Say it instead of typing it, and attach the recording where the conversation is.
What it does
In-app recording of short audio notes attached to a record, comment, or message.
How it works
- 1 Add recording to the places where people already leave text, most likely alongside Comments and Mentions, so a voice note is another kind of comment rather than a separate feed nobody checks.
- 2 Store the recording through the app's existing file upload path so a voice note inherits the same retention and access rules as any other attachment on the record, and disappears with the record when it is deleted.
- 3 Show a live duration and a simple level meter while recording, and let the user review and discard before it is sent. Nobody should be committed to a recording the instant they stop.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-notes
Direct Messages
Direct Messages
Let two users hold a private conversation inside the app instead of leaving to email.
What it does
One-to-one private threads with message history, per-conversation unread counts, and blocking.
How it works
- 1 Build the conversation list, the thread view, and the unread badge. Keep the first version to one-to-one threads only and defer group conversations, reactions, threading, and file attachments rather than shipping all of them half-finished.
- 2 Reuse the app's existing Read and Unread State and Notification Center rather than inventing a second unread mechanism and a second alert path. A message notification should sit alongside every other notification the user gets.
- 3 Reuse the composer, mention handling, and rendering rules from Comments and Mentions instead of writing a second message editor with subtly different escaping.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/direct-messages
Internal Notes
Internal Notes
Give staff a place to write things the customer must never see.
What it does
Notes attached to a record that are readable only by internal roles, and that never appear in any export, feed, or API response.
How it works
- 1 Model an internal note as a distinct visibility state on the server, not a flag the client filters on. Every read path — record view, search, digest emails, exports, webhooks, API serializers — must exclude internal notes for anyone without the internal role.
- 2 Give internal notes a visual treatment that cannot be confused with a public comment: different surface, a persistent label, and a warning that survives collapse or truncation. If a user has to remember which box is which, this feature has failed.
- 3 Decide explicitly what an impersonating admin or a support session sees, and state the rule in the UI. Support staff reading internal notes is usually fine; a support session rendering them inside a screen the customer is watching is not.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/internal-notes
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.