shipcue

Bug reports your coding agents can fix

A report button for your app, a queue in your own Postgres, and an MCP server so Claude Code or Codex can take the most urgent report, fix it and close it with the PR link.

Now serving--nobody yet

    Try it: file a few reports, then claim one the way an agent would. The most urgent goes first.

    How it works

    Someone reports it

    The button opens a small form: bug or feature, what happened, how bad it is, where in the app. People can paste a screenshot. The page address, browser and a snapshot of app state you choose come along automatically.

    It joins the queue

    Reports go into one table in your own Postgres, ordered by priority and then by age. Nothing goes to a third-party dashboard.

    An agent fixes it

    The MCP server hands an agent the top report as a ready-to-run task. Claims are atomic, so several agents can work the queue at once and never take the same report.

    Who uses shipcue

    Hackathon teams

    Four people each running a couple of agents on one repo. One queue means no two agents fix the same bug, and nobody's fix quietly undoes someone else's.

    Founders with early users

    Users report from inside the app with the page, browser and state attached. Your agent works the queue and you review the PRs.

    Internal tools and betas

    Teammates and testers file what they hit while they click through. The most urgent report gets fixed first.

    All use cases

    Add it in three steps

    Create the table, mount one handler, drop in the button.

    import { ReportButton } from 'shipcue/react';
    
    <ReportButton
      areas={[{ value: 'editor', label: 'Editor' }]}
      diagnostics={() => ({ route: location.pathname })}
    />

    Full setup in the docs