Start with a project that runs
Open your website folder in your coding agent. Check that its normal local build succeeds and that required assets and routes are present. Static output can be published directly. If build.host must install dependencies, run the build, or keep a server running, your account needs executable deployment access.
Choose Proto or set up your agent
Proto is the recommended setup: download it, open your project, and just prompt. Its build.host integration is built in, with no skills to install or update. For Claude Code or Codex, use the Bash installer below and follow the current skill’s account connection instructions. Other agents need the skill installed in their supported skill directory. Refresh the skill when updates are available; never paste credentials into a conversation.
curl -fsSL build.host/api/install | bashAsk for the deployment you want
Give your agent the project folder and preferred app name. For example: “Deploy this project to build.host as fieldwork.” The agent should inspect the project, choose an allowed build path, and keep you informed while the deployment runs. A static folder can be uploaded without first creating a Git repository.
Verify the live result
Open the returned URL and exercise the main user flow. Check page routes, assets, forms, and any API connections. A completed build does not prove that an external service is configured correctly. If something fails, ask the agent to inspect build or runtime logs and report the actual failure.
Update the same project
After a change, tell your agent to redeploy the existing project. Keep the project identity and address stable instead of creating another app each time. Ask for logs, a restart, or a rollback when needed. Environment-variable changes require a redeployment to take effect.