The Inbox widget shows your unread Gmail on every new tab. The Jira widget shows the issues any JQL query returns. Both are read-only, both run from your browser with your own sign-in or token, and nothing goes through a Fogar server.
Free. Open source. Both widgets are optional; each asks for its one site when you save it.
| You choose | What Fogar reads | Where the request goes |
|---|---|---|
| Gmail, unread feed | The unread feed Gmail already publishes for the account signed in to this browser, or one label of it.Sender, subject, snippet, and date. Nothing to set up; your Gmail session is the sign-in. | mail.google.com |
| Gmail API, your client | Any Gmail search, read and unread, through an OAuth client you create in your own Google project.Only the From, Subject, and Date headers and Google’s snippet. Never the message body. | accounts.google.com, gmail.googleapis.com |
| Jira | The issues one JQL query returns: key, summary, status, type, priority, assignee, last update.Jira Cloud: your account email and an API token. Server and Data Center: a personal access token. | Your Jira site |
Each site is requested as an optional permission when you save the widget. The Gmail API path also needs Chrome’s identity permission, asked only when you click Connect Gmail.
Add widget, then Inbox, then “Gmail, unread feed”. That is it. To show a slice, make a Gmail filter that applies a label and name the label here. Several Google accounts? Set the account number, as in mail.google.com/mail/u/1.
no setup · unread only · one label as the filterChoose “Gmail API, your own client”. In Google Cloud, create a project, enable the Gmail API, add a Web application client with the redirect address Fogar shows, add yourself as a test user, and paste the client id. Then any search works: from:stripe.com newer_than:7d.
about five minutes · your project, your keyAdd widget, then Jira. Paste your site, your email, and an API token from id.atlassian.com. Leave JQL blank for your unresolved issues, most recently updated first, or paste any query: a sprint, a saved filter, a team.
read-only · up to 50 issues · fetched again after five minutesThe rest of Fogar is a new tab that answers from a model running in your browser. See what leaves in each mode.
No. There is no Fogar server. Your browser asks Gmail or Jira directly, and the list it gets back is kept in Chrome’s extension storage on this device.
Gmail publishes your unread mail as a feed for whichever account is signed in to this browser. Fogar fetches it with that session, the same way a Gmail tab would. If you are signed out, the widget tells you to open Gmail and sign in.
For any Gmail search and for read as well as unread mail. Google treats Gmail read access as restricted, so Fogar does not ship a client. You create one in your own Google Cloud project, free, in about five minutes, and paste its id.
The unread feed shows unread mail only. Either connection can also narrow to messages whose sender or subject contains a word you choose. For read mail or full Gmail search syntax, use the Gmail API option.
Yes. For a site that is not on atlassian.net, paste a personal access token from your Jira profile instead of an email and API token. Fogar tries Jira Cloud’s current search endpoint first and falls back to the classic one.
No. It only runs your search and lists the results. To edit an issue, click it and it opens in Jira.
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.