Record Locking
Reserve a record while you edit it so nobody else can start editing at the same time.
What it adds
Pessimistic locks on high-risk records: one editor at a time, with expiry and a supervised takeover path.
What your agent is told to do
5
What your agent is told to do
5-
1
Acquire the lock on the server when a user opens the edit view, storing the holder, the acquisition time, and an expiry.
-
2
Keep the lock alive with a heartbeat from the open editor and release it on save, cancel, or navigation away.
-
3
Enforce the lock on every write path, not just in the UI. A client-side lock is a courtesy, not a guarantee — the server must reject writes from anyone who does not hold it.
-
4
Let an authorized user force-release a lock they do not own, and record who broke which lock and when.
-
5
Do NOT lock reading. Viewers must always get through; only the edit action is gated.
Edge cases it handles
6
Edge cases it handles
6- A crashed browser or closed laptop leaves a lock with no owner. Expire on missed heartbeats, not only on an absolute timeout.
- The same user opening a second tab should take over their own lock, not be blocked by themselves.
- Show who holds the lock and since when. 'Locked by another user' with no name is a support ticket.
- A force-release must notify the displaced editor while they still have their unsaved work on screen.
- The lock holder must be warned before their lock expires mid-edit, with a way to extend it.
- Deleting or archiving a locked record has to release the lock rather than strand it.
Definition of done
8
Definition of done
8- Opening the editor acquires a server-side lock and closing it releases one.
- Writes from a non-holder are rejected by the server.
- Locks expire after missed heartbeats without manual cleanup.
- A user's own second session takes over rather than being blocked.
- The lock holder's identity and start time are shown to anyone blocked.
- Force-releases are permission-checked and recorded.
- 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.