Skip to content
Back

Cited AnswerPro

An AI answer wired to its sources – point at a citation to light up its sentence and source, click to unfold the quoted passage with the matching words marked.

oxyn add cited-answer
BCP3 sources · 14 pages read

The quickest win is caching dependencies between runs: the runner restores compiled crates instead of building them again. On large workspaces that can take a cold build from twelve minutes to about three. The cache only hits while the lockfile stays the same, so pin the toolchain and land dependency bumps in their own commits.

Then split the test suite across parallel jobs: each shard finishes in about four minutes, which halved the wait for most pull requests in one team's setup. Keep the slow end-to-end tests for the main branch, so reviews get a quick first signal.

Cache Notes · cited in 1 sentence
The code is part of Oxyn Pro

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.

Get Pro

Rendered from Rust at build time · goes live when visible

When to use

  • Checking which sentence comes from which source: point at a citation to light up its sentence, click to read the passage it rests on.

When not to use

  • Prompt composer with model picker, voice input, app connections and approval request: use Chat Composer instead.
  • The model menu of an AI chat: use Model Picker instead.
  • The prompt box for an agent, in six layouts: use Composer instead.

Installation

Cited Answer 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.

Terminal
oxyn add cited-answer

Usage

Dioxus · rust
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Examples

Default

The second source is lit – its sentence tinted, the rest faded. Point at a marker or a chip to light another.

BCP3 sources · 14 pages read

The quickest win is caching dependencies between runs: the runner restores compiled crates instead of building them again. On large workspaces that can take a cold build from twelve minutes to about three. The cache only hits while the lockfile stays the same, so pin the toolchain and land dependency bumps in their own commits.

Then split the test suite across parallel jobs: each shard finishes in about four minutes, which halved the wait for most pull requests in one team's setup. Keep the slow end-to-end tests for the main branch, so reviews get a quick first signal.

Cache Notes · cited in 1 sentence
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Quote

Quote unfolded: the passage with the matching words marked, Open source and Copy quote.

BCP3 sources · 14 pages read

The quickest win is caching dependencies between runs: the runner restores compiled crates instead of building them again. On large workspaces that can take a cold build from twelve minutes to about three. The cache only hits while the lockfile stays the same, so pin the toolchain and land dependency bumps in their own commits.

Then split the test suite across parallel jobs: each shard finishes in about four minutes, which halved the wait for most pull requests in one team's setup. Keep the slow end-to-end tests for the main branch, so reviews get a quick first signal.

Ccachenotes.dev · Jul 9, 20262
Keeping build caches warm
Pin the toolchain and the lockfile, and land dependency bumps on their own. One changed version early in the graph invalidates every crate built after it.
Open source
Cache Notes · cited in 1 sentence
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

None lit

Nothing lit: every sentence at full strength and "5 of 6 sentences backed by a source".

BCP3 sources · 14 pages read

The quickest win is caching dependencies between runs: the runner restores compiled crates instead of building them again. On large workspaces that can take a cold build from twelve minutes to about three. The cache only hits while the lockfile stays the same, so pin the toolchain and land dependency bumps in their own commits.

Then split the test suite across parallel jobs: each shard finishes in about four minutes, which halved the wait for most pull requests in one team's setup. Keep the slow end-to-end tests for the main branch, so reviews get a quick first signal.

5 of 6 sentences backed by a source
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Classic

Classic style: the text on a white card over a grey tray, the quote above the chips.

BCP3 sources · 14 pages read

The quickest win is caching dependencies between runs: the runner restores compiled crates instead of building them again. On large workspaces that can take a cold build from twelve minutes to about three. The cache only hits while the lockfile stays the same, so pin the toolchain and land dependency bumps in their own commits.

Then split the test suite across parallel jobs: each shard finishes in about four minutes, which halved the wait for most pull requests in one team's setup. Keep the slow end-to-end tests for the main branch, so reviews get a quick first signal.

Ccachenotes.dev · Jul 9, 20262
Keeping build caches warm
Pin the toolchain and the lockfile, and land dependency bumps on their own. One changed version early in the graph invalidates every crate built after it.
Open source
Cache Notes · cited in 1 sentence
Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

API reference

CitedAnswerCard

PropTypeDefaultDescription
headerStringDefault::default()Header line (the demo when empty).
textStringDefault::default()Markup: `[n]` after a sentence cites source n (see `parse_cited`).
sourcesVec<CitedSource>Default::default()Sources (the demo when empty).
litOption<usize>Default::default()—
openboolDefault::default()Open that source's quote at the start.
actionString"Follow up"Footer button label.
styleStringDefault::default()`clean`, `classic`, or empty to follow `data-cstyle`.
on_actionEventHandler<(String, String)>—(`open` | `close` | `copy` | `follow-up`, source name).

Read from the Rust signature and doc comments.

Keyboard interactions

KeyAction
TabMarkers in reading order, then the source chips and Follow up
EnterorSpaceUnfold or fold that source's quote

Accessibility

  • Markers and chips are buttons named "Source 2: Cache Notes – Keeping build caches warm", aria-expanded and aria-controls on the quote.
  • The quote is a region named "Quote from <publication>"; the last row is a polite live region ("Quote copied").
  • The lit sentence changes weight as well as colour, so it reads without colour.

Responsive behaviour

  • Fills its container up to 460 px and works from 300 px; below 400 px it tightens, below 360 px the number tags drop, below 280 px Copy quote keeps only its icon.
Edge cases (spec)

Up to 460 px, from 300 px: tighter under 400, index tags drop under 360, Copy quote keeps only its icon under 280; chips stay on one line.

Notes for AI

  • Import CitedAnswerCard from oxyn_dioxus and include STATUS_INDICATOR_CSS plus the token stylesheet once.
  • A GPUI version exists: CitedAnswerEl in oxyn_gpui.
  • Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.

Guides

Oxyn · 74 free components · 264 Pro components · 96 screens · 20 blocks · Dioxus and GPUI