Three places quibble works
In your browser, in your app, or as a companion on your computer. Each one has the same button and files the same kind of note. Pick the one that matches where your feedback comes from:
In your browser
The quibble extension, on any site, including ones you can't change: someone else's app, a staging build, a vendor's admin screen. Nothing is added to the site. Click the quibble icon on any page, point at what's wrong, and the note goes straight into your own GitHub repository, as your GitHub account.
It does what the in-app button does on GitHub: a priority, tags, pointing at the element, a screenshot with private fields blurred, optional per-site diagnostics, and a review list with close and reopen. Your browser talks only to GitHub; nothing goes through anyone else's server. Chrome and Brave, GitHub only.
Try the extension live, with nothing to install
- Your browserYou spot a problem on any siteThe quibble extension adds the details
- Your GitHubIt arrives as an issue in your repository
Your browser talks only to GitHub.
In your app
Built into your app, for the people who use it. A developer adds quibble once, and everyone who can sign in to your app gets the button on every page. Each note names who sent it, from the sign-in you already have.
quibble runs inside your app: a Python package for FastAPI, Django, Flask, Starlette or Litestar, or your own server following quibble's documented schema. Notes go to GitHub, GitLab, Gitea, Forgejo, Jira or Linear.
- Their browserA user spots a problem and clicks quibble
- Your appquibble adds the page, the error and who sent it
- Your to-do list GitHub, Jira, Linear…It arrives as an issue, ready to fix
Nothing passes through quibble. There’s no quibble server to pass through.
On your computer
A companion beside a desktop app, a local tool, or the app you're
developing, in any language: Node, Rust, Go or anything else.
quibble serve runs next to it on the same computer, and the app's page loads
the button from there.
It listens only on that computer, accepts only the pages you list, and can require a shared key. It files to any of quibble's trackers, from the same settings. It's local by design: for a hosted app in another language, put quibble in your app through the schema.
- Your computerYou spot a problem in your appquibble, running beside it, adds the details
- Your to-do list GitHub, Jira, Linear…It arrives as an issue
Only the issue leaves your computer, sent straight to your to-do list.
quibble serve on the same computer, a note is filed, and the issue arrives. The tracker here is the in-memory stand-in from quibble’s own test kit.Compare Quibble Editions
| In your browser | In your app | On your computer | |
|---|---|---|---|
| Best for | Your team, on any site | Feedback from everyone who uses your app | Desktop apps, local tools, development |
| Who gets the button | Whoever installs the extension | Everyone who can sign in to your app | Whoever uses the app on that computer |
| Changes to the site | None | A developer adds it once | The app loads it from quibble serve |
| Languages | Any site | Python, or any language through the schema | Any |
| Where notes go | GitHub | GitHub, GitLab, Gitea, Forgejo, Jira, Linear | GitHub, GitLab, Gitea, Forgejo, Jira, Linear |
| Who it says filed it | Your GitHub account | The person, from your app's sign-in | The one person set up on that computer |
| Runs on | Your browser | Your app's server | That computer only |
| Review page | Yes, in the extension | Yes | No: it only files |
| Licence | The same for all three: free for individuals and small companies; larger ones, email us | ||
Pick one and start
In your app: set it up, or hand it to your coding agent. On your computer: how quibble serve works. quibble, the extension included, is in early access; email hello [at] quibble [dot] fyi to get it.