Managing requests
The Requests page is where every customer submission lands, and where you triage, grade-check and ship the ones worth shipping. This page covers the inbox itself; see How shipping works for what happens after you click Ship it, and doubloon costs.
Filters and search
The status bar above the list buckets requests into Active, Failed, Rejected, Done and Shipped. Toggle any combination on or off; Active alone is the default. This choice is remembered per app, in your browser only — it isn't synced anywhere else, so a different browser or device starts back at the default.
The search box below the filters narrows whatever the current filter combination already shows, by request text, customer email, or any note you've added — entirely client-side against the page of requests already loaded, so it updates as you type with no round trip to wait on. It doesn't reach into requests further back than what's currently loaded; use Load more requests first if what you're looking for isn't showing yet.
Statuses and progress
An in-flight request shows a segmented progress bar: Triaging, Queued, Building, PR opened, then Shipped. Rejected, Done and Failed are end states and don't show the bar — the status badge alone covers it.
Reload and staying current
The reload button re-fetches the list from the start and refreshes your doubloon balance — useful right after a ship's cost settles, since that can refund doubloons without any other action on your part changing what's on screen. While anything on the page is actively triaging or shipping, the list also quietly refreshes itself every 30 seconds on its own, so you don't need to reach for reload just to see it land.
Expanding a request fetches its grade once; collapsing and re-expanding it — or toggling a status filter that happens to hide and re-show it — reuses that same result rather than re-fetching it, so re-opening a request you've already looked at is instant. Reload is what makes it check again, for the cases where a grade genuinely wasn't ready yet.
Reviews and re-work
Once a request is delivered, its expanded view tracks the pull/merge request's review activity, and — on Basic and Pro plans — lets you queue a bounded re-work pass against specific comments. Exactly what's available here differs by provider: