# Episode 130: VCAIISO

Page: https://stenobird.com/podcast/msp-chat-6703058/episode-130-vcaiiso
Text version: https://stenobird.com/podcast/msp-chat-6703058/episode-130-vcaiiso.md
Podcast: [MSP Chat](https://stenobird.com/podcast/msp-chat-6703058)
Published: 2026-07-10T15:15:23+00:00
Episode link: https://www.spreaker.com/episode/episode-130-vcaiiso--72915706
Audio file: https://p.podderapp.com/2846285216/api.spreaker.com/download/episode/72915706/29a8f83d_9172_47dd_9072_1d17c5ce84b1.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/msp-chat-6703058/episodes/episode-130-vcaiiso
Duration seconds: 3788

## Resource

Erick and Rich discuss why service desk automation startup Squash believes there’s a close connection between AI automation for MSPs and governance and why they’re probably correct, as well as three steps MSPs can take to ready tomorrow’s generation of leaders today. Then they’re joined by Arve Kjoelen for a timely conversation about the security implications for MSPs and their customers posed by leading-edge LLMs like Mythos and GPT-5.6. And finally, one last thing: how two joy-riding teens discovered the hard way that the long arm of the law extends into Waymos. Discussed in this episode: It’s Governance First, AI Second at Squash Police detain 2 teens after a joy ride in a Waymo in Northern California Some guests on this podcast are clients of Channel Mastered. Compensation plays no part in their appearance or the content of the discussion unless the episode they appear on is a “bonus episode” explicitly labeled as sponsored.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/msp-chat-6703058/episodes/episode-130-vcaiiso/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/msp-chat-6703058/episode-130-vcaiiso.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.