Working with a coding agent

Hand behold to a coding agent. Every pane is plain JSON over HTTP, and each write stays with you.

Works

• GET /api lists every route and what it does
• /api/graph returns the graph as { ir, svg, meta } with drift status on each node
• A failed precondition answers {code, error, remedy}, so an agent branches on code
• behold preview and serve --public refuse every write

Needs

• An agent that can run commands
• Read-only credentials in the shell that starts behold, when nothing should be applied

First step

Hand the agent this prompt:

Clone https://github.com/INTENTIUS/behold and get me looking at a live
infrastructure graph in my browser.

I want the bundled demo. It needs Docker and no cloud account. Install what
it needs and start it, then tell me the URL.

Walk me through what I am looking at: what the colours mean, and how I make a
resource change colour while I watch.

When Docker is not running, say so. Show me the source graph on its own
instead.

For anything past the demo, read https://intentius.io/behold/llms.txt and
https://intentius.io/behold/using/agents/.

Never deploy with the Deploy button, `POST /api/apply` or `POST /api/ci/dispatch`. Gate approvals stay mine as well (`/api/ops/:name/signal/:gate`, `/api/workspace/gates/approve`, `/api/operator/approve/:op/:gate`). Op runs (`/api/ops/:name/run`) and rollbacks (`/api/rollback`) are mine too. Leave `--auto-sync` off, and keep a `behold preview` or `--public` serve read-only.

Driving it from an agent

Proof

The example projects and end-to-end scripts in the behold repository for this room. The build checks that each one is there.

Path	Where
AGENTS.md	AGENTS.md

Then read

Tasks

Driving it from an agentRun it in five minutes

Background

The read loopRead-only core, delegated writes

Reference

The contractAGENTS.md