The browser extension#

Laver quick-add is a Chrome extension that files a ticket from whatever page you are standing on, with the screen, a recording of the tab and the URL already on it. It is how a bug gets reported by the person who found it instead of being described from memory an hour later.

It is not on the Chrome Web Store. It ships in the extension/ directory of the Laver repository and is loaded unpacked, which takes about a minute.

Install it#

1. Go to chrome://extensions, turn on Developer mode, choose Load unpacked, and pick the extension/ directory.
2. Open its Details → Extension options.
3. Paste an API key — Laver → your profile → API keys. The two addresses are already filled in; change them only if you run Laver yourself.
4. Press Connect. Chrome asks for permission to reach that one address, and the extension asks for no others.
5. Pick a default board.

Chrome 116 or newer. The shortcuts can be changed at chrome://extensions/shortcuts.

Use it#

One text box: the first line becomes the title, the rest becomes the description. The screenshot is taken before the panel is drawn, so the panel is never in the picture. A recording stops on its own after two minutes so the clip stays inside the 25 MB an attachment can be.

• Point at the element you mean with the pin button. Clicking it attaches a screenshot cropped to that element, with a margin of the page around it so it can be placed, and puts its DOM path on the ticket and at the foot of the description.
• The panel stays in front of the page. Nothing can be drawn over it: not a cookie wall, not a chat bubble, not a fullscreen video — which is usually the thing being reported. Drag it by its header if it is sitting on top of that thing.
• The URL you were on is on the ticket as a link, in its own Captured from card.
• Internal tickets are hidden from guests on the board, which is what makes it safe to invite a client onto the board the team works on.
• Each site remembers the board it files to, so the second report on a site does not ask.

What it sends, and what it does not#

• It authenticates with an agent API key, not a session. The key acts as the person who created it, is confined to one workspace, and inherits that person's board access — so revoking it in Laver stops the extension dead. See API keys.
• The key lives in the browser's extension storage and is only ever read by the extension's service worker. The page you are reporting never sees it, and never calls the Laver API.
• Only http and https pages can be captured. A chrome:// page, a local file or an extension page files a ticket without a URL rather than with a useless one.
• Nothing is sent until you press the button. There is no background collection, and the extension holds no permission for a site until you use it there.

Everything it files is an ordinary ticket: the same fields, the same board, the same comments and files as one typed by hand.