Repository navigation
docs: record the demo again with lox run - #82
Merged
Merged
Conversation
The demo showed the approval in the lockmq console, from before decisions moved to lockhub. It is now built from a recording of one real run (lockmq v0.10.0, lox v0.12.1, RabbitMQ 4.4.0): the lox run terminal captured at six moments, and the agent's calls and results. scripts/brand/demo.py reads the recording in scripts/brand/demo/ and types none of the terminals' text itself. README and site: the 'recorded before lockhub' caption is gone, the alt text lists the four steps. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
agent.json: the read's intent, recorded in French, is kept in an English translation and marked as such; run_order and answer_cut say what the run held and the image leaves out. The alt text attributes the connect question to the agent's first broker requests. demo.py's docstring lists what it composes on the left terminal. 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 #76
What changed
site/assets/demo.svgis recorded again: the human answers inlox run, not in the lockmq console. Four steps: the broker password typed inlox run, the first connection asked and approved there, a stream read approved by a rule (auto:actionin the feed), the messages back with the email masked.scripts/brand/demo.pyno longer types the terminals' text: it reads a recording kept inscripts/brand/demo/(sixlox runcaptures and the agent's calls and results) and only lays it out.site/index.html, which uses the same file;height640 → 590).docs/install.md: one line on where the recording lives.securityadded to the repository.Where each screen comes from
One real run on 2026-11-18, releases as a user installs them: lockmq v0.10.0 (image
ghcr.io/davidgodefroid/lockmq@sha256:08a8cf46…, signature verified bylox add), lox v0.12.1 (lockhub release binary), RabbitMQ 4.4.0 (rabbitmq:4-management) in Docker. Workspace~/shop, declared withlox add lockmq --name dev --url http://host.docker.internal:15676 --amqp-url amqp://host.docker.internal:5676 --vhost orders --user lockmq-ro --credentials ask, default rules, tierread. Fixture: vhostorderswithorder-events(stream, 3 JSON messages with a customer email, 2 consumers),orders.retry(classic, 1 consumer),orders.failed(quorum, 1204 messages, no consumer); userlockmq-rowith themonitoringtag.tmux capture-pane -eoflox run(106x22) during the run, committed asscripts/brand/demo/frames/*.ansi:1-password(the console's password question, relayed as a card),2-password-typed,3-serving,4-connect-question(the agent's first request),5-connected(aftery),6-read-auto(the stream read,auto:action ✓)lockmq_queuesandlockmq_readarguments, the queue rows, the message body with<redacted:r1.1>, the answerscripts/brand/demo/agent.json: the same run's agent side (Claude Code headless,claude -p, with the.mcp.jsonthatlox addwrote), results as the MCP server returned themWhat the script adds, and what it cuts (nothing else is written by hand):
└connectors.name type messages_ready N consumers N, four fields of the returned item (the full items are inagent.json). The message body is the returned JSON, wrapped after commas;… +2 messagesstands for the two other messages;…in thelockmq_readcall stands for itsintentargument.lockmq_statusandlockmq_streamcalls, the first-start policy review, alockmq_pii_addcall after the read, and the second paragraph of the answer, which reported that call's failure (see below).agent.jsonnames them incalls_not_shown.lox runframes are not consecutive: two intermediate captures are left out (the connect line before its✓, the read line before its✓).Verified
python3 scripts/brand/demo.py > site/assets/demo.svgreproduces the committed file; the SVG parses as XML.scripts/brand/render.mjs(resvg) at 16 s.sh scripts/hygiene.sh:hygiene: clean.prefers-reduced-motionstill pauses the image on a frame where everything shows (16 s).Seen during the recording, not part of this change
lockmq_pii_addfails underlox run:pii rules: open <workspace>/.lockmq/pii.toml: read-only file system(v0.10.0), so the mask rule a read proposes cannot be saved by the agent. The email was masked anyway (detectors).lockmq_readwithfrom: "last", count: 3returns one message (the last), not the last three; an agent asked for "the last 3 messages" needs a second read.lockmq initwrites still tells the agent to say "lox approve".🤖 Generated with Claude Code