Skip to content

The ask demo

llms.txtlists every page for an agent

The ask demo at behold-ask-demo.intentius.workers.dev plays a person asking their coding agent about an estate. The agent asks behold with a Cypher query. The page shows that query with its rows. Each loop asks one question. After the answer, the query box is yours.

The prompt and the agent’s reply type in the pane at the bottom. Before it calls behold, the agent says in one line how it reads the question. The query fills the Cypher pane on the right. When those cards sit too far apart to read, the graph shows them on their own, moved close together with the edges between them. Whole estate switches back. On a phone the answer moves up under the estate graph once the reply has printed.

A headline says what was found. The rows and a drawing of them follow. The drawing joins two resources when a row pairs them. Those edges come from the answer’s rows, and behold adds no join of its own. A dashed edge is one behold derived because one resource’s attribute holds the other’s cloud id.

Click a row or a node to light it on the estate graph. A card opens with where it’s declared and its cloud id. Escape clears it. Cards on the estate graph can be clicked too. Hover over a name for its full key.

While the recording plays, the box is marked Playback. Once the reply has printed it’s marked Your turn. Next question moves on when you’re ready.

Your query runs in your browser on LadybugDB’s WebAssembly build. Writes are refused, as on behold serve. The engine is about 23 MiB and loads after the page draws.

MATCH (a:Resource)-[:KNOWN_AS]->(c:CloudId)<-[:KNOWN_AS]-(b:Resource)
WHERE a.scopeKey <> b.scopeKey
RETURN a.key, b.key, c.value

The graph database lists the tables and properties.

The answers come from one run of behold. The header gives its date. The estate was:

  • example-three-cloud on the floci, floci-az and floci-gcp emulators;
  • the emulated AWS account, indexed with behold index aws;
  • a kind cluster indexed with behold index kubernetes;
  • for the SSH question, one read of a real AWS account’s us-west-2 security groups. Its account id is replaced by 123456789012.

Each question is one call to behold mcp’s ask tool. We wrote the prompts and the replies. Every number and resource in a reply comes from the recorded rows. While the page plays, it reads nothing outside its own files.

Install behold with its optional graph engine. Index any cloud account or cluster you want in the graph. Then serve the estate.

Terminal window
npm install @intentius/behold @ladybugdb/core
npx behold index aws --account <account-id> --regions us-east-1
npx behold serve ./estate --port 4600

Then give your agent behold mcp for the same directory and ask it a question:

Terminal window
claude mcp add behold -- npx behold mcp ./estate

The agent answers through the ask tool with a cypher query and its params as a JSON string. This is the recorded call for “What breaks if I delete the GCP load balancer’s forwarding rule?”

{
"cypher": "MATCH (o:Resource)-[:REF*1..6]->(r:Resource {key: $key}) RETURN DISTINCT o.key AS key, o.kind AS kind, o.scopeKey AS scope",
"params": "{\"key\": \"gcp/webRule\"}"
}

Driving it from an agent lists the other tools.

From a checkout of behold:

Command What it does
just ask-demo-record Boots the estate on emulators under e2e/lib/safe-env.sh, asks each question and prints a verdict line per question. A question with no answer is left out. Needs Docker, kind, kubectl, the aws CLI, choudoufu and plunge.
just ask-demo-refill Fills the prompts, reading lines and replies again from scripts/ask-demo/questions.ts, over the rows already recorded.
just ask-demo-read-real-aws --account <id> Run by a person signed in to that account, after npm i --no-save @aws-sdk/credential-providers@3. Makes two security groups in us-west-2, indexes them and deletes them, then writes the redacted index version. Refuses unless the region holds only default groups.
just ask-demo-deploy Builds dist-ask-demo/ and deploys it as a Cloudflare Worker.
just ask-demo-check [--url <url>] Plays a loop in headless Chrome, runs a visitor’s query and fails on a missing file, a request leaving the bundle or a content security policy violation.

The bundle’s policy allows 'unsafe-eval' for the engine’s WebAssembly bindings.

behold