Owlcast

M Warrick

Owlcast explores AI and the systems that power it, sharing what works, what doesn't, and what's still being figured out. Solo episodes, conversations with builders, and the Vibe Check series from Temporal. All working through what it actually takes to build today.

  1. Aug 11

    Vibe Check: Headscale Live — What Makes Code Proprietary?

    Watch the video version for the demos and screen shares: https://www.youtube.com/live/qqfcF3qHJ8g Kristoffer Dalby, co-maintainer of Headscale and Member of Technical Staff at Tailscale, joined Vibe Check to tackle a real hostname normalization bug in the Headscale repo using AI coding agents. We use Codex and Claude side by side to plan and implement a fix, then dig into the harder questions: who actually wrote this code, how do you review AI-generated PRs, and what's changing about open source maintenance now that contributors are shipping agent-generated pull requests. Topics covered: What Tailscale and Headscale do: mesh networking, direct connections, and self-hosted control planesHostname normalization bug: overly strict DNS validation stripping valid charactersUsing Codex and Claude together to plan and implement an open source fixAI-generated PRs and the maintainer review burden: solving symptoms vs. solving problemsCode ownership and attribution when agents write the codeContext window degradation and model reliability for coding tasksProperty-based testing with Claude (Antithesis-style)Integration testing as the primary test strategy in HeadscaleResources: Headscale: https://github.com/juanfont/headscaleHeadscale docs: https://headscale.net/stable/Tailscale: https://tailscale.com/Hostname normalization issues: https://github.com/juanfont/headscale/issues/2926 & https://github.com/juanfont/headscale/issues/3188Related PRs: https://github.com/juanfont/headscale/pull/2976 & https://github.com/juanfont/headscale/pull/3189Kristoffer's FOSDEM talk: https://fosdem.org/2026/schedule/event/KYQ3LL-headscale-the-complementary-open-source-clone/Originally streamed April 16, 2026 on Vibe Check Temporal YouTube channel and you can watch the full episode at: https://www.youtube.com/live/qqfcF3qHJ8g

    Vibe Check: Headscale Live — What Makes Code Proprietary?
  2. Aug 4

    Vibe Check: Deploying OpenClaw and Exploring Autonomous Systems in the Wild

    Watch the video version for the demos and screen shares: https://www.youtube.com/live/0q11SEogJFU In this livestream, Lizzie Siegel (Developer Advocate at DigitalOcean) demos OpenClaw — an open source autonomous agent framework that can take real actions, not just chat. Lizzie spins up OpenClaw on a DigitalOcean Droplet, connects it to WhatsApp as the UI, and breaks down how skills work, what's possible, and what to watch out for when agents can touch real infrastructure.* We go beyond the surface and explore: What OpenClaw is (and what "autonomous agent" actually means in practice)Why running agents on a contained VM (a Droplet) can be safer than giving access to your laptopHow OpenClaw differs from CoWork and why guardrails matterUsing WhatsApp as the interface (including what it looks like when you're "chatting with yourself")Hosting + setup basics: deploying from the marketplace, SSH'ing in, and choosing an LLM providerSkills and ClawHub: what a Skill.md is, how skills extend capabilities, and how people share themA real example skill: auto-booking reservations (and why it can cross into ToS/ethics territory)Risks + responsible use: automation, credential exposure, and where agents can go off the railsIf you're experimenting with autonomous agents, curious what it looks like to run them against real infrastructure, or deciding when you want agent autonomy vs workflow guardrails, this episode is for you. Resources: Lizzie's working end-to-end demo (7 min): https://www.youtube.com/watch?v=owyr56T86BARun OpenClaw on DigitalOcean (tutorial): https://www.digitalocean.com/community/tutorials/how-to-run-openclawClawHub (skills directory): https://clawhub.ai/Exposures Watchboard: https://openclaw.allegro.earth/Maton AI (connect Gmail/Drive/Calendar/Slack): https://www.maton.ai/Temporal for AI: https://temporal.io/solutions/aiHeads up: an API key was briefly visible during the stream and has since been revoked. Never share API keys publicly — treat them like passwords and rotate immediately if exposed.

    Vibe Check: Deploying OpenClaw and Exploring Autonomous Systems in the Wild
  3. Jul 28

    Vibe Check: What should an agent remember?

    > Watch the video version for the demos and screen shares: https://www.youtube.com/watch?v=VvaVzu_BjS0 What should an agent remember, and where should that memory actually live? Melanie sat down with Chris Gambill (Gambill Data) and Scott Haines (Databricks) to get concrete about agent memory: what belongs in the context window, what belongs in memory files, and what needs to live outside the agent entirely. Chris demoed OmniGent, the open source meta-harness from Databricks that runs multiple coding agents side by side. We watched it stand up a World Bank data pipeline into a medallion architecture, including a debate step where two models argue the approach before one goes and builds the plan. Scott walked through how he keeps sessions lean using a memory.md that points to the real source of truth instead of reloading the whole codebase, and why his context window stayed around 32k tokens instead of ballooning into the millions. From there we got into the parts that actually matter in production: - The three levels of memory: session, team or workspace, and organization-wide - Why hard security rules like "nothing gets pushed to main without a PR" belong outside the memory file, as an actual hook and not a suggestion - The idea the guests called "dreaming": agents summarizing their own sessions so the next one starts from the lessons, not the raw token history - Token usage as a signal: why token leaderboards are a bad productivity metric and what real ROI looks like (PRs opened and closed, healthier communities, actual contributions) - Multi-project and external memory: Postgres-backed sessions, sharing state through GitHub, and the risk of stale memory polluting a good result - Where autonomous agents and real money should still stop and ask first Resources - OmniGent (open source meta-harness from Databricks): https://omnigent.ai/ - Databricks: https://www.databricks.com/ - Chris Gambill, Gambill Data: https://gambilldata.com/ - Chris Gambill on YouTube (data engineering): https://www.youtube.com/@GambillDataEngineering - Scott Haines on YouTube (Conferences playlist): https://www.youtube.com/playlist?list=PLBJeAtDBQjJMANOGMxUd30nSIhdw9bcNt - Temporal orchestration for Open Lakehouse: https://www.openlakehouse.io/technologies/orchestration - Temporal, durable orchestration for AI agents: https://temporal.io --- Originally streamed July 22, 2026 on Vibe Check Temporal YouTube channel and you can watch the full episode at: https://www.youtube.com/watch?v=VvaVzu_BjS0

    Vibe Check: What should an agent remember?
  4. Jun 23

    Vibe Check: There's No Agent Without the Harness

    Watch the video version for the demos and screen shares: https://www.youtube.com/live/N8Z-XIs_m8k Episode description Melanie is joined by Elizabeth Fuentes Leone (AI Engineer & Developer Advocate at AWS) and co-host Shubham Londhe to make the case that there's no agent without the harness: the code and infrastructure around the model that turns it into something you can run in production. Elizabeth builds a harness from scratch with AWS Bedrock AgentCore in a single CLI command, then walks through the pieces that do the work and where durability fits in. In this episode: What a harness actually is: the agent loop plus the infrastructure that feeds the model and handles its outputBedrock vs. AgentCore, and swapping model providers (Bedrock, Anthropic, OpenAI, Gemini) by changing one model IDAgentCore's built-ins: an MCP tool gateway with semantic search, session and persistent user memory, and zero-config observabilityWhere Temporal fits (durable execution, retries, and state as a tool inside the loop) and why it complements, not replaces, LangGraph or LlamaIndex If you've built an agent that runs fine on your laptop and fell apart in production, this one's for you. Resources: Bedrock AgentCore: https://aws.amazon.com/bedrock/agentcore/AgentCore credits: https://events.elifuentes.tech/events/agentcore-harness/Elizabeth Fuentes Leone: https://elifuentes.tech/Shubham Londhe: https://www.trainwithshubham.com/Temporal on GitHub: https://github.com/temporalioHow Temporal uses Bedrock AgentCore: https://aws.amazon.com/blogs/apn/how-temporal-uses-amazon-bedrock-agentcore-to-create-robust-ai-systems/

    Vibe Check: There's No Agent Without the Harness

About

Owlcast explores AI and the systems that power it, sharing what works, what doesn't, and what's still being figured out. Solo episodes, conversations with builders, and the Vibe Check series from Temporal. All working through what it actually takes to build today.