Install FrontBug
There are two versions and they are not the same. The one in the Chrome Web Store installs in one click. The newer one, the only one that talks to your agent, is behind a free account.
What works today
- Sessions on any http or https page, with notes on an element, a region or the whole page.
- Component fingerprints: selector, framework component and, on development builds, file and line.
- Screenshots and voice notes, with the console and network of the thirty seconds before each note.
- Log triage that puts the first-party failure after your click at the top and keeps the noise.
- An exported bundle a coding agent can work from, and a review hub for teams with a board and per note ownership.
The extension has been under Chrome Web Store review since September 2026. This page changes when that does.
One click, from the store
Install FrontBug from the Chrome Web Store. You get everything the extension does on its own: pin notes to components, capture them with their logs and screenshots, record a voice note, export a bundle you can hand to anyone. What you do not get is the Agent tab working. The published build ships the setting but not the channel behind it, so the switch is there and does nothing.
The newest build, with an account
This is the same extension, ahead of what the store is serving, with the local channel working: notes go straight into a Claude Code session running in your repo, no copy-paste. It is not published anywhere yet: Google is still reviewing it. So the way to get it is an account.
Create a free account and download it
The account is not a toll gate: it is the hub where your team’s notes land, where you triage them and close a session. Free, no card. Already have one? Sign in and download.
Why there is no one click for that one
Chrome refuses to install extensions that do not come from its own store on Windows and macOS. A download button for a .crx would look like a shortcut and would not work: the file downloads, you drag it in, and the entry sits there greyed out. We would rather ask you to sign in once and follow four steps that work than offer one that does not.
The CLI, for the agent tab
Only needed for that second path. It is on npm, MIT licensed, with no dependencies: what you install is what runs.
- Install it globally:
npm install -g frontbug - In the repo you are reviewing, start the agent:
frontbug agent. It puts the token the extension asks for on your clipboard. - Paste it into the extension’s Agent tab and leave that terminal running.
frontbug --help lists the rest: reading notes in the repo, marking them fixed, pulling a bundle, and the Claude Code skill.
What you need next to it
Nothing, to take notes and export a bundle: the extension works on its own and with the network off. The account and the CLI are for the step after that: getting those notes to whoever fixes them.