10 articles with this tag

Browsing in bursts? Your history should group itself like you do. I do not browse in a straight line. I doubt most people do. I browse in bursts. A burst of research before building a feature. A burst of comparison before choosing a tool. A burst of debugging when something breaks. A burst of reading when one article...

I replaced chrome://history — here's why I skipped the AI everyone else would've reached for If you tell someone you are building a smarter browser history page, the AI idea arrives almost immediately. Summarize my tabs. Ask my history questions. Name my sessions. Turn yesterday's browsing into a neat report. It is an...

Local first, deterministic, and still smarter than chrome://history I like tools that are boring in the right places. That might sound like a strange way to describe a browser history replacement, but it is exactly how I think about Browser Memory. The product should feel useful. It should help me return to sessions,...

What if Chrome's history page understood sessions? I kept asking myself one question while building Browser Memory: What if Chrome's history page understood sessions? Not in a complicated way. Not as a full productivity dashboard. Just enough to know that the seven pages I opened while debugging one problem belonged...

No AI, no cloud, no account: rethinking what smart means in a browser extension When I started building Browser Memory, I kept running into the same assumption: If a browser extension organizes your history, it should probably use AI. I get why that idea appears so quickly. Browser history is full of context. A model...

I stopped re Googling things I'd already found — here's what I built instead There is a special kind of frustration in searching for something you already found. Not something similar. Not a replacement. The exact page. You remember seeing it. You remember it helped. You might even remember what you were working on...

Your browser history should remember your day, not just your URLs Most browser history pages are technically honest and emotionally useless. They tell you what happened. They do not help you understand what the day was. That was the irritation that kept pulling me back to Browser Memory. Chrome already keeps a record...

Browser Memory: sessions, not just a list of URLs The first time I seriously looked at Chrome's history page as a product builder, I realized something simple: It remembers the wrong unit. Chrome remembers visits. I remember sessions. A visit is one page. A session is the reason that page existed in the first place....

I built a Chrome History replacement with zero AI, on purpose The easiest pitch for Browser Memory would have been the obvious one: "AI for your browser history." It almost writes itself. Summarize your browsing. Ask questions about your past tabs. Let a model name your research sessions. Turn every messy trail into a...

Chrome's history page is a junk drawer. I gave mine a memory instead. I have lost the same useful page more times than I want to admit. Not because I forgot how to search. Not because the page disappeared. Usually it was still there, buried somewhere inside , sitting between a login redirect, a docs page I opened by...