README: give the agent a model, and if it goes wrong #13

New issue

Closed

opened 2026-10-11 15:52:52 +01:00 by vnprc-agent · 1 comment

vnprc-agent commented

2026-10-11 15:52:52 +01:00

The deploy README is the public home of the start-here page: it already explains the install script and the forge step, and it stops at ssh allod-dev. Two sections finish it.

Primary goals:

Give the agent a model — the quick way, pi-key nullsink inside the VM (or piped from the host: ssh allod-dev pi-key nullsink < ~/nullsink-key), and the durable way, pi-provider add nullsink on the host with its two commits, the re-lock, and rebuild-vm allod-dev; what each leaves on the VM (a key file, or nothing).
If it goes wrong — the short list a stranger needs: check the prompt (host versus VM), rerunning the script is safe, the unexpected end-of-file retry on provision-vm, the root login fallback after the reboot, Virtual Machine Manager opening empty.
One page — a reader who lands on the org front page and clicks deploy gets the whole path with nothing left to look up.

Current state and specifics

README.md has "Getting started" and "Giving the dev VM its own forge". The draft of the two missing sections exists privately and has been walked on real hardware; the public text is a sanitized copy of it (no hostnames beyond the public forge, no private paths).

Scope

In: the two sections, each with its command block. Out: the install script, the org front page, anything about keys for providers other than nullsink and the two subscription logins.

The deploy README is the public home of the start-here page: it already explains the install script and the forge step, and it stops at `ssh allod-dev`. Two sections finish it. Primary goals: - **Give the agent a model** — the quick way, `pi-key nullsink` inside the VM (or piped from the host: `ssh allod-dev pi-key nullsink < ~/nullsink-key`), and the durable way, `pi-provider add nullsink` on the host with its two commits, the re-lock, and `rebuild-vm allod-dev`; what each leaves on the VM (a key file, or nothing). - **If it goes wrong** — the short list a stranger needs: check the prompt (host versus VM), rerunning the script is safe, the `unexpected end-of-file` retry on `provision-vm`, the root login fallback after the reboot, Virtual Machine Manager opening empty. - **One page** — a reader who lands on the org front page and clicks `deploy` gets the whole path with nothing left to look up. ### Current state and specifics `README.md` has "Getting started" and "Giving the dev VM its own forge". The draft of the two missing sections exists privately and has been walked on real hardware; the public text is a sanitized copy of it (no hostnames beyond the public forge, no private paths). ### Scope In: the two sections, each with its command block. Out: the install script, the org front page, anything about keys for providers other than nullsink and the two subscription logins.

vnprc referenced this issue from a commit

2026-10-11 16:14:35 +01:00

README: give the agent a model, and if it goes wrong

allod-agent added the

landed?

label

2026-10-21 22:27:16 +01:00

allod-agent commented

2026-10-21 23:32:27 +01:00

Member

Landed on master in commit d72a6eb: the README sections for giving the agent a model and if it goes wrong. Verified against the files on master today; closing as completed.

Landed on master in commit d72a6eb: the README sections for giving the agent a model and if it goes wrong. Verified against the files on master today; closing as completed.

allod-agent

2026-10-21 23:32:28 +01:00