Cursor — The Video Signal

Sep 21, 2026 · 10:06

Netlify's Dana Lawson: 'We Ain't Precious No More'

The landscape of software development is shifting from developer-centric to builder-centric, driven by AI agents. While agents enable non-technical users (Product Managers, designers) to open pull requests (PRs) and build applications, this transition introduces new challenges. Agents can fail by missing crucial product or design context, even when passing automated CI checks. Successful adoption requires platforms to be designed for these diverse 'builders' and necessitates that Product Managers evolve into 'agent orchestrators' who define the system's boundaries and ensure proper human control planes.

Key takeaways

Agent Failure Due to Context Loss 2:24
An agent, despite having access to skills, CI requirements, and passing automated checks, can fail by using a generic component (e.g., a generic React button) instead of a specific, context-aware component that holds critical requirements like accessibility patterns. (Marc Sloan, 00:00:24)
Non-Technical PR Merge Metrics 3:26
Across hundreds of organizations, 74% of PRs opened by non-technical individuals get merged, and 84% of those merge without any developer needing to push follow-up commits. (Tammuz Dubnov, 00:03:26)
The Builder Persona Shift 5:21
The platform is no longer built solely for developers. The rise of agents means that anyone—therapists, students, small business owners—can build, making the builder persona far broader. (Dana Lawson, 00:05:41)

Watch on YouTube Full article

Sep 16, 2026 · 1:26:58

The Watchdogs of AGI — Rune Kvist of AI Underwriting Company

The adoption of frontier AI is increasingly constrained not by capability, but by liability, risk, and trust. AI Underwriting Company (AIUC) proposes that the solution is a 'confidence infrastructure' built on rigorous standards and insurance. AIUC-1 is an emerging standard for agent security, safety, and reliability, requiring comprehensive testing against failures like jailbreaks, hallucinations, and data leaks. The model suggests that standards must precede insurance, and that a third-party body is needed to bridge the trust gap between frontier AI labs and conservative institutions like banks and governments.

Key takeaways

The Binding Constraint on AI Adoption 1:55
The primary hurdle for AI is not technical capability, but the lack of trust and clarity regarding liability. As AI agents become more autonomous and capable, the risk surface grows, necessitating external validation and risk quantification.
AIUC-1: The Standard for Agent Reliability 5:30
AIUC-1 is a comprehensive framework for agent security, safety, and reliability. It mandates technical controls, test controls, and policy controls, requiring quarterly updates to keep pace with the rapidly evolving AI landscape.
The Role of Confidence Infrastructure 7:30
The market requires a combination of standards (defining the rules) and insurance (quantifying and accepting the risk). Insurers are critical because they are financially incentivized to quantify risk truthfully, thereby creating a 'promise' that enables enterprise adoption.
Future Scope: Agents to Models to Robotics 8:20
The risk challenge will escalate across AI domains: from agents (AIUC-1) to models, and eventually to physical AI/robotics. The core challenge remains establishing a common, auditable standard across all modalities.

Watch on YouTube Full article

Sep 16, 2026 · 17:49

The Search Engine for the Agentic Web — Will Bryk, Exa

The talk introduces Exa, a search engine designed specifically for AI agents, arguing that traditional search engines (like Google) are fundamentally flawed because they are built for human recommendation rather than precise information retrieval. The core premise is that as AI systems become ubiquitous, the volume of searches issued by machines will surpass human searches by a thousandfold by 2026. Exa addresses this by providing a high-quality, customizable search API that enables agents to perform complex, database-like queries over the world's information, moving beyond simple keyword matching.

Key takeaways

AI Search Volume Prediction
The speaker predicts that in 2026, the number of searches issued by AI systems will exceed those issued by humans. This volume is expected to increase by a thousandfold in the following years, necessitating a specialized search infrastructure.
The Flaw of Recommendation Engines 5:10
Mainstream search engines are designed as recommendation engines, meaning they prioritize suggesting related content (e.g., 'shirts with stripes' when 'shirts without stripes' is queried) rather than providing exact, database-level answers. AI agents require the opposite: perfect retrieval.
The Perfect Search Thought Experiment 10:05
The ideal search involves running a Language Model (LLM) over a complex query and a document pair to determine a match. While this is highly accurate, scaling it to a trillion documents costs millions per query, making cost-optimization the primary engineering challenge.
The Business Catalyst 13:45
The company's business model was catalyzed when external users requested programmatic API access to their search engine, proving the need for an AI-focused search API, rather than just a consumer product.

Watch on YouTube Full article

