TL;DR togglePro
Read a post at three depths (whole text, a summary, or bullet points) with a length setting; the shorter views stream in where the text was, and every bullet links back to its source paragraph.
oxyn add tldr-toggleWhy our agents now ask before they spend
Corvel engineering blog · 6 min readReading the article
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
- Read an article at the depth you want: Full, Summary or Key points, with a length control.
When not to use
- Replays a multi-agent run on one clock: use Agent timeline instead.
- One model at a glance: use Model card instead.
- A small automation on a single rail: use AI workflow instead.
Installation
TL;DR toggle 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 tldr-toggleUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Summary
A medium summary streams in.
Why our agents now ask before they spend
Corvel engineering blog · 6 min readReading the article
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Key points
Five key points that jump to their paragraph.
Why our agents now ask before they spend
Corvel engineering blog · 6 min readFinding the key points
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Full
The full article.
Why our agents now ask before they spend
Corvel engineering blog · 6 min readLast quarter our agents ran about forty thousand tasks for customers, and a small share of them did something nobody asked for: they bought credits, renewed a domain or upgraded a plan because a tool made it easy.
None of these were bugs in the usual sense. The agent read the goal, found a tool that moved it forward and used it. The problem was that spending money is a different kind of step from reading a file.
We now sort every tool into three tiers. Reading is free to run, writing asks once per session, and anything that spends money or cannot be undone asks every time, with the amount shown in the request.
Approvals used to feel slow, so we made them cheap. The request names the tool, the amount and what happens next, one key approves it, and the agent keeps working on other steps while it waits.
Since the change, unwanted purchases dropped to zero and the median task got four seconds slower. Customers told us that trade was easy: they would rather wait a moment than explain a surprise charge.
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Failed
Couldn't summarize, with Try again.
Why our agents now ask before they spend
Corvel engineering blog · 6 min readReading the article
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
TldrToggle
| Prop | Type | Default | Description |
|---|---|---|---|
nowrequired | ClockMs | — | Host clock. |
mode | usize | 1 | Starting view (0 full, 1 summary, 2 key points). |
length | usize | 1 | Starting length (0 short, 1 medium, 2 long). |
fail | bool | Default::default() | The first summary fails. |
saved | bool | true | Show the words-saved readout (Oxyn extra). |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Tab | The view switch, the length control, key point links |
| Arrows · HomeorEnd | Move in either group |
| EnterorSpace | Jump to a key point's paragraph |
Accessibility
- View and length each take one tab stop; arrows move inside them.
- The body has aria-busy while summarizing; the jumped-to paragraph is highlighted and announced.
- Errors use role alert with Try again.
From the spec
Mode and length are radio groups with arrow keys; key points are buttons naming the paragraph. Every action returns the line the polite live region announces. The focus outline shows only for keyboard focus.
Motion & interaction
Switching streams the summary in place; a key point jumps to Full and highlights its paragraph briefly.
Timing
Everything on screen is derived from the host clock now (no timers in the component), so playback, tests and the GPUI view agree.
| Transition | Duration | Easing |
|---|---|---|
| Think | 700 ms | — |
| Paragraph highlight | 1600 ms (JUMP_MS) | ease-out fade |
Reduced motion: streamed text and moves appear at their end state; progress still advances, without travel animation.
Responsive behaviour
- The body follows its content's height; the controls wrap under 480 px.
- Key points wrap; their jump buttons stay at the end of the line.
Edge cases (spec)
Segmented control stays one row down to 320 px. Saved-time readout updates per length. Checked at 1440, 768 and 390 px in light and dark with no text overlap. Chrome is monochrome grey; colour is semantic only (success, warning, danger, info) plus the providers' coloured brand marks.
Notes for AI
- Import
TldrTogglefromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
AiKitViewinoxyn_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.