Build Journal

Radio and Tavus Fixes with Local Fetch Improvements — September 4, 2026

I improved the radio and Tavus tools today, fixing bugs and enhancing local fetch capabilities for better agentic web interactions.

3 changes2 min readby Rob

What shipped

  • Radio Tool FixLucas live now uses the OWNED Interviewer persona for enhanced interactions.
  • Tavus UnblockIn-app frames for AISEO and Calendly booking are now accessible.
  • Local Fetch ImprovementImplemented untrackedFetch for better external data calls.

Today, I focused on enhancing the functionality of the radio and Tavus tools while also making some significant improvements to our local fetch capabilities. In just about an hour, I managed to ship three commits: one feature improvement and two critical bug fixes. It’s these small but impactful changes that drive the overall quality of the platform forward.

The first commit was a fix for the radio tool, specifically addressing the issue with Lucas live. Previously, it used a stock ID that didn't leverage the full capabilities of our OWNED Interviewer persona. This was a problem because it limited the engagement potential of the tool. After diving into the code, I realized that this persona could utilize 28 different tools, allowing for a richer interaction. The fix ensured that Lucas live now correctly employs this persona, which should significantly enhance the user's experience during live interactions.

Next, I turned my attention to the Tavus tool. Here, the issue was related to in-app frames, particularly with the AISEO board and Calendly booking functionalities being blocked. This was frustrating for users who needed seamless access to these features. I ground the Lucas radio-stage tools in the #SPACE interaction config, which not only unblocked these frames but also ensured that they now work harmoniously within the app. This fix consumed a bit more time than expected, but it was worth it to ensure a smoother user journey.

The final commit of the day was a feature improvement related to our local fetch capabilities. I implemented the untrackedFetch for render-path external calls, which allows for more efficient data retrieval. This change is particularly important because it complements the noindex purge follow-ups I had already initiated. By streamlining how we handle external calls, we can enhance the overall speed and responsiveness of our services. I’m excited to see how this will positively impact our agentic SEO efforts moving forward.

Reflecting on the progress, I’m reminded of the challenges of building this platform solo. Each bug I tackle, every feature I improve, feels like a small victory in a long journey toward creating a one-man-show company with a billion-dollar valuation. Working with Claude Code in VS Code has been a game-changer, allowing me to iterate quickly without the overhead of additional team members or tools. It’s a testament to what can be achieved with focused effort and the right technology at my disposal.

As I wrap up today’s work, I’m proud of the progress made but also aware of the ongoing challenges. The bugs I encountered today were frustrating but offered valuable lessons in debugging and improving the user experience. I’m committed to continuing this journey, learning from each setback, and pushing the boundaries of what’s possible with spatial AI and the agentic web. Here’s to more productive days ahead.

Terms in this entry#SPACETool / Tool call

← Back to the full build journal