Alternatives
Products that do what Tailor: Edit Your Websites in the Browser with Llama3 does
Hey HN! I recently built Tailor (https://tailor.cryingpotato.com) as a way to speed up the dev cycle that comes with tweaking a website. My workflow to tweak websites was pretty painful - I’d change things in devtools until they looked visually correct, and then context-switch back to my terminal to apply relevant edits. Tailor makes that process much easier by keeping the edit loop fully in the browser. Tailor uses LLMs as a fuzzy reasoning engine to automatically map your HTML edits to source code edits. It also runs code directly in your browser using WebContainers so you don't…
- 1

- 2

- 3BH
Hey HN, We got tired of browser frameworks restricting the LLM, so we removed the framework and gave the LLM maximum freedom to do whatever it's trained on. We gave the harness the ability to self correct and add new tools if the LLM wants (is pre-trained on) that. Our Browser Use library is tens of thousands of lines of deterministic heuristics wrapping Chrome (CDP websocket). Element extractors, click helpers, target managemenet (SUPER painful), watchdogs (crash handling, file downloads, alerts), cross origin iframes (if you want to click on an element you have to switch the target first,…
Apr 2026 · github.com
- 4RL
We've been building data pipelines that scrape websites and extract structured data for a while now. If you've done this, you know the drill: you write CSS selectors, the site changes its layout, everything breaks at 2am, and you spend your morning rewriting parsers. LLMs seemed like the obvious fix — just throw the HTML at GPT and ask for JSON. Except in practice, it's more painful than that: - Raw HTML is full of nav bars, footers, and tracking junk that eats your token budget. A typical product page is 80% noise. - LLMs return malformed JSON more often than you'd expect, especially with…
Mar 2026 · github.com
- 5

- 6

- 7

- 8

- 9

- 10

- 11

- 12

- 13

- 14

- 15

- 16

- 17

- 18

- 19

- 20

- 21

- 22

- 23

2d ago · chromewebstore.google.com
- 24WR
How It Works - Offline Indexing: Docs are processed and embedded using the GTE-small model at build time. Browser-Based Magic: - SQLite database (stored in the browser) for vector search. - Local embedding model for query processing. - Local LLaMA model for response generation using WebLLM. - Everything Happens Locally: No data leaves the user’s device. Key Benefits - No API Costs: Everything runs in the browser—zero backend expenses. - Unlimited Chats: No rate limits or usage restrictions. - Privacy-First: Your data stays on your device, always. You can find the code here:…
2024 · docs.akiradocs.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →