Guide
Badges, tiers, and reporting issues
Two things people ask about that are not part of building: the achievement system, and what to do when something goes wrong.
Badges are cosmetic. They exist because shipping work is worth marking. Reporting an issue is the opposite: it is the shortest path to a fix, and the more precisely you describe the symptom, the faster it goes.
Badges
The badges page tracks achievements earned from real activity in your account, not from anything you can buy. Each one records a milestone you actually reached.
| Badge family | What it records |
|---|---|
| Builds shipped | Projects you took all the way to a published result. |
| Publish streaks | Consistency: shipping something on consecutive days. |
| Founder Tier | Overall progress across your whole history on the account. |
Tiers are cumulative and never reset. Nothing about badges affects your plan, your credits, or what the agent will do for you.
Reporting an issue
The issue page is built for diagnosis rather than for a complaint box. When you describe a problem there, Black Whole can run a live self-check against the thing that broke and attach the result to your report. That removes the slowest part of any bug report: the back and forth about what you were looking at.
- Say what you expected, then what actually happened.
- Name the project, the page, and roughly when it happened.
- Attach the self-check result if the page offers to run one.
- If the problem is in a build, describe the last change you asked for.
Never paste a secret into a report
Anything you type into a report becomes part of the record. If a key or a password was involved, rotate it at the provider first, then describe what happened without the value. See Secrets.Developer access
Black Whole also exposes a Model Context Protocol endpoint, so an external AI tool you already use can reach your account through a standard, authenticated interface. It is aimed at developers who want the same capability inside their own editor rather than in a browser tab.