Your first deploy
From a connected agent to a live link — what to say, what happens, what you get back, and how to know it actually worked.
You have connected your agent. Now you want a link.
Say this
put this online
That is genuinely enough, as long as your agent can see the project — the folder it's open in, the files it just wrote, the canvas it just built. Your agent works out what the project is, creates a project and an app on agenthost, and sends the files.
If your agent is working on several things at once, be specific:
put the landing page in ./site online, call it "spring-launch"
What happens
Your agent makes a project
A project is just a folder for your things. Your first deploy creates one; later deploys can reuse it. See The words we use.
It sends your files and we build them
Your agent hands over the project source directly. We work out how to build and run it from what's
in there — a package.json means Node, an index.html means a plain site, and so on — and we
build a container for it. You never choose a build command.
About a minute later, it's live
You get a hostname like spring-launch-8f2a.customer.agenthost.eu, with HTTPS already working.
Anyone with the link can open it, unless you ask for it to be private.
How to know it worked
The link opens and shows your thing. That is the only test that counts, and it is worth doing yourself rather than taking "deployed" for an answer.
Ask your agent to confirm it too:
open the link and check it actually loads
A good agent does this unprompted, because a build can be queued, reported as running, and still be crash-looping. If it isn't serving, ask:
read the logs and tell me what went wrong
Your agent can read your app's build and runtime output directly and usually tells you the fix in the same breath. See Fix a broken deploy.
What you get back
Every app has:
- A URL — a free
*.customer.agenthost.euhostname, or your own domain. - HTTPS, set up automatically. You never touch a certificate.
- A name and an id. The id is what your agent uses for everything afterwards; you never have to remember it, but "the recipe box app" is usually enough for your agent to find it.
Changing it
Ask for the change, then ask for it to go live:
make the header dark and put it online again
The same link updates in place. You do not get a new URL, and you do not have to tell anyone anything. See Update what's live.
It replaces, it doesn't merge
A deploy replaces everything the app was serving with the files sent this time. That is what makes it predictable — what's live is exactly what your agent just sent, with nothing left over from before.
Next
Connect your agent
Add agenthost to Claude, Claude Code, Cursor, VS Code or any MCP client, sign in with your email, and you're done. No API key, no password in a chat window.
The words we use
Organization, project, app, site, runtime, deploy, environment variable, invite. What each one means on agenthost and how they nest.