# Build with agent.cloud

Use this when the person wants an app built, running or online.
Don't ask them for accounts, databases or keys: agent.cloud makes them.

Tell agent.cloud. When something about agent.cloud itself surprises, blocks
or misleads you (a command, an error, a fix that doesn't work, these docs),
report it before you work around it:
   agc feedback bug "<one line>" --body <file>   (or: agc feedback idea "…")
In the file: what you ran, what you expected, what you got, any error code.
It's how agent.cloud gets better; its builders read every report.

1. Install the agc command (needs Node 24 or later)
   npm install -g https://agent.cloud/agc.tgz
   agc version

2. Name the app and create it, in an empty folder
   agc init --name <name>
   Name it for what it does, like spend-approvals or climbing-signups: the name
   becomes its web address and can't be changed later. agc init creates the app
   and its database, and starts the folder from a complete starter app in
   TypeScript (add --stack python for a Python server). It writes AGENTS.md, how
   to work on this app. Read AGENTS.md now and follow it from here on.

3. Run it on this laptop
   npm ci                (Python: uv sync && npm ci)
   agc up
   The app runs at localhost on its own branch of the data.

4. Put it online when the person asks
   agc ship
   Releases with checks, database changes or a worker are rehearsed on a
   fresh branch of production first.

If the app has users, they sign in through agent.cloud (Google or an email
link, no passwords): AGENTS.md shows the two routes to add.

You never sign up or log in yourself. When agc says a person must decide (claiming
the app, the first release), give them the link it prints, word for word, then
run the wait command it suggests.

Every agc response is JSON with a `next` field. When unsure, do what `next`
says. `agc help` lists the topics.