Skip to content

docs: redraw the demo with the approval in lox run (#91) - #93

Merged
DavidGodefroid merged 2 commits into
mainfrom
docs/91-demo-lox-run
Nov 18, 2026
Merged

DavidGodefroid merged 2 commits into
mainfrom
docs/91-demo-lox-run

Conversation

@DavidGodefroid

Copy link
Copy Markdown
Owner

Closes #91

What changed

  • site/assets/demo.svg is redrawn (scripts/demo-svg.py): the agent plans and hears pending, the plan shows as a question in lox run, you open its details and press y, the agent runs the ticket, the lockfile console fetches the file and runs the three plugins in the sandbox, and three 1s go back.
  • New scripts/demo-lox-run.json: the five lox run frames the demo shows, as lockhub's renderer drew them (text and SGR styles).
  • README: the "Drawn before approvals moved to lockhub" caption is removed; the alt text lists each step.
  • Site (site/index.html): same alt text, the caption no longer says the demo predates lockhub, and the image's height follows the new 1200x710 drawing.
  • Topic security added to the repository (gh repo edit --add-topic security); topics are now ai-agents, harness-security, mcp, security.

Where each screen comes from

Nothing on screen is typed by hand except the agent's closing remark and the captions under the picture. This is not a recording of a live lox run session: each screen is produced by the code that draws it, run on the demo's plan.

Screen Source
The ticket's screen (file plan · 3 answers, the key, each plugin's question and the meaning of 1 and 0, this plan reveals at most 3 answers about the file, the sha256 … · 686 bytes line, the masked key invoices/j***(20)/2026-10.pdf, touched: email) lockfile origin/main (b6645cf), internal/backend: planScreen then hubScreens (lockkit v0.20.0 render.MaskScreen), called from a throwaway test with the key invoices/jane.doe@example.com/2026-10.pdf, the intent, and the three plugin.toml manifests of lockfile-marketplace origin/main (cee1c23). The sha256 and size are those of a real two-page PDF (one page blank) made for the demo.
The lox run terminal (header, question card collapsed and with details, why asked: this lock's ticket does not name its kind (version 1): asked, the feed line with ask:v1, ✔ you, ✔ you ✓, the key footer) lockhub origin/main (4d94ef1), internal/loxrun: a real Session on a 92x25 colour terminal (the package's own test harness: fake hub queue, signed ticket), fed a version-1 read_pii ticket of lock lockfile, instance files, agent dev-1, built as lockkit's console.hubApprover.Submit builds a plan's ticket, carrying the screen above. Keys sent: d, then y; then the hub state consumed. The frames written to the terminal are stored as they came, in scripts/demo-lox-run.json.
lockfile plan --key … --plugin … --intent … and lockfile run TICKET docs/usage.md, the agent-side command table.
Pending human approval: ticket … on lockfile. Do not retry. End your turn; you will be told when it is decided. lockkit v0.20.0 mcpkit.PendingText, which cmd/lockfile prints for a pending plan (fail in agent.go). One line in the CLI; wrapped in the picture as a terminal wraps it. The ticket id is the one of the captured session.
handle f_G9Qf4otbDr, file.non-empty@1.0.0: 1, pdf.parses@1.0.0: 1, pdf.has-blank-page@1.0.0: 1 The format is resultLines in cmd/lockfile/agent.go; the handle is one value of workspace.newHandle; the three answers are what the three plugins, built from lockfile-marketplace (local main, whose sources of these plugins equal origin/main but for pdf.parses' go.mod/go.sum), print on fd 1 when given that PDF on fd 3.
local, /srv/lockfile/samples, fd 3 read-only · no network · 3-byte stdout docs/usage.md (the samples profile), docs/security-model.md (the plugin row). Unchanged claims, path corrected to the documented one.

Limits of this method, for the reviewer:

  • The lox run header shows no locks line and no lock tabs: the harness session follows no lock console, as a lox run that reaches the consoles would. The timestamp is the capture's.
  • The box-drawing characters of the frames are drawn as SVG strokes at their cell positions so the card's frame joins in any font; the characters themselves are in the JSON.
  • The colours are this demo's palette applied to lockhub's SGR roles (internal/loxrun/style.go), not a terminal theme.
  • The old handle f_8Kq2xR had a shape the code never produces (handles are f_ + 10 characters); fixed.

Verification

  • python3 scripts/demo-svg.py > site/assets/demo.svg reproduces the committed file.
  • python3 scripts/check-site.py site : 7 pages checked, 0 errors.
  • Rendered in headless Chrome at each step (stills below; the animation is paused at the given second).

Before (main):

before

After, at 1.5 s, 3.5 s, 6 s, 7.7 s, 10.5 s and 15.5 s:

1.5
3.5
6
7.7
10.5
15.5

🤖 Generated with Claude Code

DavidGodefroid and others added 2 commits November 18, 2026 12:08
The demo's lox run terminal is now lockhub's own frames (scripts/demo-lox-run.json),
fed the ticket lockfile makes of the plan; the agent side shows plan, pending, run
and the answers as the CLI prints them. The README caption that said the demo
predated lockhub is gone, and the alt text lists each step.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The capture note (lockhub commit, lockkit version, test harness, the header lines a
live session adds) is in the generator's docstring and in the JSON's note key; the
reduced-motion still is the approval card.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@DavidGodefroid
DavidGodefroid merged commit 007f635 into main Nov 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Re-record the demo with lox run and add the security topic

1 participant