GIGIlistening…

Build Journal

GIGI AI Concierge Speech Improvements & Faster Turns — May 14, 2026

I improved GIGI AI's speech handling and response times, tackling truncation issues and optimizing prompt efficiency for better user experience.

2 changes3 min readby Rob

What shipped

  • Improved Speech HandlingEliminated speech cutoffs by reverting fire-and-forget actions.
  • Faster Response TimesOptimized prompts and processing for quicker interactions.
  • Dynamic URL UpdatesHonored fresh URL changes for improved user experience.

Today, I focused on making significant improvements to the GIGI AI concierge, particularly around its speech handling and response times. The goal was to enhance user experience by eliminating speech cutoffs and ensuring faster, more fluid interactions. After a long 7-hour workday, I successfully shipped two features that I believe will bring us closer to our vision of a seamless agentic web experience.

The first commit I made was all about addressing a critical issue with speech truncation. I had observed that GIGI AI occasionally cut off responses mid-sentence, which can be frustrating for users trying to engage in a conversation. To tackle this, I reverted the fire-and-forget action approach that was implemented previously. By ensuring that the system now awaits completion before moving on, I’m hoping to maintain the integrity of the conversation. Additionally, I bumped the max_tokens to a safer range of 500 for responses and 400 for prompts. This adjustment aims to provide enough context for GIGI AI to generate coherent replies without running into truncation issues.

The second commit was focused on optimizing the speed of GIGI AI’s responses. I trimmed the prompt, lowered the max_tokens, and implemented parallel rate-limits to allow for faster processing. I also introduced a 1.5-second GPS budget, which should help in minimizing the time GIGI takes to respond. One of the more nuanced changes was to honor fresh URL changes over a 60-second user-pick lock. This means that if a user selects a new option or updates their input, GIGI will adapt more quickly, improving the overall fluidity of interactions.

The day was not without its challenges. Diagnosing the speech cutoff issue took more time than I anticipated. I had to backtrack through previous changes to understand the root cause. My initial instinct was to blame the max_tokens setting, but it turned out that the asynchronous handling of actions was more to blame. This experience reinforced the importance of a thorough understanding of how different components interact with each other, especially when building a complex platform like this one.

Working solo with Claude Code in VS Code has its ups and downs. On one hand, it allows me to iterate quickly and explore solutions without waiting for a team to review my work. On the other, it can be isolating when I'm deep in the weeds of debugging and optimization. Nevertheless, I’m proud of the progress I made today. Each improvement I implement brings me closer to the vision of a one-man-show company with a billion-dollar valuation. I can feel the momentum building, and with every commit, I’m laying the groundwork for what I hope will be a transformative platform for users.

I also took the opportunity to reflect on the broader implications of these changes. GIGI AI is not just an assistant; it's a gateway to the agentic web. By refining its capabilities, I am directly contributing to the evolution of spatial AI and the way users interact with technology. As I move forward, I’ll continue to prioritize enhancements that not only improve performance but also align with the core mission of hashtag.org and the agentic web.

In summary, today was a productive day filled with meaningful improvements to GIGI AI. The adjustments to speech handling and response times are foundational steps toward a more robust platform. As I continue to navigate the challenges of building alone, I remain focused on my long-term goals and the vision for this project. With every line of code, I’m not just shipping features; I’m building a future.

Terms in this entryHashtagGIGITokenPrompt

← Back to the full build journal