Documentation menu
Features

Capture & Library

Capture links, notes, quotes, and files without setup, then browse every saved knowledge type in one filtered Library.

Capture is available from every authenticated screen. Library is where captured and derived knowledge becomes browsable without forcing everything into folders first.

Capture Without Prerequisites

Choose Capture, then select Link, Note, Quote, or File. A capture does not require a tag, folder, stage, classification, embedding, or model provider.

  • Link saves a page through the normal bookmark pipeline.
  • Note creates a standalone note.
  • Quote preserves selected evidence with its source URL and an optional interpretation.
  • File imports supported material as a searchable note.

The browser extension, PWA share target, CLI, and local automation routes use the same owned knowledge store. Link and quote captures can queue in the browser while offline.

Bookmark readers retain capture-attempt history, source evidence and available preserved copies, locally hosted article images, and your scroll progress. Direct HTTP capture remains available on every installation. On fresh supported Linux installs, the installer enables an isolated native capture runtime by default; choose the core-only option when you do not want it. See Preservation and Sharing.

Browse the Unified Library

Library shows bookmarks, notes, daily notes, annotations, and knowledge objects by default. Generated entities and concepts remain available through the separate Derived view and in Graph, rather than competing with material you saved or wrote. Use filters for type, topic, source, workflow stage, date, and connection state. Results use cursor pagination so large collections remain practical.

Inbox remains available as a Library context for stage, importance, next-action, bulk, and keyboard triage. Existing /dashboard and /inbox links continue to open the corresponding Library context.

What Arivu Derives

Arivu can locally extract text, concepts, entities, and deterministic summaries. Generated knowledge is grounded in selected text or source evidence. When evidence is incomplete, Arivu may intentionally leave a generated field empty rather than fill the gap. A complete rendered capture can improve weak direct extraction, but a challenge page or failed attempt cannot replace stronger evidence or the last good reader.

Optional providers can add richer summaries and embeddings. Safe parts of a structured summary can remain available when another field fails validation, and provider outages can fall back to publisher descriptions and evidence-derived material. Missing embeddings only remove semantic-similarity relationships; saved content, text search, explicit links, other eligible graph relationships, and Insights continue.

Next Steps