The pantry

Everything in a library sits on a shelf: a name, a line on what it is for, and notes of its own. Documents list in natural order, and each shelf has its own slice of the index.

The chapter of your book: a title, an overview written like a chapter’s opening, and numbered sections. Each document keeps a stable number, No. 12, and one row of actions: Star, Focus, Share, Move and Edit.

A full page of its own, numbered in order, with a title, a body, its sources and one of ten types, from Evidence to Decision. Mark the ones that matter as Key.

Your assistant does the heavy lifting; the editor is where the work becomes yours. Write straight into the page, type / for an element, and drag sections into order. It saves a second after you stop typing, and Revisions keep every earlier version.

53 kinds of rich block inside a section: timelines, tables, charts, diagrams, flashcards, slide shows and working widgets that run in a sealed frame. Your assistant writes them and know.sh draws them in the book’s own ink, light or dark. Turn them on in Account → Elements; with them off, each reads as its words.

A back-of-book index built as you write: the names, places and terms that recur across your sections, each with the numbers where they appear. Highlighted sections are set in bold.

Ask your assistant for a quiz on a document: five to ten questions, each citing the sections it came from. Take it on the web or the iOS app, and it comes back under Revisit when it is due.

Select a passage and Highlight it. The highlight stays attached as the text around it changes, and its section’s number turns bold in the index.

Notes in the margin beside the passage they are about, with replies one level deep. They are yours and your assistant’s; readers of a public link never see them.

When your assistant spots something you did not ask about, it leaves a proposed note with Accept and Dismiss. Nothing in your text changes until you say so.

Every change to a document or section, marked as yours or an assistant’s, with Restore. It is what makes it safe to let an assistant loose.

A read-only link to one document, with an optional password and expiry, and any section left out. Readers see the text, never your notes or highlights.

Look up (⌘K, or /) searches every word as you type: index terms, documents, sections, highlights and shelves.

Star the documents you keep coming back to. Put one in Focus for a week, and Revisit tells you when the week is up.

The library laid out like the front of a book: by shelf, by month filed, or recent, starred and shared.

Turn research into a plan: operations with statuses and dependencies, laid out as a graph. An assistant with the planning permissions, such as Claude Code with the plugin, can lay one out for you.

Bring the AI you already use. Claude, ChatGPT or a local model connects through the know.sh MCP server and can search, read, write and reorganise your library, with every change kept in Revisions. You sign in once; there is no key to copy. The support page has setup for each.

Claude and ChatGPT can run a prompt on a schedule: this week’s injury news, the papers published on your topic. When the result arrives, reply file this in know.sh and your assistant adds it, with its sources.

Link a document or section to another, and the link shows a preview on hover.

Turn it on in Account → Listening, on iPhone or the web. know.sh reads a whole document aloud, the title, the overview and then each section, in one of nine English voices by Kokoro, made on your own device: nothing you read is sent anywhere to be spoken. Kokoro downloads once, about 87 MB on iPhone. Set the speed from 0.8× to 2×, stop after each section, and on iPhone keep listening with the screen locked, skipping sections from the lock screen or your headphones. An element is named as it comes, by its kind and title.

The same library on iPhone and iPad: read, highlight, note, take quizzes and see elements drawn. In beta on TestFlight today.