When performance bottlenecks force an architectural reckoning, the real challenge isn't moving code—it's defining data contracts. This episode explores the deep technical decisions behind migrating six client-side analyzers from a VS Code extension to cloud-based MCP agents. Discover why the transport layer is the easy part, and why understanding what context your agents actually need is the design problem that determines success. Learn how to approach this migration by starting with the data contract boundary rather than the infrastructure, and why losing direct workspace access forces you to rethink what 'quality analysis' means in a distributed system.

In this episode:
00:00 - The Performance Bottleneck: Six Analyzers Running Client-Side
00:08 - Architectural Identity Crisis: Cloud Layer vs. Local Processing
00:51 - The Real Cost of Migration: Losing Direct Workspace Access
01:13 - Data Contracts Over Infrastructure: The Hidden Design Problem
01:31 - Start with Context Boundaries, Not Code Migration

---
Copy this prompt into Cursor to start implementing:

Based on my podcast episode "Migrating Client-Side Analyzers to Cloud Agents: The Architecture Beyond the Code Move", help me:
- Understanding software architecture principles
- Best practices in code organization

Analyze my codebase, identify the relevant files, create a plan, then implement the changes.