Safety-Redacted Transcript - Slick

This public transcript is intentionally redacted. The source talk was a live product demonstration and included operational details for browser-native and desktop-adjacent agent control. Those sections have been replaced with safe summaries.

Attribution Note

The original metadata and transcript do not cleanly label every speaker. The listed speaker is Simon Maple, while the transcript suggests the on-stage presenter may be Lars. Use neutral attribution such as "the presenter" unless the question is specifically about the metadata.

Core Idea

The talk presents Slick as a browser-native agent experience. The presenter argues that skills can turn a theoretically powerful agent into a practically useful one by teaching it how to work with unfamiliar interfaces and task contexts.

Product Vocabulary

• Cone: the main user-facing agent surface.
• Sprinkles: small interface components shown alongside the conversation.
• Licks: events exchanged between interface components and the agent.
• Scoops: sub-agents delegated to focused tasks.
• Dips: lightweight interface fragments rendered in the conversation.

Demo Summary

The talk itself was delivered as a live Slick demonstration. The presenter used the product to show how an agent UI can generate temporary interfaces, run multiple focused helper agents, and respond to events from presentation components.

Architecture Summary

The talk describes a browser-centered architecture with a main agent loop, a UI shell, helper agents, and scoped tool access. It emphasizes that the agent can feel more useful when it shares context with the web interface the user is already using.

Operational protocol details, desktop application control paths, sensitive auth flows, public event wiring, and unsafe integration mechanics are not included in this public version.

Safety Lessons

• A browser-native agent needs explicit capability boundaries.
• UI events should be scoped, auditable, and user-visible.
• Sensitive auth material should not be exposed to the model.
• Integrations should be treated as privileged operations, not casual UI shortcuts.
• Demonstration convenience should not be mistaken for production safety.

Limits Of This Bundle

This redacted bundle supports product discussion and safety-aware architecture planning. It does not support reconstructing the original live demo or operational control mechanisms.