hcl

Overview ¶

Package hcl provides an HCL → YAML converter for docker-agent configuration files. The HCL surface mirrors the YAML schema with a few conventions:

• Top-level keyed maps (agents, models, providers, mcps, rag) are written as labeled blocks, e.g. `agent "root" { ... }` becomes `agents: { root: { ... } }`.
• Inside an agent, `command "name" { ... }` becomes `commands: { name: { ... } }`.
• Toolsets use the label as the `type` field: `toolset "mcp" { ... }` becomes `toolsets: [{ type: mcp, ... }]`. At the top level, `toolsets "name" { ... }` instead defines a reusable, named toolset under `toolsets: { name: { ... } }`.
• Multi-line strings should use heredocs. Because HCL templates expand `${...}` interpolation, any literal `${...}` (such as `${shell({cmd: "..."})}`) must be escaped as `$${...}`.
• The custom `file("path")` function reads a UTF-8 text file and returns its contents as a string. An optional second argument renders the file as an HCL template, e.g. `file("prompt.md", { name = "Ada" })` expands `${name}` inside the file. Relative paths are resolved from the HCL config file's directory.

The converter does not validate the resulting document against the configuration schema; that is left to the existing YAML/JSON loader.