Start from the code you already have
Open the project in your coding agent and make sure its normal local build works. A website folder can be uploaded directly; a repository can be deployed through the GitHub connection. You do not need to start from a build.host template or move development into a different editor.
Download Proto and describe the project and address you want; its hosting integration is built in, with no skills to install or update. For other agents, install or refresh the build.host skill and follow its current account connection instructions. The agent can inspect the project’s framework, choose a permitted build path, and report the resulting deployment rather than asking you to reproduce the same setup manually.
Continue after the first URL
A live URL is the beginning of operating an app. Ask the agent to inspect a failed build, read runtime logs, configure a connection, or deploy your next change. Naming the existing project keeps each operation attached to the right app and its deployment history.
For a configuration change, specify whether the value belongs at build time or runtime. Redeploy to apply it. For a regression, ask the agent to identify an available earlier deployment and verify the site after restoring it.
Keep the result verifiable
The useful result is a working application, not merely a completed build. Check important routes, forms, fonts, images, and external API connections on the live address. Your agent can help gather evidence and diagnose failures, but application-specific tests remain part of your project.
Static output is self-serve. For framework projects, build locally and publish the generated files. Request executable deployment access only when build.host must install dependencies, run a build, or keep a server running.