Repository navigation
docs: redraw the demo with the approval in lox run (#91) - #93
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #91
What changed
site/assets/demo.svgis redrawn (scripts/demo-svg.py): the agent plans and hearspending, the plan shows as a question inlox run, you open its details and pressy, the agent runs the ticket, the lockfile console fetches the file and runs the three plugins in the sandbox, and three1s go back.scripts/demo-lox-run.json: the fivelox runframes the demo shows, as lockhub's renderer drew them (text and SGR styles).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.securityadded to the repository (gh repo edit --add-topic security); topics are nowai-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 runsession: each screen is produced by the code that draws it, run on the demo's plan.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, thesha256 … · 686 bytesline, the masked keyinvoices/j***(20)/2026-10.pdf,touched: email)origin/main(b6645cf),internal/backend:planScreenthenhubScreens(lockkit v0.20.0render.MaskScreen), called from a throwaway test with the keyinvoices/jane.doe@example.com/2026-10.pdf, the intent, and the threeplugin.tomlmanifests of lockfile-marketplaceorigin/main(cee1c23). The sha256 and size are those of a real two-page PDF (one page blank) made for the demo.lox runterminal (header, question card collapsed and with details,why asked: this lock's ticket does not name its kind (version 1): asked, the feed line withask:v1,✔ you,✔ you ✓, the key footer)origin/main(4d94ef1),internal/loxrun: a realSessionon a 92x25 colour terminal (the package's own test harness: fake hub queue, signed ticket), fed a version-1read_piiticket of locklockfile, instancefiles, agentdev-1, built as lockkit'sconsole.hubApprover.Submitbuilds a plan's ticket, carrying the screen above. Keys sent:d, theny; then the hub stateconsumed. The frames written to the terminal are stored as they came, inscripts/demo-lox-run.json.lockfile plan --key … --plugin … --intent …andlockfile run TICKETdocs/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.mcpkit.PendingText, whichcmd/lockfileprints for a pending plan (failinagent.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: 1resultLinesincmd/lockfile/agent.go; the handle is one value ofworkspace.newHandle; the three answers are what the three plugins, built from lockfile-marketplace (local main, whose sources of these plugins equalorigin/mainbut 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 stdoutdocs/usage.md(thesamplesprofile),docs/security-model.md(the plugin row). Unchanged claims, path corrected to the documented one.Limits of this method, for the reviewer:
lox runheader shows nolocksline and no lock tabs: the harness session follows no lock console, as alox runthat reaches the consoles would. The timestamp is the capture's.internal/loxrun/style.go), not a terminal theme.f_8Kq2xRhad a shape the code never produces (handles aref_+ 10 characters); fixed.Verification
python3 scripts/demo-svg.py > site/assets/demo.svgreproduces the committed file.python3 scripts/check-site.py site:7 pages checked, 0 errors.Before (main):
After, at 1.5 s, 3.5 s, 6 s, 7.7 s, 10.5 s and 15.5 s:
🤖 Generated with Claude Code