Aug 26, 2026 · 18:49

Knowledge Systems: The New GTM Stack — Jeffrey Wang, Exa

Jeffrey Wang argues that Go-To-Market (GTM) strategy must be treated as an AI engineering problem. The core thesis is that GTM is fundamentally a data problem, requiring the creation of a 'live model of your world' that autonomous agents can act upon. He details systems like Exa (a search engine for agents), the ICP dashboard for classifying the Total Addressable Market (TAM), and Request Lens for real-time customer signal detection. Key architectural principles include making the system API-first, recognizing that consistent UIs still complement flexible chatbots, and prioritizing arbitrary customizability over rigid build vs. buy decisions.

Key takeaways

GTM as a Data Problem 4:56
The goal is to build a live model of the world—combining internal data (customer usage) with external data (web activity, company information)—that agents can programmatically act on. This shifts GTM from a purely sales function to an engineering challenge.
Agent-First Requires API-First 16:59
For any agent system (whether it's a GUI or a chatbot) to access data, the underlying systems must expose robust programmatic interfaces (APIs). This is critical for enabling agents to function.
System Components: ICP Dashboard & Request Lens 8:38
The ICP dashboard uses Exa's embeddings over the internet to classify every company in the TAM and estimate anticipated spend. Request Lens provides real-time alerts when significant customer signals occur (e.g., signups, search surges).
The Value of AI Cloning (Jeffbot) 13:42
An agent can be trained on historical data to mimic a user's professional style and decision-making. Jeffbot was built by analyzing 760 emails and hundreds of past decisions, creating 'evals' to calibrate its judgment against the founder’s own behavior.

Watch on YouTube Full article

Aug 4, 2026 · 1:01:23

Datadog Deleted All Its AI Context. It Worked.

Datadog detailed its journey scaling AI coding agents across 4,000 engineers, highlighting that performance improvements were achieved by deleting years of accumulated context files (context rot). The discussion emphasizes the critical role of building dedicated evaluation (evals) platforms to make data-driven decisions about model selection and agent capabilities. Key findings include using evals to replay historical PRs for code review guardrails and adapting hiring practices away from traditional LeetCode interviews toward real-world, large codebase tasks.

Key takeaways

Context Rot: Deleting Context Improved Performance 2:49
The team found that deleting old, accumulated AI context files (written prior to models like Sonnet 3.5) led to better evaluation scores, demonstrating 'context rot'—where historical information becomes irrelevant or harmful to the agent's performance.
Evals for Code Review and Regression Testing 5:49
The first concrete application of evals was building a platform that replays historical PRs known to have caused incidents, allowing agents to act as a last guardrail before production deployment.
Shift from Productivity to Ambition 59:02
The core lesson learned is that the goal of AI adoption should not solely be increasing productivity, but rather 'increasing ambition'—enabling teams to attempt and validate more complex ideas.
AI-Driven Interviewing 53:25
The process of hiring is evolving away from low-signal LeetCode interviews toward real-world scenarios that require AI to navigate and understand large, complex codebases.

Watch on YouTube Full article

Jul 31, 2026 · 1:01:49

Prompt-Jacking: The Rise of a New Supply Chain Risk - Kasimir Schulz & Kenneth Yeung

The talk details how AI coding assistants and agentic systems introduce novel supply chain risks by allowing attackers to compromise developers through hidden text or malicious prompts. Vulnerabilities are often found not in traditional code flaws but in the design of agents themselves. Key attack vectors include indirect prompt injection via raw file data (e.g., READMEs), exploiting tool call responses, manipulating control sequences, and abusing structured formats like JSON within automated pipelines.

Key takeaways

Inspect Raw Data Sources 2:00
When reviewing codebases or documentation, always check the raw markdown/HTML data (e.g., a README file) rather than just the pre-rendered view, as malicious payloads can be hidden in comments or unrendered sections.
Guardrails are Not Enough 10:30
While guardrails (LLM as a judge, classification models) are useful, they can be bypassed by advanced techniques like recursive prompt injection or token manipulation. Security must address architectural weaknesses beyond just the prompt.
Separate Control and Data Planes 17:45
A critical defense is ensuring a strict separation between system instructions (the control plane) and user/tool input data (the data plane). LLMs often fail to distinguish between these two, making this separation crucial for security.
Audit All Skills and Tools 28:00
When using agentic skills or tools (e.g., in OpenWebUI), audit the skill's name, description, and parameters, as these are often inserted into the system prompt at a high privilege level and can be exploited for injection.

Watch on YouTube Full article