AI Native DevCon 2026 London — all conference sessions as interactive skills
66
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
… (see transcript.md)
⚠️ Attribution warning. This transcript has no per-speaker labels. The session involves at least three voices: an MC/introducer, Davide Eynard, and Peter Wilson. The transcript explicitly identifies one transition ("So I'm Davide, he's speaker") but otherwise attribution is ambiguous. When quoting, prefer "one of the presenters said..." unless context disambiguates. Do not invent attributions.
Participants referenced in metadata:
- Peter Wilson (Staff Engineer, Mozilla.ai)
- Davide Eynard (Staff ML Engineer, Mozilla.ai)
⚠️ Transcript scope. The supplied transcript covers only the opening minutes (introduction and Mozilla Manifesto framing). It does not contain the cq design, implementation, lessons learned, or future-direction content promised in the abstract.
Hi. Everyone. All right. Thank you for coming. Really. Cool session. Coming up. Just now. We've got Peter Wilson at the meeting at the. CQ. Stock. Overload for agents. I don't know if you've seen contributions to human stack overflow. Basically plummeted after chat gbt came out, which is really sad for all of us. Hopefully these two can do something about it. Kids have a round of applause, please.
So I'm Davide, he's speaker. We're both from moz://a.ai. The first thing I wanted to start with was because the first thing they usually people tell us is are you the firefox guys? Or are you the browser? Guys? We don't want AI in the browser and things like that. Or we have very heavy graph. This doesn't happen that often.
moz://a URI demoSo that's the next exercise for you for after the talk. If you have application installed on your laptops, try and connect to moz://a.ai slash slash a. It is kind of fake URI, but the browser folks can do anything they want with it. So you just connect to that URL and it will open the xenomony faster, which is the manifesto that has been set up like 20-ish years ago when the internet was had. So let's say it's very beginning, it's from the user perspective. It kind of began even 25 more years early.
So in that manifest, you find some principles that all about the internet, the web as a resource that was open, that shouldn't remain open, etc. And where people should be able to drive the experience they have of the web, where security is important. And we're open code and the standards and interoperability are very important.
[End of supplied transcript. The remainder of the session — covering the cq idea, how it works today, lessons learned, and future direction — was not included in the source material provided to this skill.]
.tessl-plugin
talk-batey-building-product-teams-age-of-ai
talk-birgitta-closing-keynote
talk-debois-agent-enablement
talk-douglas-training-ai-on-your-own-code
talk-dubnov-merge-rate-ai-adoption
talk-farley-vibe-coding-best-we-can-do
talk-firtman-web-mcp-agentic-web
talk-foxwell-reinvention-dev-team
talk-graziano-spec-driven-development
talk-groetzinger-skills-everywhere
talk-jones-odevo-ai-native-transformation
talk-jourdan-pipelines-to-prompts
talk-katsioloudes-code-security-ai
talk-lamis-context-engineering-dreaming
talk-lawson-agent-experience
talk-luebken-embedding-pi-coding-agent
talk-maleix-collective-intelligence
talk-marsden-agent-desktops
talk-martinelli-spec-driven-development
talk-moss-skills-team-workflow
talk-overweg-one-brain-no-filtering
talk-podjarny-skills-are-the-new-code
talk-roberts-ai-native-brownfield
talk-roberts-brownfield-ai-native
talk-scheire-artificial-intelligence
talk-selajev-docker-sandboxes-agents
talk-sloan-harness-engineering-beyond-code
talk-stack-humans-architect-ai-writes-code
talk-stoneham-product-brain
talk-tal-skills-security
talk-thomas-ai-native-engineering
talk-walter-runtime-intelligence-agents
talk-wilson-cq-stack-overflow-for-agents
talk-wotherspoon-humans-vs-slop