Sites and domains

Ask the agent for the thing itself: “make a page for the open roles”, “put the docs online”. The reply comes with a preview link to the page on the agent’s own computer, so you can look before anything is published.

The preview rides that computer, which sleeps after about three quiet minutes. A link you forward still works, but the first load after a quiet spell takes about ten seconds while the machine wakes. After that it is fast, and the agent says so when it hands the link over.

When the page is right, say “put it live”. The agent deploys it and comes back with a production address, name.agentbuilt.app, where it stays up on its own. The first deploy takes a couple of minutes while the machine is built and the address and its certificate come up, and the agent reports the address once it answers. After that, a redeploy to the same name is instant.

A site is a folder the agent deploys under a name you choose together. There are three shapes, and the agent picks one from what the folder is:

• A website: files served as they are, such as pages, images or a built front-end.
• An always-on app: a program that runs around the clock, on a machine with 512 MB of memory.
• An always-on app on a bigger machine, with 1 GB of memory, for an app that needs more.

Hosting is included. There is no price per site, no tiers and no checkout. Sites run on the cloud beside your agents’ machines, up to ten live at a time in a workplace (see What runs where). An always-on app can use the room’s saved keys, such as a chat bot’s token. The agent names the key when it deploys, and the key never goes into the app’s files (see Keys for checks and for sites).

A site belongs to the workplace. Any agent, from any room, can list every site, read its logs, restart it, rename it, add a domain and redeploy it. Creating a new site, upgrading one and asking to delete one are for an admin’s agent (see Roles).

A redeploy to a live name is instant, with no approval step and no undo, and the public sees the new version at once. A proposal guards code that lands in a repository; a site is the agent publishing what you asked for. If you want a look first, ask for a preview.

One fence stands between agents. A live site is replaced only by the agent that last deployed it, unless you ask a different agent to take it over. The site’s screen shows who deployed it first and who deployed it last.

A live site can answer on a domain you own, such as app.example.com. Ask an agent to add it. It requests a certificate and hands you one DNS record to create: a CNAME from your hostname to the site. That step is yours, at whichever provider holds your domain.

A bare domain, example.com with nothing in front of it, cannot carry an ordinary CNAME. Use your provider’s ALIAS record or CNAME flattening for that case. A subdomain like www or app takes a plain CNAME.

Once the record is visible, the certificate is issued within minutes, and the agent can confirm the domain reads READY. The agentbuilt.app address keeps working beside your domain. The Workspace has no domains screen, so to see which domains a site answers on, ask an agent. An admin’s agent can take a domain off again.

Ask an agent to rename a site and it moves to the new address at once, with nothing going down. The old address redirects to the new one for good and stays reserved to you, so every link you already shared still arrives.

An always-on app that needs more memory can be upgraded: an agent moves it to the 1 GB machine, and it restarts for a few seconds. There is no downgrade, nothing above 1 GB, and no bigger machine for a website.

Logs and a restart are things you ask an agent for. “Show me the last errors on the dispatch app” or “restart the routing service” is a message to any agent in the workplace.

An agent cannot delete a site. An admin’s agent can ask, and the request waits for you on the site’s own screen. The agent tells you in its reply, because nothing else does. The screen says who asked and when, and offers Delete this site, which asks you to type the site’s name, and Keep it. Only the owner of the agent that asked can decide. An admin also has Delete this site on every site’s screen, request or not.

A deleted site stops serving at once. There is no trash and no restore, but the content is one redeploy away, and the name stays reserved to the workplace so an agent can deploy to it again. The chat where the agent asked gets a card with the outcome, Kept or Deleted.

Home shows a Sites section once the workplace has its first site. Each row is one site: its name, the agent that deployed it, when it was last updated, whether it is a site or an app, and a state badge when it is not simply live.

Tap a row for the site’s screen: the live address, which opens the site, who deployed it first and last, and a delete request when there is one. A teammate’s agent appears as that, with its room.