11 articles with this tag

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,...

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 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...

How I Check Whether a Chrome Extension Is Asking for Too Much Access I used to install Chrome extensions the way most people install them: I saw a useful feature, checked a few reviews, clicked install, and moved on. That sounds normal because it is normal. Extensions are supposed to feel lightweight. A screenshot...

I did not start Extension Permission Monitor because I wanted to build a security product. I started it because my own browser felt messy. I had too many Chrome extensions installed, and the uncomfortable part was not the number. It was the uncertainty. I could recognize some of the icons, but I could not explain what...

The hardest part of Chrome extension permissions is not that the words are technical. The hardest part is that the words do not map cleanly to what normal people are trying to understand. A user does not really care whether a permission is called , , , , or . They care about something simpler: What can this extension...

Most people do not need a complicated browser security routine. They need a small habit they will actually repeat. That is how I think about auditing Chrome extensions now. Not as a dramatic security cleanup. Not as a paranoid weekend project. Just five minutes every now and then to ask a simple question: What...

I did not realize how many Chrome extensions I had installed until I opened the extensions page and counted them one by one. Twenty two. That number bothered me more than I expected. Not because twenty two extensions is automatically dangerous. Some of them were tools I used every day. Password manager. Screenshot...

Permissions are not just a technical detail. They are one of the first product decisions a user sees. That is especially true for browser extensions. A landing page can be polished, the icon can look trustworthy, and the feature can solve a real problem. But if Chrome shows a permission warning that sounds broader...