Skip to content
build.host

Search build.host

Loading search…

↑ ↓ to browse · Enter to open · Esc to close

Start deploying

Deploy and operate.
From your agent.

Connect your coding agent to build.host, publish your project, and manage it through the same conversation.

Recommended: download Proto and just prompt

Download Proto and open your project. The build.host integration is built in, with no skills to install or update. Ask Proto to deploy your project using your connected ERP.AI account.

Using another coding agent

Claude Code, Codex, and other agents need the build.host skill installed and kept current. The Bash installer below installs for Claude Code and for Codex when its configuration directory exists. For other agents, read the current skill and use the agent’s supported skill directory. Rerun setup when skill updates are available. Follow the skill’s current account connection instructions.

curl -fsSL build.host/api/install | bash

Ask: “Deploy this project to build.host as fieldwork.” Your agent inspects the project, checks allowed build capabilities, and returns a live address after a successful deployment.

Bring a folder or a repository

Upload a local website folder without GitHub, or deploy from a repository your account can access. Keep the project identity stable when updating an existing site. Static output is self-serve. For framework projects, build locally and upload the generated files unless your account has executable deployment access. Apps in the approved catalog (GET /api/apps) deploy with their Dockerfile on any account.

What your agent can do

Deploy

“Deploy this project as fieldwork.”

POST /api/projects

Redeploy

“Deploy the latest version of fieldwork.”

POST /api/projects/:id/deploy

Configure

“Set API_BASE_URL on fieldwork at runtime.”

POST /api/projects/:id/envs

Read logs

“Show the latest runtime logs for fieldwork.”

GET /api/projects/:id/logs

Roll back

“Restore the previous deployment of fieldwork.”

POST /api/projects/:id/rollback

Restart

“Restart fieldwork.”

POST /api/projects/:id/restart

The full contract, required fields, authentication flow, and error handling live in the build.host skill. Use the skill rather than guessing API payloads.

Environment variables

Choose build-time or runtime scope deliberately. Stored values are encrypted at rest, and a redeployment is required to apply changes. Public frontend variables can appear in downloadable JavaScript; keep server secrets out of frontend code and use the supported credential flow.

Logs and recovery

Use build logs when a deployment fails to build, and runtime logs when a live app has a problem. Restart runs the current release again; redeploy publishes a new version; rollback restores an available earlier deployment. Verify the live URL and main application flow after each operation.