Getting started

This page walks through a complete first build: creating an account, describing what you want, answering the agent's questions, and reading the preview. It takes about ten minutes end to end, and most of that is you deciding what the site should say.

1. Create your account

Sign up with an email address and password, or with a Google account. After signing up you are asked three short onboarding questions — what you do, what you plan to build, and how you found Black Hole. The answers are used to set sensible defaults for your first build and to skip questions the agent would otherwise ask you every time.

Choose a strong password. Black Hole checks every new password against a list of passwords known to have appeared in public breaches and refuses the ones that have. This check happens on the server and your password is never sent anywhere in readable form.

2. Connect a provider key, or upgrade

Every build runs on a large language model, and that model costs money to run. Black Hole gives you two honest ways to pay for it:

• Use your own key. Connect an API key from OpenAI, Anthropic, Google AI Studio, Mistral, OpenRouter, DeepSeek, Together, or a custom endpoint. You pay your provider directly at their rates, and Black Hole's builder is free. See Connecting your API key.
• Upgrade to Pro. Pro unlocks Black Hole's own hosted Power and Max modes, so you do not need any provider account at all. Billing runs through Stripe.

3. Describe what you want

On the home page you get a single prompt box. Write in normal sentences. There is no syntax to learn and no keywords to memorise. A useful first prompt names the thing being built, who it is for, and what the visitor should do:

"A one-page site for Kalpana Studio, a two-person ceramics workshop in Pune. Show the work, explain the weekend classes, and let people email to book a place. Warm, handmade feel — not corporate."

If you paste a web address anywhere in the prompt, the agent opens that page, takes a screenshot, and reads it before building. That is the fastest way to say "something like this" without describing a design in words.

4. Answer the clarifying questions

The agent only asks when the answer genuinely changes what gets built. You will usually see two or three questions with suggested answers already highlighted. You can answer them, or press Auto-answer to accept every suggestion and start immediately.

5. Watch the build

As the build runs, the activity checklist shows each real step: the brief being analysed, each file being written with its path, and the review pass at the end. If a step fails, it turns red and shows the actual error rather than silently continuing.

6. Read the preview and keep going

1. The finished site appears in the preview panel beside the chat.
2. Scroll through it as a visitor would and note anything that reads wrong.
3. Type your correction as a normal message — "make the class times section a table" — and the agent edits the existing build rather than starting over.
4. When it looks right, publish it. See Publishing and GitHub.

What to do if the first result is disappointing

Do not rewrite the whole prompt. Tell the agent what is wrong with the result in one sentence — too corporate, missing the pricing section, the photos should be full width — and let it revise. Corrections against a real page are far more precise than a longer prompt against a blank one.