Checkpoint treePro
Forked checkpoints as an indented tree: every rewind opens a fork under the checkpoint it came from, folds to a count, and the path to the head stays solid.
oxyn add checkpoint-tree- Read the brief
- Built the pricing table
- Switched to Stripe ElementsFork
- Wiring the webhooksHead
- Added the Stripe checkout
- Tests failing – 4 of 12Failed
The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.
Rendered from Rust at build time · goes live when visible
When to use
- The agent just broke something three turns ago, or the user wants to try a different approach from an earlier point.
- They want to find the right moment, see what it looked like, and go back — choosing whether to bring back the files, the conversation, both, or to branch off — without fear of losing work they want to keep.
When not to use
- Review an agent's change set: use Diff viewer instead.
- Send, stop, queue and steer in one control, in twelve styles: use Send control instead.
- Messages typed while the agent works wait above the composer: use Queue stack instead.
Installation
Checkpoint tree is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.
oxyn add checkpoint-treeUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Open
Two lines, the fork open.
- Read the brief
- Built the pricing table
- Switched to Stripe ElementsFork
- Wiring the webhooksHead
- Added the Stripe checkout
- Tests failing – 4 of 12Failed
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Three
Three attempts from one checkpoint.
- Read the brief
- Built the pricing table
- Switched to Stripe ElementsFork
- Wiring the webhooks
- Tried a hosted checkout pageForkStoppedHead
- Added the Stripe checkout
- Tests failing – 4 of 12Failed
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Folded
Forks folded to a count.
- Read the brief
- Built the pricing table
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
CheckpointTree
| Prop | Type | Default | Description |
|---|---|---|---|
checkpointsrequired | Vec<Checkpoint> | — | Checkpoints in the order taken. |
head | Option<String> | Default::default() | Where the agent stands (default: last). |
times | Vec<String> | Default::default() | Time labels, same order (absolute ISO); default the run time. |
folded | Vec<String> | Default::default() | Ids whose forks start folded. |
title | String | "Branches" | Heading. |
on_rewind | EventHandler<String> | — | Rewind pressed (button, Enter or Space): the checkpoint id. |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| ↑or↓ · HomeorEnd | Move between visible checkpoints |
| ←or→ | Fold or unfold the forks of the focused checkpoint |
| EnterorSpace | Rewind to the focused checkpoint |
Accessibility
- role=tree with treeitems carrying aria-level and aria-expanded; one tab stop.
- Each item says its title, status, ISO time, whether it is a fork, and current or left behind.
- Fold buttons are pointer shortcuts; ← and → do the same from the keyboard.
From the spec
- Marker role: a
buttonwitharia-haspopup="menu"; accessible name "Checkpoint, auto, 3:42 PM, before 'now add rate limiting', 3 files changed, available". Chat-only: "…, no file changes". Current: "…, you are here". - Menu items are named by scope with counts ("Restore 3 files", "Rewind 2 turns", "Restore 3 files and rewind 2 turns", "Fork from here"); disabled items keep focusability with
aria-disabledand the reason as description. - Side list:
listboxgrouped by day (groupwith the date as label); scrubber is asliderwhose value text names the checkpoint (as run-replay.md §8). - Live region (polite): "Restored 3 files to 3:42 PM. Undo available for 10 seconds." · "Restore undone." · "Opened fork from 3:42 PM." Failures assertive once. No announcements on hover.
- Keyboard: Tab to marker; Enter menu; R / C / B / F / P inside menu; Esc closes; in the side list ↑/↓ move, Enter preview, Shift+Enter open menu; ⌘S save manual checkpoint (side list and timeline focus only); ⌘Z undo restore while the toast is visible and focus is not in an editable field; F6 cycles to the toast region.
- Focus order after restore: focus returns to the marker (now "You are here") unless the user was in the sheet, in which case it moves to the toast's Undo button; after the toast closes, focus goes back to the marker.
- Contrast: hairline ≥ 3:1 against the transcript background on focus/hover (rest may be 2:1 as decoration since the diamond and text carry it); "You are here" accent text ≥ 4.5:1.
- Undo is never toast-only: the
RestorePointstays in the side list and menu ("Undo last restore"). - Reduced motion: §5 last row.
Motion & interaction
- Marker enter. The hairline draws from the start edge to the end over 240 ms (
ease.out) as the turn begins; the diamond scales 0 → 1 (spring.snap) at the start. A marker never pushes content: its 24 px row height is reserved when the turn row is created. - Hover reveal. After
delay.marker.hover(150 ms) the actions fade in with x −4 → 0 (dur.marker.reveal, 120 ms); leaving hides them after a 300 ms grace so the pointer can travel to them. Hover over a user message also reveals a ↶ on that message (thehover-revertplacement). - Preview popover. 200 ms hover delay, 140 ms fade; the file list rows show counts with no roll (static); clicking a file opens the diff viewer filtered to that file at the checkpoint → head range.
- Menu. Opens with
dur.sheet.enter; items carry letter hints; disabled items show their reason as secondary text, not a tooltip only. - Scope switch inside the sheet. Switching Files / Chat / Both crossfades the impact summary (160 ms) and rolls the confirm button counts ("Restore 3 files" → "Restore 3 files and rewind 2 turns"); the button keeps its width reserved for the longest label (one cell, Arc idea, note 12).
- Restore — files. Each later file-edit chip touched by the restore morphs to
Reverted(↶ rotates −90° → 0, 160 ms) in transcript order withstagger.bulk(30 ms, cap 8); the "Restoring n of m" count rolls withdur.digit.roll. - Restore — chat. Turns after the marker fold upward into a single "2 rewound turns · Bring back" row (
dur.rewind.fold, 280 ms, stagger 20 ms cap 6), then the rewound user prompt travels from its bubble into the composer (dur.travel, ≤ 260 ms) with the caret at its end. If the composer has a draft, the prompt is not moved; a chip "Rewound prompt · Insert" appears above the composer instead (proposed). - Restored. The marker label crossfades to "You are here" and an accent wash fades over 600 ms.
- Undo toast. Rises 8 px from the composer edge (200 ms
ease.out); a 1 px hairline depletes overundo.window(10 s, proposed); hover or focus pauses it and it resumes with at least 3 s left. Undo plays the same choreography backwards (chips un-revert, fold re-expands). - Fork. The marker duplicates: a ghost diamond slides 12 px toward the end edge and fades (200 ms) while the toast appears; if the host opens the fork in a new tab, the tab strip owns that animation.
- Failure. Toast in danger tone, glyph nudge 2 × 3 px (tools.md error nudge); text never shakes.
- Auto vs manual.
Automarkers are hairline-only at rest;Manualmarkers always show their name and a flag; saving a manual checkpoint (⌘S in the timeline) stamps the diamond with a 160 ms scale pulse 1 → 1.2 → 1.
Timing
| Transition | Duration | Delay | Easing / spring | Stagger | Frame rate |
|---|---|---|---|---|---|
| Marker hairline draw | 240 ms | at turn start | ease.out | — | 60 Hz |
| Diamond enter | 160 ms, scale 0 → 1 | 0 | spring.snap | — | 60 Hz |
| Actions reveal / hide | 120 ms / 120 ms | 150 ms / 300 ms grace | ease.out / ease.in | — | 60 Hz |
| Preview popover | 140 ms | 200 ms | ease.out | — | 60 Hz |
| Menu / sheet enter | 220 ms, y +12 → 0 | 0 | spring.snap | — | 60 Hz |
| Menu / sheet exit | 160 ms | 0 | ease.in | — | 60 Hz |
| Impact skeleton | — | 150 ms | — | — | 30 Hz shimmer (skeletons.md) |
| Scope switch | 160 ms crossfade + 280 ms count roll | 0 | ease.in-out / ease.out | 30 ms digits | 60 Hz |
| Chip revert cascade | 160 ms each | 0 | spring.snap | 30 ms, cap 8 | 60 Hz |
| Rewind fold | 280 ms | after files settle | ease.in-out | 20 ms, cap 6 | 60 Hz |
| Prompt → composer | ≤ 260 ms | after fold | ease.in-out | — | 60 Hz |
| "You are here" wash | 600 ms | 0 | ease.out | — | 30 Hz |
| Undo toast enter / exit | 200 ms / 160 ms | 0 | ease.out / ease.in | — | 60 Hz |
| Undo hairline | 10 s (paused on hover/focus) | 0 | linear | — | 10 Hz |
| Manual save pulse | 160 ms | 0 | spring.snap | — | 60 Hz |
| Fork ghost | 200 ms, x +12, fade | 0 | ease.out | — | 60 Hz |
| Reduced motion | hairline and diamond appear instantly; reveals, popovers, sheets and toasts use 80 ms opacity crossfades with no offsets; no cascade (all chips swap together); rewind fold is instant with an 80 ms crossfade; prompt appears in the composer without travel; no wash (static 2 px accent outline for 2 s); undo countdown is text "Undo · 9 s" updated at 1 Hz | — | linear | none | event-driven |
Responsive behaviour
- Each fork indents 16 px; titles truncate before badges.
- Under 460 px the line counts give way.
Edge cases (spec)
- Restore while the agent runs. Restore actions are
Blocked; "Stop and restore" stops the run (send-control Stop semantics), waits forCancelled, then opens the impact sheet. Preview and Fork stay available because they change nothing in this thread. - User has a draft in the composer when rewinding chat: the rewound prompt goes to a chip above the composer, never overwrites the draft.
- Very fast agents writing many turns quickly: markers still enter one per turn; a burst of markers inside 1 s merges visually into one hairline with a count badge "3 checkpoints" until hovered.
- Hundreds of checkpoints. Inline markers remain one per turn; side list virtualises and groups by day; scrubber aggregates diamonds closer than 4 px into a stacked diamond with a count.
- Same file restored twice (restore, then restore an older one): each creates its own
RestorePoint; undo always targets the most recent restore only; older ones are reachable in the list. - Undo after further edits. If files changed after the restore (user or agent), Undo opens the impact sheet instead of applying directly ("2 files changed since the restore").
- Partially captured checkpoints. Preview lists skipped files with the reason; the confirm sheet says "1 file can't be restored (too large)".
- Checkpoint on a different git branch than the current one: preview shows "Captured on
feature/auth, you're onmain"; restore writes files into the current branch's working tree and the sheet says so (no checkout happens, checkpoints-git.md §2.1 rule 3). - Fork without worktree support. Fork starts on current files with a note "Files in the fork start as they are now".
- Long prompt excerpts. One line, 60 ch, ellipsis; full text in the preview and accessible name.
- RTL. Marker hairline and side list mirror; times, paths and counts stay LTR; the scrubber's time axis keeps left → right (run-replay.md §7 convention).
- Tiny sizes (16–20 px). Marker is the diamond only; Enter / tap opens the menu; preview disabled.
- Dense IDE panels. 20 px marker rows, no labels at rest, preview opens on Enter instead of hover.
- Touch. 44 px hit area on markers; long-press for preview; menu becomes a bottom sheet; undo toast sits above the keyboard.
- Slow networks / remote store. Impact skeleton after 150 ms; if impact takes > 5 s, the sheet offers "Restore without summary" with a generic warning (rollback-impact.md
ImpactUnavailable). - Expired mid-flow. If retention removes files between Confirming and Restoring, the restore fails with "No files were restored · this checkpoint has expired" and nothing changes.
Notes for AI
- Import
CheckpointTreefromoxyn_dioxusand includeHITL_CSSplus the token stylesheet once. - A GPUI version exists:
CheckpointsViewinoxyn_gpui. - Props to set first:
checkpoints. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.