Selection-aware capture
Capture the whole article or just the passage you highlighted. Layout, ads, and navigation are stripped out.
TinyWorks Research turns any page you read into a structured research card — summary, key points, entities, and citation — without leaving the tab.
No account required · Works offline after capture
Understanding React Server Components
Boilerplate, navigation, and ads are discarded before the model ever sees the page.
Research card
RSC moves rendering and data access to the server, cutting client JavaScript without giving up composition.
Capabilities
Every feature exists to shorten the path from source material to usable knowledge.
Capture the whole article or just the passage you highlighted. Layout, ads, and navigation are stripped out.
Every card gets a one-line thesis, key points, and open questions — never a wall of paraphrase.
People, papers, libraries, and metrics are pulled out and linked across your library.
Copy or sync to Obsidian, Notion, and plain files with front matter and source URLs intact.
Search what you meant, not what you typed. Results resolve to the exact paragraph you saveped.
Cards live on your machine by default. Sync is opt-in, per workspace, and end-to-end encrypted.
Workflow
Designed to disappear into your reading, not interrupt it.
Press the shortcut or click the toolbar icon. Research reads the article in place — no new tab, no copy-paste.
The card appears in a side panel with the summary, points, and tags. Edit anything before it is stored.
Save to your library, or push Markdown straight into Obsidian, Notion, or a file in your repo.
Output
Cards are plain Markdown with front matter. Read them in any editor, diff them in Git, and keep them long after you stop using Research.
---
title: Understanding React Server Components
source: https://react.dev/blog/server-components
saved: 2026-08-01T09:24:00Z
tags: [react-19, rsc, streaming]
---
## Thesis
RSC moves rendering and data access to the server,
cutting client JavaScript without losing composition.
## Key points
- Server Components stream HTML to the client.
- Component code never ships to the browser.
- Data fetching lives beside the component.
## Open questions
- How does caching interact with streaming boundaries?FAQ
Straight answers about scope, privacy, and portability.
Add it to Chrome, read something worth keeping, and press the shortcut. That is the entire onboarding.
Free for unlimited local research cards · Pro from $6/mo