A new direction for AI developer tooling (Friends)
Episode
89 min
Read time
2 min
Topics
Productivity, Leadership, Artificial Intelligence
AI-Generated Summary
Key Takeaways
- ✓Local-First Architecture: Tidewave runs on localhost rather than remote servers, accessing your actual browser session and development environment. This allows the agent to use existing authentication, database connections, and framework configurations without separate MCP setup or credential management.
- ✓Browser-Based Verification: The agent executes JavaScript directly on the page to test implementations, automatically scrolling to validate autoplay features and running database queries to confirm data persistence. This creates a verification loop where agents test their own work before declaring completion.
- ✓Context Pruning Strategy: When context windows fill, Tidewave prunes tool outputs from early conversation stages rather than summarizing everything. This preserves recent context accuracy while extending conversation length, allowing developers to have meta-conversations with the agent about available tools and capabilities.
- ✓Framework Integration Over MCPs: Instead of installing multiple MCP servers for database access, GitHub integration, or documentation, Tidewave leverages existing framework capabilities. The agent uses code execution within the web application context, accessing documentation bundled with exact dependency versions rather than potentially outdated remote sources.
- ✓Productivity Through Specialization: Developers gain measurable productivity by identifying specific use cases where agents excel versus fail. Valim avoids using agents for Elixir type system work but successfully uses them to translate features between frameworks, skipping redundant tests and mocks while maintaining quality through proper verification loops.
What It Covers
Jose Valim discusses Tidewave, a local coding agent for full-stack web applications that runs in the browser alongside your development environment, integrating tightly with Phoenix, Rails, and other frameworks for real-time verification and testing.
Key Questions Answered
- •Local-First Architecture: Tidewave runs on localhost rather than remote servers, accessing your actual browser session and development environment. This allows the agent to use existing authentication, database connections, and framework configurations without separate MCP setup or credential management.
- •Browser-Based Verification: The agent executes JavaScript directly on the page to test implementations, automatically scrolling to validate autoplay features and running database queries to confirm data persistence. This creates a verification loop where agents test their own work before declaring completion.
- •Context Pruning Strategy: When context windows fill, Tidewave prunes tool outputs from early conversation stages rather than summarizing everything. This preserves recent context accuracy while extending conversation length, allowing developers to have meta-conversations with the agent about available tools and capabilities.
- •Framework Integration Over MCPs: Instead of installing multiple MCP servers for database access, GitHub integration, or documentation, Tidewave leverages existing framework capabilities. The agent uses code execution within the web application context, accessing documentation bundled with exact dependency versions rather than potentially outdated remote sources.
- •Productivity Through Specialization: Developers gain measurable productivity by identifying specific use cases where agents excel versus fail. Valim avoids using agents for Elixir type system work but successfully uses them to translate features between frameworks, skipping redundant tests and mocks while maintaining quality through proper verification loops.
Notable Moment
Valim demonstrates how developers can trick coding agents by asking hypothetical questions about nonexistent tools. The agent imagines the tool exists, attempts to invoke it, then crashes when discovering the tool is fictional—revealing fundamental limitations in current agent reasoning capabilities.
You just read a 3-minute summary of a 86-minute episode.
Get The Changelog summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from The Changelog
From open source hits to OpenAI (Interview)
Jun 5 · 106 min
Latent Space
Why Video Agent models are next — Ethan He, xAI Grok Imagine
Jun 1
More from The Changelog
MCP on Code Mode (Interview)
May 15 · 114 min
All-In with Chamath, Jason, Sacks & Friedberg
Jensen Huang LIVE: Nvidia's Future, Physical AI, Rise of the Agent, Inference Explosion, AI PR Crisis
Mar 19
More from The Changelog
We summarize every new episode. Want them in your inbox?
Similar Episodes
Related episodes from other podcasts
Latent Space
Jun 1
Why Video Agent models are next — Ethan He, xAI Grok Imagine
All-In with Chamath, Jason, Sacks & Friedberg
Mar 19
Jensen Huang LIVE: Nvidia's Future, Physical AI, Rise of the Agent, Inference Explosion, AI PR Crisis
Latent Space
Mar 17
Why Anthropic Thinks AI Should Have Its Own Computer — Felix Rieseberg of Claude Cowork & Claude Code Desktop
The AI Breakdown
Mar 12
What Vibe Coding is Turning Into
NVIDIA AI Podcast
Mar 12
Building AI Factories: How Red Hat and NVIDIA Turn Enterprise Data Into Intelligence - Ep. 293
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into The Changelog.
Every Monday, we deliver AI summaries of the latest episodes from The Changelog and 192+ other podcasts. Free for up to 3 shows.
Start My Monday DigestNo credit card · Unsubscribe anytime