localmd Connect - Browser Superpowers

Companion for localmd.app - browser tools, page capture and site scripts for your in-browser AI agent.

**localmd.app** is a knowledge base that lives in a folder of plain Markdown on your own disk: an agent lives in your folder, and a wiki grows around your files. It reads the PDFs, EPUBs and notes already there and writes linked Markdown beside them — every citation clicks back to the exact paragraph, and every change waits for your yes. **localmd Connect gives that same agent a pair of hands in your browser.** Not a second AI in your browser with its own chat box and its own memory — that arrangement leaves you copy-pasting between it and everything else. This is the agent you already talk to, with the same knowledge base and the same citation rules, reaching one more place: a browser you are already signed into. **What you read lands in your folder.** Clip the page you are on as clean Markdown with its title, author and dates — or just the passage you selected, anchored so you can cite back to it. Drag a rectangle to screenshot part of a page and annotate it. A PDF open in a tab is filed as the file itself. It arrives as a source in your own folder, citable like any book you put there, so carrying context out of the browser stops being your job. **50+ browser tools, and they work on your own logged-in browser.** Open a page and read it as clean text or Markdown, list what is clickable, click, type, fill a whole form in one call, press keys, scroll, screenshot, manage tabs, and fetch any URL with your own session past the CORS wall that stops an ordinary web page calling most APIs. Pages behind a sign-in, and services that refuse a web page outright, are simply available — no cookie pasting, no second browser, no scraping code to keep alive. These are primitives, not per-site integrations — they work the same way on a site nobody has ever looked at as on one you use daily. **A site nobody wrote support for is a conversation, not a missing feature.** The agent can ask where a value actually comes from — the page's structured data, its accessibility tree, the requests it makes — and run JavaScript in the page's own origin until the answer comes back the same way twice. Then it saves what it worked out as a **skill in your own folder**, and the next time is immediate. Adding a capability is a conversation you have, not a release you wait for. **Highlight while you read.** Mark passages in any page in the colour you want, write a note on one, and they are still there on your next visit. Your agent can read them back, so what you marked by hand becomes the strongest signal of what mattered. Select any text and the toolbar can also translate it, explain it, or run a prompt you wrote yourself — answered by the model you configured in localmd.app, right there over the paragraph. **And persistent page fixes (experimental).** Site scripts let you fix a page once and keep it fixed: hide the ad rails and the clutter, restyle a site you read daily, or run a small script on pages you choose, on every visit until you remove it. **Your browser's own memory, if you let it.** Bookmarks, history, reading list and recently-closed tabs are each behind a switch you flip in the popup — off until they buy you something, and then your agent can find the page you know you read without you hunting for it. ━━━ WHAT YOU CAN DO ━━━ • Clip a page, a selection, a region screenshot or a PDF into your folder with one keystroke, and cite it later like any other source • Research a site you have to be signed in to, straight into your knowledge base • Highlight as you read, and have your agent write up what you marked • Translate or explain a passage in place, or run a prompt you wrote yourself • Have the agent work out how an unfamiliar site serves its data — and keep what it learned as a skill in your folder • Read any page as clean Markdown, or fetch JSON and RSS with your own session • Drive a multi-step task across tabs while you watch it happen • Strip the noise from a site you read daily, permanently ━━━ HOW MUCH IT DOES ON ITS OWN ━━━ The honest answer is mechanisms, not intentions: • Exactly one site can reach the tools — localmd.app. The list is compiled into the extension; there is no setting that widens it, so no page can talk you into granting itself access • Nothing outside your browser can reach it either: no local server, no port, no daemon • Anything that would post, send or delete on a real site asks first, in localmd.app, showing exactly what it is about to do — and driving the page's own buttons by hand does not get around that • Anything that injects code into your pages asks the same way • Writes to your folder arrive as a diff you approve or discard, with git underneath, so nothing is a one-way door • Every site script is listed in the popup, where you can pause or delete it • Your bookmarks, history and reading list stay unreadable until you switch each one on yourself • There is no server of ours anywhere in this — but be clear about what that does and does not mean: what you send your model goes to the provider you configured, under your own key ━━━ OPEN SOURCE ━━━ Both halves are open and MIT-licensed — the app at https://github.com/whitefoxx/localmd and this extension at https://github.com/whitefoxx/web-tools. An extension that drives your signed-in browser is exactly the half you should be able to read. Your files should outlive the app. They are Markdown in a folder you chose; if you stop using localmd tomorrow, everything you wrote is still there, openable by anything. ━━━ WHAT TO EXPECT ━━━ • This is a **companion**. On its own it does nothing — it needs localmd.app, which is free and open source. • **An agent driving a site is less settled than a purpose-built integration.** Sites get redesigned and things break. We think this is the right direction and are betting on it; you should know it is a bet and not a finished spec. • Chrome or Chromium only. The app half needs the File System Access API — the same API that lets your knowledge base be a real folder on your disk instead of a database we hold. • Site scripts need Chrome's **"Allow user scripts"** switch on this extension's details page. One click, and everything else works without it. • It runs headless: no window, no sidebar, just a small toolbar popup showing status, what you captured, and your site scripts. ━━━ GET STARTED ━━━ 1. Install localmd Connect. 2. Open localmd.app — it is allowed by default. Settings → Tools will say Connected, and your agent has the tools. 3. Turn on "Allow user scripts" in the extension's details page if you want persistent page fixes. The knowledge base itself: https://localmd.app