quibble.fyi
Early access

One button, four jobs

quibble puts feedback into your tracker the moment someone has it, from inside your app, on the page it's about. Who's clicking the button changes what that's worth.

Hear from your customers

Your signed-in users see a small button on every page. When something annoys them, they write a sentence and send it, without leaving the page, finding a support address or describing where they were.

You get an issue in your own tracker with the page, their browser, the error the page threw, and who sent it, taken from the sign-in you already have. It's filed with your labels and a priority, next to the rest of your work, not in a separate inbox.

quibble's endpoint sits behind your app's sign-in, like the rest of your app. It is for people who use your product, not an open form on a public page.

Try it on a store checkout

#218 feedback: the coupon box says every code is invalid

P2checkout

Speed up QA testing

Testers file as they click through a build. Every report arrives with the page, the browser, the screen size and the last errors the page threw, so nobody has to ask “which page?” or “can you send the console?”.

They can point at the element that's wrong, attach a screenshot, and tag the note with labels your tracker already has. Turn on failed network requests and console output for a test build, and add fields of your own, such as the build number.

Across several repositories, quibble files each note into the right one by page, and the review page lists everything filed so far, open or closed.

Try it on a reports dashboard

#57 feedback: save spins forever on the profile form

P1bug

  • Page: /settings/profile
  • build: 2026.09.24-rc2
  • element: form#profile button[type=submit]

▸ Diagnostics netFailures: POST /api/profile → 500 (812ms)

Tighten the loop with your coding agent

When you build with a coding agent, the slow part is often telling it what's wrong. With quibble you try the build, click the button on the thing that's off, and say so in a sentence. The issue that lands already holds what an agent needs: what you said, where you were, the element, and what broke.

Claude Code, GitHub Copilot's coding agent, OpenAI Codex, or whatever agent reads your tracker can pick it up from the quibble label and open the fix. On GitHub, the official GitHub MCP server already reads these issues, so there's nothing extra to build or run.

Try it on a staging build

  1. “ugh”
  2. Issue #412
  3. Your agent
  4. Pull request

Make support requests effortless

When a customer is stuck, the hardest part of a support request is usually the first question back: which page, which account, what did it say? With quibble they ask from the page they're stuck on, in a sentence, and never leave your app.

The request lands in your tracker with the page, who's asking (from the sign-in you already have), the error the page showed, and any account details your app chooses to add, like plan or account ID. Card numbers and other private fields stay masked.

quibble files into your issue tracker, not a helpdesk. It suits teams that run support from GitHub, GitLab, Gitea or Forgejo, next to the fixes it leads to.

Try it on a billing page

#731 feedback: I can't update my card, it just says something went wrong

P2billing

  • Page: /settings/billing
  • Reported by: [email protected] (via quibble)
  • account_id: acct_2231
  • plan: Team

▸ Diagnostics jsErrors: PaymentsError: card update rejected (code PM_402)

Want it in your app?

quibble is in early access. Write to [email protected] and say which of these you'd use it for. A person reads every one.

Try it live first