Help
What to say when a first run goes wrong, from a pending Stripe check to an agent you need to stop, and how to reach the Startups.Studio team.
Ask your agent first. It reads these docs and your audit log, so most fixes take one sentence.
First-run problems
| What you see | Say | What happens |
|---|---|---|
| Stripe still says verification is pending | "What does Stripe still need from me?" | Each open Stripe requirement is a Task with Stripe's form and its deadline. Merchant account lists what Stripe asks for. |
| Payments stopped after a Stripe deadline | "Why are charges off?" | A missed requirement turns charges off until you answer it. Charges disabled has the fix. |
| Your domain does not load | "My domain is not working" | Fix my domain checks each record and names the wrong one. |
npm create startups stops with an error | "Why did create fail?" | The error names its code and request id. Errors gives each code's cause and fix. |
| A test payment is missing | "Show me today's test payments" | Test and live keep separate records, so a test payment shows only in test. Test and live explains the split. |
| An agent did something you did not want | "Pause every agent that talks to customers" | Pause stops them at once, and the next section undoes the work. |
Undo what an agent did
Every call is an Action in the audit log, with who asked, what ran and what it changed. Say "undo that", and the agent calls Change.revert: a new Change that reverses the old one and deletes nothing.
Money comes back through its own Verb. A payment returns by Order.refund, and an unpaid Invoice stops by Invoice.void. A message already sent stays sent, so set a spending Limit before it matters, as in approve what agents spend.
Reach a person
Support is the Startups.Studio team. Reach it on startups.studio, startups.new or startup.games.
Say "get me a person" in any of the three. Your agent opens a Conversation with the team and attaches the request ids and Actions involved. A person from the team answers in the same thread.
From code, every error carries a requestId. Debugging shows the full record behind one id, which is usually the answer.
What changed
The Changelog lists what changed in the startup-builder package and its API, SDK, CLI and MCP, newest first. Each guide and System carries live, beta or planned, and the status table defines each one.