Trade-offs · 2026-11 · 1 min read

The clipper captures; the workbench thinks

A browser extension is the wrong place to put intelligence. The hard part of designing one is where the line sits between capture and thinking.

Illustration for: The clipper captures; the workbench thinks

Textrix will have two entry points into one knowledge base: the desktop workbench and a browser extension. The hard part of designing the second one is not features — it is where the line sits between capture and thinking.

Capture should be plain

The clipper saves a minimal snapshot of the page as Markdown and hands it to your local knowledge base. No forced account, no cloud clipboard standing in the middle, no proprietary capture format — the file it produces is a plain Markdown file on your own disk, same as everything else in the vault.

Thinking stays in the workbench

Cleaning up, linking, summarising, filing — all of that happens in the workbench, where the single source of truth lives and where AI changes pass a checkpoint before reaching disk. Putting processing inside the extension would split the source of truth and route your pages through a server; keeping it local preserves both guarantees.

The trade in one sentence

The extension gives up cleverness so the knowledge base keeps exactly one truth on exactly one machine. A clipper you can trust is worth more than a clipper that tries to think for you.

← All posts

Keep reading

Two more articles from the same trade-off series.

Still in development

Not yet available for download. Join the waitlist and you will be invited first when it opens.

Email-collection mode: submitting opens a pre-filled message in your mail client.