Start typing in the new tab and matching bookmarks appear underneath: by title, by site, by folder, with room for a typo. For the ones you cannot name, ask. “Find bookmarks about cooking” has a model on your device read the list and sort it. Your bookmarks never leave the machine.
Free. Open source. Chrome keeps your bookmarks; Fogar reads them.
Chrome’s own bookmark search matches whole words at the start of a title or address. Fogar builds its own index once and ranks every bookmark against every word you type: title first, then site, then folder, then the rest of the address. Short typos in titles are forgiven.
Recent bookmarks get a nudge. So do short titles, which are usually the site itself rather than an article. Six words and up is a question, not a lookup, so the list steps aside and the model takes over.
Ask for a topic and Fogar first has the model expand it into related words, so “cooking” also looks for risotto, kitchen, and seriouseats. A keyword pass over titles, addresses, and folders then sets a floor no model can take away. Finally the model reads your list twenty-five bookmarks at a time and adds what words alone miss.
Results come back matched by both first, then by words, then the model’s own picks. Past five hundred bookmarks it re-reads only the keyword candidates, so a big collection stays quick.
| You do | What is read | What leaves your browser |
|---|---|---|
| Type in the box | Your bookmark tree, flattened once into an index with folder paths, rebuilt when a bookmark changes. | Nothing |
| Ask, on this device | Titles, sites, and folder names, read by the model inside the browser, twenty-five at a time. | Nothing |
| Ask, in Cloud mode | The same list, in the same batches.The model is at the endpoint you typed, so that is where the list goes. | Bookmark titles and sites, to your provider |
| Click × | The one bookmark you pointed at, removed after you confirm. | Nothing |
Fogar asks for the bookmarks permission to read the tree and, on request, remove one item. It never adds, moves, or renames a bookmark, except when you promote a saved session into a folder.
With the Sessions widget on the page, the same keystrokes find tabs open in your other windows. One click brings the window forward and selects the tab.
Windows you saved and closed appear too, one click from reopening. That is the Sessions widget.
A URL opens. A question mark searches the web. “remind me” sets a reminder, “todo:” adds a todo, arithmetic is computed. Anything else goes to the model.
Type, arrow down, Enter. Cmd or Ctrl and Enter always searches the web instead, whatever the box would otherwise do.
The rest of Fogar is a new tab that answers from a model running in your browser. See what leaves in each mode.
No. Chrome keeps the bookmarks and you organize them there as before. Fogar reads the tree, searches it as you type, and can remove the one bookmark you point at. The only thing it ever adds is a folder when you promote a saved session.
Only the one you click × on, and only after you confirm. The finder never removes anything; it lists.
Titles forgive small ones: the letters of a word four characters or longer only have to appear in order, not next to each other, so “fgar” still finds Fogar. Sites, folders, and addresses need an exact fragment.
The index is built once from Chrome’s bookmark tree and rebuilt when bookmarks change, so thousands are fine and typing stays instant. The finder has the model read everything up to five hundred bookmarks; above that it reads only the keyword candidates, so it stays quick on big collections.
Yes, with your own key. Be aware of what that means: the titles and sites of your bookmarks are sent to the endpoint you typed, in batches, because that is where the model reading them lives. On this device, nothing is sent.
Six words and up is a question rather than a lookup, so the bookmark list steps aside and the question goes to the model. If you want the model to look through your bookmarks, say so: “find bookmarks about …” or “which bookmarks are job postings” routes to the finder.
Fogar is on the Chrome Web Store. One click to add it, and it updates itself from there. Then open a new tab.
Free, from the Chrome Web Store. Brave, Arc, and Edge install from it too.
On your phone, or not on Chrome? The same Fogar runs as a web app at app.fogar.ai. Open it once with a connection, add it to your home screen (Safari: Share, then Add to Home Screen; Chrome: the menu, then Add to Home screen), and set it up from there; after that it works offline. The widgets that need Chrome’s own APIs, Sessions, bookmarks, Inbox, Feed, Jira, and Agenda, stay on the desktop.
Loaded the zip before the listing went live? The store copy has a different extension ID, so your data will not follow on its own. Three steps move it over.
Todos, notes, recipes, widgets, sessions, and settings go into one file.
It opens on your next new tab, empty.
Once it looks right, remove the old copy in chrome://extensions.
Can't use the store? The same build is here as a zip: unzip it, turn on Developer mode in chrome://extensions, and Load unpacked. It will not update itself.