Developers
The eBRBe browser extension
Start the timer from the issue, pull request, ticket, doc or design you're working on, on the right task, without leaving the page. Chrome, Edge and Firefox.
Install and sign in
Install eBRBe Time Tracker from the Chrome Web Store, Microsoft Edge Add-ons or Firefox Add-ons, then click the eBRBe button in the toolbar and Sign in to eBRBe. A tab opens at https://ebrbe.com/device with a one-time code: check it matches the popup, pick the workspace, and approve. That's the same device sign-in as the CLI.
The extension then holds a personal API key limited to time and work items (time:read, time:write, work:read, work:write; never invoices or reports). It shows up in Settings → Developers as "eBRBe extension (Chrome)" (or Edge, Firefox), where you can revoke it. Signing out of the extension revokes it at once.
Where the timer button appears
| Site | Pages |
|---|---|
| GitHub | Issues and pull requests (next to the header actions) |
| Linear | Issues |
| Jira (Atlassian cloud) | Issues (/browse/KEY-1 and boards with an issue open) |
| Notion | Pages |
| Google Docs | Docs, Sheets and Slides |
| Figma | Design files and FigJam boards |
Where the page has a stable header the button sits inline; otherwise it floats in the bottom-right corner. It lives in a closed Shadow DOM, so it can't clash with the page's styles, and the extension never injects scripts into the page itself. Turn sites off in the popup's Settings.
Start timer on the right task
Open the button's panel and eBRBe suggests the tasks this page is about, strongest first. It asks GET /api/v1/work-items/lookup with the page's address and title (and, on a pull request, its branch name if it carries a key):
| Reason | When |
|---|---|
| Linked evidence | Evidence on this page (for example the pull request imported by the GitHub integration) is linked to a task. |
| Key mentioned | The title, branch or address mentions a task key like WEB-12 (Linear and Jira keys work when your project uses the same key). |
| Similar title | An open task you can see has a title close to the page's, preferring the project the page belongs to. |
You only ever see tasks you could see in eBRBe. With no match, start the timer on the page's project (when eBRBe knows it) or without a task; the page title becomes the description.
The popup
- The running timer, with stop.
- Suggestions for the tab you opened it on.
- A task picker: your open assigned tasks, or search by title or key.
- Quick add: Log time (
1h30 Code review,45m,1:15), on the task you picked last; or New task in a project, optionally starting the timer on it. - Settings: the sites the button appears on, the eBRBe address (for a self-hosted or test server), and sign-out.
Permissions and privacy
| Permission | Why |
|---|---|
storage | Your settings and the encrypted API key. |
alarms | Refresh the running timer once a minute (toolbar badge). |
activeTab | Read the address and title of the tab you open the popup on, for suggestions. No access to other tabs or your history. |
| Your eBRBe address | Talk to the eBRBe API. A self-hosted address is asked for when you set it (optional permission). |
| The six sites above | Show the button there (content scripts). The extension can't run anywhere else. |
Only the extension's background service worker holds the key and talks to eBRBe; the button on a page asks it, and may only start a timer on a task that page was offered. The key is encrypted with a browser-held key that page scripts can't reach. A page's address and title leave your browser only when you open the button's panel or the popup, go only to your eBRBe, and aren't stored. No analytics, no remote code. See the privacy policy.
Self-hosted and development servers
In the popup, open Settings and set the eBRBe address (https, or http on localhost). The browser asks you to allow that address; changing it signs you out. Developers can build the extension for a local server with pnpm --filter @ebrbe/extension dev (see apps/extension/STORE.md).