CI/CD — The Video Signal

Aug 10, 2026 · 10:39

Create an agent that can browse the web with Managed Deep Agents and Browserbase's Stagehand

This video demonstrates building a production-ready web browsing agent by integrating Managed Deep Agents (LangSmith) with Stagehand v4 and BrowserStack. The resulting agent can interact with live websites—performing actions like scrolling, clicking, and navigating—using specialized tools exposed by Stagehand to connect the AI model to scalable browser infrastructure.

Key takeaways

Agent Architecture Overview
The solution uses Managed Deep Agents as the core agent harness (LangSmith), which is augmented with tools from Stagehand v4. Stagehand, in turn, connects to web browsing infrastructure provided by BrowserStack for production-grade scalability.
Stagehand V4 Tools 3:57
The agent is given three core tools from Stagehand: `screenshot` (visually inspects the rendered page), `snapshot` (inspects the active page and hydrates element IDs for simple interactions), and `run` (accepts snapshot actions or JavaScript via the Playwright-shaped page API, ideal for multi-step workflows).
Development Workflow (Local vs. Production) 6:00
The development process involves running `mda dev` locally to test the agent in a managed deep agent studio environment. For production, the deployment is finalized using `mda deploy`, which creates a serverless deployment within LangSmith's Context Hub.

Watch on YouTube Full article

Aug 7, 2026 · 17:30

Open Source Is Dead. Long Live Open Source. — Saoud Rizwan, Cline

The speaker argues that while traditional open source community models are struggling due to AI-driven skepticism and supply chain risks, the future of software development lies in 'open weights' models. The economic imperative is shifting away from raw intelligence toward cost efficiency and standardization. Examples like the compromise of the Litellm package and the comparison between GLM and Opus demonstrate that open weights models can achieve production-grade results at a significantly lower cost, mirroring historical commoditization events like Open Compute.

Key takeaways

Open Source Trust Crisis 2:05
The community trust model is eroding. Examples include Zig banning AI use in PRs/issues to protect contributors, curl considering ending its bug bounty program due to AI-generated reports, and tldraw automatically closing pull requests. GitHub even shipped a feature to disable third-party PRs altogether. (0:38)
Supply Chain Risk Highlighted by Litellm Attack 7:00
The Python package litellm (3.5 million daily downloads) was compromised for three hours, installing a credential harvester to steal API keys, SSH keys, and crypto keys, along with a remote command execution backdoor. The attack was only caught due to a bug in the malware that crashed Cursor. (4:20)
Open Weights Models Drive Cost Efficiency
Testing showed GLM outperformed Opus on a real client bug by cleaning up dead code and confirming compilation, even though it used twice the tokens, because its cost was half that of Opus. This demonstrates that cost efficiency is becoming more critical than raw speed or intelligence. (13:05)
The Open Compute Precedent
Facebook's decision to open source its data center designs led the entire supply chain to standardize on those schematics, commoditizing components and driving down costs for all participants, including Facebook itself. (16:20)

Watch on YouTube Full article

Jul 29, 2026 · 16:24

We Vetted 2000 AI Skills Before They Reached Developers — Lucas Palma, Nubank

Lucas Palma details how Nubank addressed AI skills—which function like supply chain dependencies—being a significant security risk in a regulated financial environment. To mitigate this, they built 'Skill Vector,' a comprehensive security review system that sits between the skill and the internal marketplace. This system vets every skill using a hybrid approach: deterministic checks (e.g., regex for unsafe instructions) followed by LLM analysis to assess context and behavior before granting permissions or allowing deployment.

Key takeaways

Treat AI Skills as Dependencies
AI skills must be treated like any other software dependency, requiring rigorous vetting and security gates, rather than just configuration files.
Hybrid Security Scanning is Essential 12:17
The most effective approach combines deterministic checks (for easy risks) with LLM review (for contextual behavior analysis), ensuring comprehensive coverage.
Security Gates Must Be Comprehensive
Vetting must cover the entire workflow, including local developer testing, CI/CD steps, PR feedback, and integration into a formal vulnerability management program.

Watch on YouTube Full article

Jul 27, 2026 · 53:34

Harness Engineering: Building an AI Software Factory

