Skip to content
selinayfilizpPublic

About

A reading room in one HTML file: highlights, margin notes that ask why, and Claude discussions grounded in the whole article. Local-first, bring your own key.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MyNotes

A reading room in one HTML file. Bring an article, highlight what matters (every highlight asks you why), keep notes in a real margin, and talk the piece through with Claude as you read. Your whole notebook lives in your own browser.

MyNotes

What it does

  • Bring an article by link (fetched through Jina Reader) or by pasting it in. Formatting survives the paste.
  • Highlight and say why. Highlighting opens a small "why this?" note that sits in the margin, aligned with the passage, like writing on paper.
  • Discuss with Claude while you read. Every question ships the full article plus your highlights and margin notes, so the conversation is grounded in the piece. The companion is prompted to quote the text, admit what is not in the article, and always give the strongest honest counterpoint instead of just agreeing with you.
  • Ask about any passage by selecting it and hitting Ask Claude.
  • A shelf that connects itself. Related articles link to each other automatically, and one click has Claude write out the real threads across everything you have saved.
  • Leave off anywhere. One click (or Cmd+B) drops a dated bookmark ribbon at the line you are reading; the article reopens right there, and the shelf shows when you left off.
  • Export any article's highlights, notes, and discussion as Markdown.
  • Notebook files. By default your notebook lives in the browser; in Chromium browsers (Chrome, Arc, Edge) you can move it into a real file on disk (Settings, then Notebook). A notebook file saves as you work, can sit in iCloud or Drive for free sync, opens on another machine, and you can keep several: one for research, one for fun.
  • Back up and restore any notebook as a JSON file (Settings), so nothing is ever trapped in browser state. Backups never include your API key.

Get started

Fastest: use it right now at selinayfilizp.github.io/mynotes. It is the same single file, served as-is; there is still no server-side anything, and your notebook lives in your own browser.

Or run it yourself:

  1. Download index.html (or clone this repo) and open it in a browser. That is the entire install: no build, no server, no account. A short welcome note is waiting so you can try highlighting and margin notes immediately, no key needed.
  2. When you want the discussion panel, open Settings and paste an Anthropic API key (create one at console.anthropic.com). The key is stored only in your browser and sent only to api.anthropic.com; tick "forget this key when the browser closes" if you prefer it gone after each session.
  3. Bring an article and read.

Your notebook (articles, highlights, notes, discussions) is saved automatically in your browser's storage for the address you opened. Keep using the same address in the same browser and everything will be where you left it.

Honest limits

  • You need an Anthropic API key, and usage is billed to your key. The default model is Claude Opus 5; Settings lets you switch to Claude Sonnet 5 or Claude Haiku 4.5 for cheaper conversations.
  • Link fetching uses Jina Reader. The anonymous free tier sometimes blocks whole networks, and large publishers with bot walls (the New York Times, for example) refuse it even for free articles. A free key from jina.ai (Settings, "Fetch key") makes fetching reliable; for bot-walled sites, copy and paste, which is a first-class path here.
  • Sync is a file, not a service. The browser notebook stays on one machine; a notebook file in iCloud or Drive is how you move between machines. There are no accounts and no live multi-device merge, and if two machines write the same file simultaneously, last save wins.
  • Desktop-first. The margin needs room; margin notes hide below roughly 900px of width.
  • No server anywhere. Article fetches go to r.jina.ai, chat goes to api.anthropic.com with your key, and nothing else leaves your browser. There are no analytics and no accounts. This is both the feature and the limit.

About keeping an API key in the browser

The page calls Anthropic directly from the browser (anthropic-dangerous-direct-browser-access), which is what makes the no-server design possible, and it means your key sits in browser storage. Reasonable precautions: tick "forget this key when the browser closes" so it lives only in sessionStorage, run the downloaded file locally rather than someone else's hosted copy, use a key with a spend limit from a dedicated workspace, and clear it in Settings when you are done. Notebook backups and notebook files deliberately never include the key.

Design

Seventies road-trip poster energy: one yellow, thick black outlines, sky and sand. Display type is Titan One; reading type stays quiet serif because you will be here a while.

License

MIT

About

A reading room in one HTML file: highlights, margin notes that ask why, and Claude discussions grounded in the whole article. Local-first, bring your own key.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages