Website command verification¶
Every displayed AgentEng command must be accepted by the CLI. The hero Orchestrator demonstrates agenteng connect a2a, agenteng connect mcp --transport http, and agenteng connect acp, then says βWelcome to AgentEng!β. These protocol commands print usable setup instructions; the animated website panels do not execute a shell or claim live connections.
Run python scripts/check-website-commands.py WEBSITE_REPO against a website checkout with Node dependencies installed. It reads public TypeScript literals using the AST, validates them against the actual CLI, and executes public lookup/setup commands. Server loops and coding sessions are parsed without launching them. Dynamic speaker-profile command rendering is covered by the speaker fixture and website tests.
The fixture contains 101 command locations. Tool CI executes each row and requires success. Update it when website commands change.
| Command | Website source (src/) |
|---|---|
agenteng --help |
components/FAQSection.tsx |
agenteng speakers |
pages/Agenda.tsx |
agenteng events --city london |
pages/London.tsx |
agenteng events --city san-francisco |
pages/SanFrancisco.tsx |
agenteng events --next san-francisco |
pages/SanFrancisco.tsx |
agenteng events --london --next |
pages/London.tsx |
agenteng events --london --history |
pages/London.tsx |
agenteng events --previous |
components/SFProofBand.tsx |
agenteng agenda --london |
pages/Agenda.tsx |
agenteng tickets --london |
components/TicketsSection.tsx |
agenteng sponsors --sf |
components/SponsorStrip.tsx |
agenteng inspect --speaker samuel-colvin |
components/SpeakerAgentActions.tsx |
agenteng --themes |
components/CoreThemesSection.tsx |
agenteng --list-disciplines |
components/WhatIsAgentEngSection.tsx |
agenteng --list-cities |
pages/AgentEngineeringHQ.tsx |
agenteng --info |
components/Footer.tsx |
agenteng whoami --chair |
components/FounderCLISection.tsx |
agenteng agenda --london |
components/AgendaPreviewSection.tsx |
agenteng event --london |
pages/London.tsx |
agenteng speakers |
components/SpeakersAnnouncedSection.tsx |
agenteng speakers |
pages/Speakers.tsx |
agenteng venue --london |
components/VenueSection.tsx |
agenteng agenda --london --topic memory |
components/ProgramTracksSection.tsx |
agenteng participate |
components/CTASection.tsx |
agenteng faq --search different |
components/WhyDifferentSection.tsx |
agenteng hq manifesto |
components/ManifestoSection.tsx |
agenteng hq mindset |
components/AgentEngineeringMindsetSection.tsx |
agenteng hq reading |
components/FurtherReadingSection.tsx |
agenteng hq |
components/HomeHeroSection.tsx |
agenteng events --sf --next |
pages/SanFrancisco.tsx |
agenteng events --city san-francisco |
pages/SanFrancisco.tsx |
agenteng event --london |
components/HeroSection.tsx |
agenteng hq mindset |
data/agent-activities.ts |
agenteng tools --discipline memory |
components/AgentToolingSection.tsx |
agenteng connect cursor |
components/AgentToolingSection.tsx |
agenteng --agent-to-agent (runs agenteng a2a-talks) |
pages/AgentToAgent.tsx |
agenteng connect a2a |
components/AgentToolingSection.tsx |
agenteng connect a2a |
data/agent-activities.ts |
agenteng participate |
data/agent-activities.ts |
agenteng hq reading |
data/agent-activities.ts |
agenteng event --london |
data/agent-activities.ts |
agenteng hq |
data/agent-activities.ts |
agenteng hq manifesto |
data/agent-activities.ts |
agenteng tools --discipline eval |
components/ProgramTracksSection.tsx |
agenteng tools --discipline protocol |
components/ProgramTracksSection.tsx |
agenteng tools --discipline protocol |
data/agent-activities.ts |
agenteng tools --discipline code |
components/ProgramTracksSection.tsx |
agenteng themes |
components/ProgramTracksSection.tsx |
agenteng themes |
data/agent-activities.ts |
agenteng agenda --london --topic memory |
data/agent-activities.ts |
agenteng speakers |
data/agent-activities.ts |
agenteng speakers |
data/speaker-stack.ts |
agenteng sponsors --sf |
data/agent-activities.ts |
agenteng venue --london |
data/agent-activities.ts |
agenteng connect mcp --transport http |
data/agent-activities.ts |
agenteng connect acp |
data/agent-activities.ts |
agenteng about |
data/agent-activities.ts |
agenteng disciplines |
data/agent-activities.ts |
agenteng events --london |
data/agent-activities.ts |
agenteng events --sf |
data/agent-activities.ts |
agenteng discover |
data/agent-activities.ts |
agenteng recordings |
data/agent-activities.ts |
agenteng events --sf --next |
data/agent-activities.ts |
agenteng event --sf |
data/agent-activities.ts |
agenteng agenda --london |
data/agent-activities.ts |
agenteng conduct |
data/agent-activities.ts |
agenteng tools --discipline harness |
data/agent-activities.ts |
agenteng talks --event agenteng-london-2026 |
data/agent-activities.ts |
agenteng about --chair |
data/agent-activities.ts |
agenteng about --organiser |
data/agent-activities.ts |
agenteng sponsors --london |
data/agent-activities.ts |
agenteng faq |
data/agent-activities.ts |
agenteng faq --search recorded |
data/agent-activities.ts |
agenteng speaker samuel-colvin |
data/speaker-stack.ts |
agenteng speaker andrey-breslav |
data/speaker-stack.ts |
agenteng speaker ismail-pelaseyed |
data/speaker-stack.ts |
agenteng speaker tobie-morgan-hitchcock |
data/speaker-stack.ts |
agenteng speaker alexander-korchagin |
data/speaker-stack.ts |
agenteng speaker jon-bratseth |
data/speaker-stack.ts |
agenteng speaker meryem-arik |
data/speaker-stack.ts |
agenteng speaker frederic-barthelet |
data/speaker-stack.ts |
agenteng speaker jocelyn-darcy |
data/speaker-stack.ts |
agenteng guide --london |
pages/Guide.tsx |
agenteng event --london |
pages/London2026.tsx |
agenteng gallery |
pages/Gallery.tsx |
agenteng event --london |
pages/AgentEngPage.tsx |
agenteng events --next san-francisco |
pages/AgentEngPage.tsx |
agenteng speakers |
pages/AgentEngPage.tsx |
agenteng agenda --london |
pages/AgentEngPage.tsx |
agenteng guide --london |
pages/AgentEngPage.tsx |
agenteng a2a-talks |
pages/AgentEngPage.tsx |
agenteng tools --discipline memory |
pages/AgentEngPage.tsx |
agenteng connect a2a |
pages/AgentEngPage.tsx |
agenteng connect mcp --transport http |
pages/AgentEngPage.tsx |
agenteng connect acp |
pages/AgentEngPage.tsx |
agenteng --info |
pages/AgentEngPage.tsx |
agenteng themes |
pages/SanFranciscoConference.tsx |
agenteng faq --search different |
pages/SanFranciscoConference.tsx |
agenteng speakers --city san-francisco |
pages/SanFranciscoConference.tsx |
agenteng events san-francisco --upcoming |
pages/SanFranciscoConference.tsx |
agenteng events --city san-francisco |
pages/SanFranciscoConference.tsx |
agenteng guide --london is shown as text on the /london-2026/guide page header, and agenteng gallery and agenteng event --london on /gallery and /london-2026, so they are listed by hand: the literal scanner only reads string literals, and skips literals that end like a sentence (such as the /agenteng meta description). components/TicketsSection.tsx still contains agenteng tickets --london, but the homepage no longer renders that section; the command keeps working and now reports the site's fully booked wording. The exporter fails if the homepage renders TicketsSection again, so the registration status is reviewed before the next export.
Personal agenda, bookmark, proposal and inbox commands are unsupported. Agenda topic filtering reads published programme text and creates no personal state.
Run python scripts/check-website-stability.py WEBSITE_REPO to verify public session/source IDs survive agenda reordering and duplicate IDs are rejected before export.
Agent-to-Agent (A2A) Talks¶
scripts/export-website.mjs reads src/data/agentToAgent.ts (session, title, YouTube ID, tag and duration) and the page copy in src/pages/AgentToAgent.tsx (title, intro and the exact disclaimer) into a2a_talks in the catalogue, with one a2a-talks source. The export fails if the data shape changes. These AI-generated videos are never exported as speakers or sessions; the gallery keeps them as kind: a2a rows marked AI-generated, which agenteng gallery lists only with --a2a or --city Online, last, and agenteng talks never lists, and general search and chat leave them out unless the question names A2A or Agent-to-Agent.
Site structure (London 2026 archive, talks, /agenteng)¶
The site moved the London 2026 conference under /london-2026. Catalogue sources and answers use the new URLs:
| Old URL | New URL |
|---|---|
/speakers |
/london-2026/speakers (speaker anchors #<slug>) |
/agenda |
/london-2026/agenda |
/guide |
/london-2026/guide |
/#venue, /#agenda, /#tickets |
/london-2026 |
/#faq (London FAQ) |
/london-2026#faq |
/#program (tracks) |
/london-2026#tracks |
The homepage still has #faq and #truly-yours; the old paths redirect on the site. Site main 8cd5a6a renamed the talks page to the gallery: /talks and /talks/<slug> now redirect to /gallery and /gallery/<slug>, and the catalogue holds no /talks URLs.
Pages mirrored:
| Page | Mirrored by |
|---|---|
/london-2026 and /london-2026/speakers, /agenda, /guide |
events, speakers, agenda, guide |
/london-2026/videos (welcome video iTV8VSrVJEk, then 9 talks marked coming soon) |
agenteng gallery --city London, agenteng recordings |
/gallery (London and San Francisco tabs) |
agenteng gallery |
/gallery/:slug |
agenteng gallery <slug> |
/agenteng (CLI page) |
the commands in the table above |
Data files read by scripts/export-website.mjs:
src/data/talks.ts: exportslondonVideos(the London welcome recording, then the 9 London talks),sfGallery(the Harness Engineering San Francisco event recap, kindevent-recap, slugsf-harness-engineering-2026-recap, with the site'ssummary; the site redirects the old/gallery/sf-harness-engineering-2026-full-eventandagenteng gallerystill accepts the old slug) andtalks(both, then the A2A talks)./galleryshowslondonVideosandsfGallery. Event recaps are their own kind: they are never labelled as talk recordings, and the Harness Engineering San Francisco sessions do not point to the recap as their recording. Each exported row has agallerytab (london,san-franciscoora2a), slug, title, kind, city, event, speaker, topics,youtube_id,transcript, status, AI-generated flag and its/gallery/<slug>URL, with one source each.talks.tsbuilds its rows from other data, so the exporter rebuilds them from the same literals (thelondonWelcomeandsfRecordingsliterals, agenda, speakers,sf-code-engineering.tsandagentToAgent.ts) and fails if the exports, the Gallery page or the mapping change, or if London or Code Engineering talks start publishing a YouTube ID or transcript, so a newly published recording is mirrored deliberately. No transcripts are published today, so none are exported. A2A rows use thea2a-talkssource kind, so general search leaves them out.codeEngineeringTalksintalks.tsis kept for the San Francisco events page only: the four Code Engineering San Francisco talks have no gallery page, so they are exported withgallery: nulland link to/san-francisco/events.src/data/sf-code-engineering.ts: roles, companies and links for the Code Engineering San Francisco (27 October 2026) speakers, checked against the SanFrancisco page roster.src/data/events.ts: next and previous editions (site_links.next_eventis Agent Engineering San Francisco, April 2027,/san-francisco;site_links.previous_eventis London 2026,/london-2026), plus each event'spage_url.site_linksalso holds/galleryand/london-2026/videos. The April 2027 conference is announced without a date or venue, so it is a link labelled "coming April 2027", not a catalogue event. The discovery prompt that used to read "Find the next Agent Engineering Conference in London" now followssite_links.next_event: "What is the next Agent Engineering event in San Francisco?", answered with the next published San Francisco event and "Agent Engineering San Francisco is coming April 2027".src/data/disciplines.ts: the site now lists 14 disciplines.agenteng disciplines(and the site formsagenteng --themesandagenteng --list-disciplines, plusagenteng themes --disciplines) lists all 14 in site order with directory tool counts; Factory Engineering and Decision Engineering are marked "no tool listings yet".agenteng themesstays the four London programme tracks. The tool directory keeps its twelve listed disciplines until tools are attributed to the new two.
San Francisco events and the 2027 conference¶
Site main 935f076 moved the San Francisco meetups and events to /san-francisco/events (still served by src/pages/SanFrancisco.tsx), and /san-francisco is now the Agent Engineering San Francisco 2027 conference page. Every San Francisco event link in the catalogue (the Code Engineering and Harness Engineering San Francisco events, their speakers, sessions, talks, event cards and sponsor sources) uses /san-francisco/events. The site's talks.ts still writes eventHref: "/san-francisco" for those rows, so the exporter maps it. Only the next-event link (site_links.next_event, "coming April 2027", from events.ts) stays /san-francisco. The exporter fails if /san-francisco/events stops routing to SanFrancisco.tsx. agenteng about lists both pages.
The command scanner reads each line of multi-line code blocks (such as the /agenteng examples) as its own command, drops an environment prefix (AGENTENG_OUTPUT=json) and anything after a pipe (| jq), and skips accessible labels (aria-label, alt, title) and prose. The check runs in a temporary directory, so commands that write files (agenteng bingo --format html --output bingo.html) leave the checkout untouched.
London 2026 team and the general /support page¶
Site PR #10 (main d39c1c6) moved the London 2026 support content (support options, organiser and supporters) from src/pages/Sponsors.tsx (/support) to src/pages/LondonTeam.tsx (/london-2026/team). /support is now a short general page. The exporter checks the support option titles and blurbs against LondonTeam.tsx, and their sources (support-refreshments, support-after-party, support-recording) use /london-2026/team, as does the sponsorship FAQ. Only the general enquiry source (sponsor-contact) stays on /support, guarded by its mailto link in Sponsors.tsx. The chair card with the organiser and associates (FounderCLISection.tsx) is rendered on /agent-engineering-hq, so the about source points there; the exporter fails if it moves. The hero tagline is still read from HeroSection.tsx.
Run python scripts/check-website-commands.py WEBSITE_REPO after each sync.