Harness engineering is a discipline focused on building automated loops of checks and maintenance agents that allow teams to delegate increasing amounts of codebase development to AI. The goal is not merely higher velocity, but achieving higher quality by shifting from manual code review (the primary bottleneck) to systematic process oversight. This involves tracking three key dimensions—autonomy, automation, and quality—and implementing layered validation systems: the Inner Loop (unit tests/linters), Outer Loop (agentic QA/UI testing), and Meta Loop (maintenance agents that analyze historical data for systemic improvements).

Key takeaways

The Three Dimensions of Agent Adoption 10:39
When adopting AI agents, track three metrics: Autonomy (how many human course corrections are needed); Automation (the level of oversight required, indicating trust); and Quality (ensuring the shipped product remains high quality). Progressing requires improving these dimensions sequentially.
The Three Loops of Harness Engineering 19:04
1. Inner Loop (Autonomy): Focuses on cheap, frequent checks like pedantic linting or unit tests to ensure agents get it right the first time. 2. Outer Loop (Automation): Involves slower, in-depth checks, such as agentic code review or running the product through a UI/CLI. 3. Meta Loop: Utilizes maintenance agents that analyze historical data (CI logs, PR comments) to propose systemic fixes and improvements to the entire process.
The Primary Barrier is Organizational 28:20
Harness engineering is fundamentally an organizational transformation, not just a technical one. Success requires changing workflows—for example, moving from monolithic PRs to smaller, low-risk chunks that can auto-merge, thereby shifting human behavior toward better practices.

Watch on YouTube Full article

Jul 17, 2026 · 8:53

Antigravity Arcade: From prompt to game in minutes

The video details 'Antigravity Arcade,' a system that leverages AI skills and workflows to allow users to generate functional web games from simple ideas without writing code. The solution covers both the front-end game generation process—which enforces visual consistency using specialized AI skills (e.g., ensuring retro aesthetics, handling physical input)—and a robust back-end deployment pipeline for hosting these user-generated games on physical arcade cabinets.

Key takeaways

AI-Powered Game Generation 3:30
Antigravity uses modular 'skills' to guide the AI agent, preventing context window bloat and ensuring adherence to organizational best practices (e.g., consistent retro aesthetic, specific key mappings) when generating game code.
Consistent Development Workflow 4:13
The project enforced consistency by using a starting template built with Phaser JS's game engine, which included skills for visual guidelines (black background, CRT shader) and input handling to ensure cross-platform compatibility.
Secure Deployment Pipeline 6:45
A custom deployer CLI tool handles the deployment of user code to physical arcade cabinets. This process uses a Unix setuid model API to securely read sensitive API tokens without exposing them to the end-user or agent, followed by Cloud Run validation and GCS storage.
Automated Game Moderation 8:02
Upon successful upload, an Eventarc trigger spins up a Cloud Run function that validates the game. If approved, Firestore increments a counter, issuing a sequential ID for moderation via a web app.

Watch on YouTube Full article

Jul 13, 2026 · 34:18

FORGET Loop Engineering. Agentic Engineering is about THIS

The video argues that 'Loop Engineering' is an insufficient and inaccurate mental model for modern software development with AI agents. The superior approach is **Agentic Engineering**, which focuses on building complex AI developer workflows (ADWs) within a 'software factory.' These ADWs orchestrate three core actors of value creation—Engineers, Agents, and Code—to automate the entire development lifecycle, from planning to deployment, thereby scaling impact and accelerating development far beyond what simple loops can achieve.

Key takeaways

Shift Focus from Loops to Workflows
Loop engineering is a poor rebrand of the Software Development Life Cycle (SDLC). The focus must be on building comprehensive AI developer workflows that combine code execution with agents, rather than focusing solely on iterative loops.
The Three Actors of Value Creation 2:00
Successful agentic engineering requires understanding and strategically placing three actors: the human engineer, specialized AI agents, and deterministic code. Code is highlighted as the most reliable actor because it costs zero tokens and runs consistently.
Scaling Developer Workflows 4:00
Advanced workflows move beyond simple loops by integrating multiple validation steps (e.g., linting, type checking, formatting) and scaling compute through specialized sandboxes for parallel execution. This process is the core of building a 'software factory.'
Meta-Engineering: Building the System 8:00
The most valuable engineering effort is not working on the application layer, but performing meta-work on the agentic layer—building the system that orchestrates and manages all other components (the 'system that builds the system').

Watch on YouTube Full article