The problem
A writer and her co-writer work on the same script from two cities. A director reads along and leaves notes. An actor opens the scene the night before a table read. They need to know who else is in the project and where, to talk about a specific line without copying it into a chat, and above all to never find that the other person’s laptop has replaced their afternoon’s work.
Collaboration features are also where tools become noisy: avatars of everyone who ever opened the file, cursors flickering across the page, red badges, a feed of activity. Kwark is a calm place to write; the work stays in front.
Kwark’s answer
Presence: only when someone is here
The presence bar (components/presence/PresenceBar.tsx) is empty when nobody else is here. That is the ordinary case, and it should take up no room at all rather than announcing that you are alone. When others are here it shows up to five initials in each person’s colour, then “+{n}”. Each mark’s tooltip says who and where: “Dev Rao — in the screenplay”, “Asha — in characters”. The bar’s accessible name counts them: “2 other people here”.
Presence is per project, with the module each person is in, so a director on the Breakdown can see the co-writer is in the screenplay without either being interrupted.
Cursors: where the hand is, in page terms
PresenceCursors.tsx draws other people’s pointers over a surface:
- Positions are fractions of the surface, not pixels, so a cursor lands on the same place on the page for someone with a different window size.
- Only people who can change what they are looking at broadcast a pointer. A reader’s cursor drifting across your script tells you nothing you need, and it is not free on the free tier.
- Leaving the surface takes the cursor away rather than stranding it at the edge.
- The layer ignores the mouse entirely, so nothing can come between someone and their work. Movement between messages is smoothed by a transition, not by sending more messages.
- In the screenplay, a co-writer’s caret shows with their name at the insertion point.
Comments: anchored, quiet, resolvable
The comment dock (components/comments/CommentDock.tsx):
- New comment asks you to “Tap what it is about”: a line, a card, a shot. The comment is pinned there.
- A thread shows On this screen or On another view, so a note made in the Breakdown about Scene 12 is not lost when you read the script.
- Each thread: Reply (“Write a reply”), Resolve, Reopen, Edit, Delete. Resolved threads move out of the way, not out of existence.
- Filters: which comments to show (open or resolved), whose (Everyone or a person), Newest or Oldest first.
- Mentions: “@” a person; they see “Someone mentioned you” (or “{n} remarks mention you”) with Show.
- Empty: “Nothing said here yet. Start the conversation.” / “No comments here yet.” / “Nothing has been resolved here.”
- On the page, a comment pin (a mango tag with the count) marks the line. On a phone, a dot on the floating button means comments are waiting for you (Decision 0016); on the screenplay’s Menu, the same dot.
Two sessions, one script
The screenplay is protected by revision stamps (see Saving and sync). If the script was changed in another session while you wrote:
This screenplay was changed in another session. Your edits are kept on this device and have not overwritten it. Loading the newer version saves yours as a snapshot first.
with Load the newer version and Keep mine. Nothing is lost either way.
When the same person opens the editor in a second window, the session lock offers to take over: “Taking over closes editing in the other window and safely transfers the latest text here.” The other window becomes read-only with “Close and keep reading”. The audit flagged this dialog’s Title Case labels (“Active Editing Session”, “Resume Editing Here”) as words to fix: the pattern is right, the words are not yet.
Anatomy
| Part | Means | Shown |
|---|---|---|
| Presence marks | Who else has this project open, in their colour | Only when someone else is here |
| “+n” | More people than the five shown | When more than five |
| Peer cursor | Another editor’s pointer, in page terms | Only for people who can edit |
| Peer caret with name | Where a co-writer is typing | In the screenplay |
| Comment pin with count | Comments on this line or object | On the page |
| “On this screen” / “On another view” | Where a thread is anchored | In the dock |
| Dot on the floating button or Menu | Comments waiting for you | Phones and the screenplay |
| Conflict banner | Two sessions changed the script | Until you choose |
Rules
- Must hide presence entirely when nobody else is here.
- Must broadcast pointers only from people who can edit, and drop them when they leave the surface.
- Must anchor every comment to what it is about, and show where when it is on another view.
- Must keep both versions when two sessions change the screenplay; the writer chooses.
- Never show read receipts, “last seen”, typing indicators for readers, or a public activity feed. The audit’s chair rejected read receipts.
- Never pulse, animate or colour-alarm a badge to draw people back.
- Never let a comment, cursor or presence layer intercept a click on the work.
- Always use each person’s one colour everywhere (presence, cursor, caret), and always with their initials or name, never colour alone.
- Always count presence and cursor traffic against the free tier: one shared presence room per project, no per-module listeners.
Edge cases
- Someone joins as a Reader. They appear in presence (others know who is reading) but do not broadcast a cursor.
- A person is removed while here. Their marks leave at once; on their side, the named access-ended page.
- Many people at a table read. Five marks and “+n”; the dock filter Whose comments to show narrows to one person.
- Offline. Comments queue on the device like any change; presence simply shows nobody.
- A comment on text that was later cut. The thread stays and says it is on another view; it is never silently deleted with the text.
- Indian-script names. Initials come from the first letter as written; never force Latin initials.
Phone and desktop
On desktop, presence marks sit in the project header at the right; the comment dock is a side panel beside the page. On a phone, presence sits in the Menu sheet’s header, the dock is a full-height sheet opened from Comments in the floating button, and New comment asks you to tap what it is about before you write. Cursors are not drawn on phones; carets are.
Writing
- Presence tooltip: “{Name} — in {module}”, with plain module names (“the screenplay”, “the outline”, “the calendar”).
- Dock: New comment, “Tap what it is about”, “Write a comment”, “Write a reply”, Send comment, Send reply, Resolve, Reopen.
- Mentions: “Someone mentioned you”, “{n} remarks mention you”, Show.
Accessibility
- Presence is a group with a counted label; each mark has the person’s name and place as its accessible name, not only a tooltip.
- Peer cursors are
aria-hidden; they are visual help, and announcing every move would be noise. - Comment pins are buttons named with the count: “2 comments on this line”.
- The dock is a dialog on phones and a complementary region on desktop; new replies are announced politely.
No presence bar at all when you are alone; “Dev Rao — in the screenplay” when Dev arrives.
“You’re the only one here” with an empty avatar ring, all day.
A conflict banner with Load the newer version and Keep mine, both safe.
The last device to save wins, and the co-writer’s afternoon is gone.
Demo
Should the reel be on the desk already when Mira comes in?
Breakdown: the reel needs a prop number.
<div class="kw-card" style="width:100%;max-width:420px;display:grid;gap:12px">
<div style="display:flex;justify-content:space-between;align-items:center"><strong>Comments</strong><div class="kw-segment" role="group" aria-label="Which comments to show"><button type="button" aria-pressed="true">Open</button><button type="button" aria-pressed="false">Resolved</button></div></div>
<div style="display:grid;gap:6px;border-top:1px solid var(--k-line);padding-top:10px"><span style="display:flex;gap:8px;align-items:center"><span class="kw-avatar" style="--kw-peer:var(--k-brand-mango)">DR</span><strong>Dev Rao</strong><span class="kw-row__meta">On this screen</span></span><p style="margin:0">Should the reel be on the desk already when Mira comes in?</p><span style="display:flex;gap:8px"><button class="kw-text-button" type="button">Reply</button><button class="kw-text-button" type="button">Resolve</button></span></div>
<div style="display:grid;gap:6px;border-top:1px solid var(--k-line);padding-top:10px"><span style="display:flex;gap:8px;align-items:center"><span class="kw-avatar" style="--kw-peer:var(--k-brand-aqua)">AK</span><strong>Asha Kumar</strong><span class="kw-row__meta">On another view</span></span><p style="margin:0">Breakdown: the reel needs a prop number.</p></div>
<label class="kw-field"><span class="kw-visually-hidden">Write a comment</span><textarea class="kw-textarea" placeholder="Write a comment"></textarea></label>
<span style="display:flex;justify-content:flex-end"><button class="kw-button kw-button--primary" type="button">Send comment</button></span>
</div>
Related
Avatar, Presence cursor, Comment pin, Sharing and roles, Saving and sync, Notifications.
AI readiness test
Task. Add live presence to the Schedule’s stripboard.
Give the agent. This page, Review and quality (free tier), components/presence/*.
Constraint. Reuse the project’s presence room.
A reliable answer
- Reuses the shared presence room with module “schedule”, no new listener
- Shows marks only when others are here
- Broadcasts pointers only from editors, as fractions of the board
- A strip being dragged by someone else shows their colour and name, and two moves to the same strip keep both until one is chosen
- No read receipts or activity feed