How shipping works

Shipping a request queues a job for a coding agent. You choose which agent tier to use before shipping — cheaper tiers cost fewer doubloons but are more likely to need refinement; higher tiers cost more and handle more ambiguous requests better.

Doubloons

Doubloons are CustomerShip's usage credit, shared across every app in your account. Your plan gives you a monthly allowance; unused Basic/Pro doubloons roll over to the next month (Free doubloons don't). Shipping a request reserves the doubloon cost of the agent tier you picked up front.

Outcomes

Prepared. The agent made a real change and a pull request is open for your review. If your repository has tests, they ran as part of this; if it doesn't, the change is still prepared but flagged as unverified by tests.
Failed — repository. The agent couldn't produce an applicable change for this request (for example, the request was too vague, or nothing in the repository matched what was being asked for), or your tests failed against the change. Half your reserved doubloons are refunded; refining the request and resubmitting usually helps.
Failed — platform. Something went wrong on our side. You're fully refunded.

A job that hits a temporary problem is retried automatically (up to three attempts) before it's reported as failed — you don't need to resubmit it yourself unless you see a final failed status.