Presence cursors
Agents in a document like teammates in a multiplayer editor – live pointers with names and costs, suggestions typed letter by letter, an image they resize, code they fix and comment pins beside the page.
oxyn add presence-cursorsAtlas 4 – launch outline
Teams spend close to 30% of each week chasing updates. Atlas gathers that work into one morning summary, so nobody has to compile it.
The hero shot is the summary itself: a single quiet page a manager opens first thing. Brief, up to date and drawn from real work, so the week begins without a check-in call.
Timeline
const timeline = {
beta: "Mar 2",
general: "mid-March",
};Launch week: one blog post, a walkthrough clip and a note to the beta list.
In the release
- A morning summary for every team, drawn from the work itself
- Reminders when a thread has gone silent for days
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "doc".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}Rendered from Rust at build time · goes live when visible
When to use
- Agents working in a document like teammates in a multiplayer editor: live pointers with a flag (name, cost, what it is doing), selected passages, suggestions typed letter by letter, an image that loads and gets resized, code fixes and comment pins beside the page.
- Every change stays a suggestion until you accept it.
When not to use
- An agent asks before it acts: use Approval Card instead.
- Several open requests in one card: use Approval pager instead.
- An agent's question in its own card above the composer: use Decision Card instead.
Installation
Presence cursors is free and MIT. The oxyn CLI copies its code, and the components it needs, into src/oxyn/ of your Dioxus or GPUI project, so it is yours to change.
cargo install --git https://github.com/ismailqureshi72/Oxyn oxyn-cli
oxyn init
oxyn add presence-cursorsuse crate::oxyn::{PresenceCursors, STATUS_INDICATOR_CSS};Rather depend on the crate? cargo add oxyn-dioxus oxyn-core --git https://github.com/ismailqureshi72/Oxyn, then use oxyn_dioxus::{PresenceCursors, STATUS_INDICATOR_CSS};
Usage
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "doc".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}Examples
Default
Four agents arrive in the doc, read, select, type suggestions letter by letter, resize the hero image, fix the code and leave comment pins; the costs and the count in the header follow along.
Atlas 4 – launch outline
Teams spend close to 30% of each week chasing updates. Atlas gathers that work into one morning summary, so nobody has to compile it.
The hero shot is the summary itself: a single quiet page a manager opens first thing. Brief, up to date and drawn from real work, so the week begins without a check-in call.
Timeline
const timeline = {
beta: "Mar 2",
general: "mid-March",
};Launch week: one blog post, a walkthrough clip and a note to the beta list.
In the release
- A morning summary for every team, drawn from the work itself
- Reminders when a thread has gone silent for days
Code
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "doc".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}Writing
Frozen while the Researcher writes its comment: the open window beside the paragraph, the Writer's rewrite just typed.
Atlas 4 – launch outlineschedul
The hero shot is the summary itself: a single quiet page a manager opens first thing. Brief, up to date and drawn from real work, so the week begins without a check-in call.
Timeline
const timeline = {
beta: "Mar 2",
general: "mid-March",
};Launch week: one blog post, a walkthrough clip and a note to the beta list.
In the release
- A morning summary for every team, drawn from the work itself
- Reminders when a thread has gone silent for days
Code
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "doc".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}Suggestion window
A suggestion's window open: who suggests it, why, Reject and Accept.
Atlas 4 – launch outlinescheduleWritersuggests a rewriteIt has dates in it now – it reads as a schedule
The hero shot is the summary itself: a single quiet page a manager opens first thing. Brief, up to date and drawn from real work, so the week begins without a check-in call.
Timeline
CodernowCan beta and general use one date style? I'd write "Mar 2" for both.const timeline = {
beta: "Mar 2",
general: "mid-MarchMar 16",
};Launch week: one blog post, a walkthrough clip and a note to the beta list.
In the release
- A morning summary for every team, drawn from the work itself
- Reminders when a thread has gone silent for days
Code
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "doc".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}Following
Following the Researcher: its face filled, every other pointer and selection faded back.
Atlas 4 – launch outline
Teams spend close to 30% of each week chasing updates. Atlas gathers that work into one morning summary, so nobody has to compile it.
The hero shot is the summary itself: a single quiet page a manager opens first thing. Brief, up to date and drawn from real work, so the week begins without a check-in call.
Timeline
const timeline = {
beta: "Mar 2",
general: "mid-March",
};Launch week: one blog post, a walkthrough clip and a note to the beta list.
In the release
- A morning summary for every team, drawn from the work itself
- Reminders when a thread has gone silent for days
Code
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "doc".into(),
following: "researcher".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}Table
Tables and tabs: the Table tab – status pills, an owner and a date being changed, a task row typed in.
Atlas 4 – launch checklist
| Task | Owner | Due | Status |
|---|---|---|---|
| Draft the blog post | Writer | Mar 2 | Doing |
| Film the walkthrough | Designer | Mar 4 | To do |
| Mail the beta list | Ops | Mar 11 | To do |
| Open office hours | — | Mar 13 | Idea |
| Add row | |||
Code
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "table".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}Classic
Classic style: the page as raised paper on a grey header band.
Atlas 4 – launch outlineschedule
The hero shot is the summary itself: a single quiet page a manager opens first thing. Brief, up to date and drawn from real work, so the week begins without a check-in call.
Timeline
CodernowCan beta and general use one date style? I'd write "Mar 2" for both.const timeline = {
beta: "Mar 2",
general: "mid-MarchMar 16",
};Launch week: one blog post, a walkthrough clip and a note to the beta list.
In the release
- A morning summary for every team, drawn from the work itself
- Reminders when a thread has gone silent for days
Code
rsx! {
PresenceCursors {
scene: Some(scene()),
tabs: tabs(),
tab: "doc".into(),
height: 470.0,
now: clock.now(),
on_accept: move |s| accept(s),
on_reject: move |s| reject(s),
on_accept_all: move |_| accept_all(),
on_resolve: move |c| resolve(c),
}
}API reference
PresenceCursors
| Prop | Type | Default | Description |
|---|---|---|---|
scene | Option<CursorScene> | Default::default() | Your own document (the demo's when `None`); switch it with `tab` / `on_tab`. |
tabs | Vec<(String, String)> | Default::default() | Tabs above the page: (id, label) – the demo's Doc / Table when empty and `scene` is `None`. |
tab | String | "doc" | The open tab. |
at | Option<u64> | Default::default() | Freeze the demo at this many ms into a pass (a settled state). |
following | String | Default::default() | The agent followed at the start (id). |
open | String | Default::default() | A suggestion whose window is open at the start (id). |
height | f32 | 470.0 | A fixed page height in px – the rest of the document fades out (0 = all of it). |
nowrequired | ClockMs | — | The clock. |
style | String | Default::default() | `clean`, `classic`, or empty to follow `data-cstyle`. |
on_accept | EventHandler<DocSuggestion> | — | A suggestion accepted from its window. |
on_reject | EventHandler<DocSuggestion> | — | A suggestion rejected from its window. |
on_accept_all | EventHandler<()> | — | "Accept all". |
on_following | EventHandler<String> | — | The agent followed (id), or empty when you stop following. |
on_resolve | EventHandler<DocComment> | — | The check in a comment's window. |
on_reply | EventHandler<(DocComment, String)> | — | A reply sent from a comment's window (Enter). |
on_tab | EventHandler<String> | — | Another tab was chosen (its id). |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Tab | The tabs, the faces in the header, then from suggestion to suggestion – a focused suggestion opens its window |
| EnterorSpace | On a face: follow that agent, or stop following |
| Esc | Dismisses an open suggestion |
Accessibility
- The text is real text in headings, paragraphs, a list and a table – pointers, carets and selections are decoration, hidden from screen readers.
- Every suggestion is focusable and labelled – "Researcher suggests removing: close to 30%" – and its window is a dialog with Reject and Accept.
- The faces are toggle buttons (aria-pressed) named after the agent and what it does; a followed face fills with its tint.
- A polite live region reads what agents do – "Coder is writing a comment", new suggestions with their note.
Responsive behaviour
- Pointers are anchored on their characters, so they stay on their letters while the text wraps at any width, font size or zoom.
- Flags sit to the bottom right of their pointer; near the right edge they are cut off rather than moved.
- Below 520 px the page gets tighter margins and the suggestion count gives way to the faces.
Edge cases (spec)
Positions come from the text itself, so any width, font size or zoom works. Flags sit to the bottom right of their pointer and are cut off at the right edge rather than moved. Below 520 px the page gets tighter margins and the suggestion count gives way to the faces. Dark mode via data-oxyn-theme.
Notes for AI
- Import
PresenceCursorsfromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
PresenceCursorsElinoxyn_gpui. - Props to set first:
now. - It reads a clock (
now) for live timers; pass one clock for the whole page rather than one per component. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.