Skip to content

Agents

What an agent needs to write and fix build files, the JSON Schema, Markdown pages, and the hosted MCP server.

Updated View as Markdown

The schema

The build file’s JSON Schema is at https://build.ezghcloud.com/schema/v1.json, without a credential. The file format is small on purpose: plain YAML, no expressions, nothing to import, one way to order tasks.

ValidateFile checks a file’s format and answers every problem as {path, message, example}: where it is, why, and text that would be accepted. ezgh build validate --json prints the same, and also looks up what the file names.

These pages as Markdown

Every page here is also served as Markdown: add /index.md to its URL. /build/llms.txt lists this section’s pages, and /llms.txt and /llms-full.txt cover the whole site.

When a pipeline fails

GetPipeline answers the pipeline with its error and every task’s status, exitCode and reason. ReadTaskLog answers a task’s log as bytes from from. ezgh build logs --failed --json answers {"pipeline", "failed": [{"task", "exitCode", "logTail"}]}.

The hosted MCP server

The hosted MCP server reaches EZGH Build through call_api with the service build, as you:

Planning and running a working tree need a checkout: use ezgh build plan and ezgh build run (Run locally).

Navigation

Type to search…

↑↓ navigate↵ selectEsc close