Try Stead
Build the support-agent demo, then try it as both a customer and a developer. You will see an agent read your orders, answer a question, and pause a refund for your approval.
Before you start
Section titled “Before you start”- Install Node.js 22 or newer and npm.
- Have an email inbox you can use for verification.
- Have a funded model-provider API key that can use the starter’s model. The default is
gpt-5.6-lunathrough OpenAI’s API. - Keep a terminal and browser open. You do not need a Fly or Cloudflare account.
The beta signup flow does not ask for a payment card. Your model provider bills model requests. The starter limits each reply to 1,000 output tokens and sets a run budget of 20,000 tokens and $0.50. Those are configured limits, not the expected price of a reply or a provider-side spending cap.
Build the demo
Section titled “Build the demo”Follow the quickstart from an empty directory. It covers registration, deployment, and the customer app. Keep the developer console open in another tab for approvals.
Try these four things
Section titled “Try these four things”- Ask about your orders. After creating demo orders, ask “What orders do I have, and how much did each cost?” The reply should name the Trail backpack and Travel mug with their amounts.
- Request a refund. Request the Travel mug refund. Its balance should stay at $24 until you approve the action in the developer console, then become $0. This is demo data; no money moves.
- Come back. Sign out of the customer app and sign back in. Your orders and support conversation should still be there.
- Try another customer. Use a different verified email in a separate browser profile. That customer should start with their own empty order list and conversation.
If something fails
Section titled “If something fails”Start with the project’s Diagnostics page or run npx getstead doctor from your starter directory. The troubleshooting guide explains the common failures and what to do next.
When reporting a problem, include:
- What you were trying to do, the exact command or screen, and the error text.
- Your CLI/SDK versions and Node version.
- The project ID, run ID, and request reference if the error shows one.
- Whether the failure repeats, and the approximate time it happened.
Send the report through the conversation where you received this invitation. Review logs and screenshots first. Never share provider keys, project credentials, cookies, login codes, verification/reset links, or customer data.
When you finish
Section titled “When you finish”You can keep experimenting in the project. If you delete it in Settings, its data and runs are permanently removed. Do not delete a project you want to return to.