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 made some major updates to GIGI AI concierge, especially in terms of speech handling and response time. My goal was to help the user experience by getting rid of speech cut-off problems while also achieving fast and fluid interactions. After working for about 7 hours, I was able to deliver two big features that are, in my opinion, going to take us closer to our goal of providing a seamless agentic web experience.

The first commit I made was focused on fixing a very difficult problem, which was speech truncation. I noticed that GIGI AI would cut off responses, and considering that speech responses are meant to engage users, it was very frustrating. To solve this problem, I reverted back to the earlier implementations of the fire-and-forget action approach. I hope to preserve the conversational integrity of the system, and in addition to this, I also increased the max_tokens to a range of 500 for responses and 400 for prompts. This should provide GIGI AI with enough context to respond appropriately, which I also hope will mitigate speech truncation.

The second commit was aimed at optimizing the speed of GIGI AI’s responses. I shortened the prompt, reduced the maximum number of tokens, and applied parallel rate-limits for faster processing. Additionally, I set a GPS budget of 1.5 seconds, which should decrease GIGI's response time. One of the more technical changes was to prioritize new URL changes over a 60-second lock on user picks. This means GIGI will respond to new inputs faster and will improve the fluidity of interactions.

I faced some difficulties while working on it, and figuring out the speech cutoff issue cost me a lot more time than I had expected. I had to go back on the changes I had made to find the cause. My first thought was that it was being caused by the max_tokens, but it was actually the asynchronous action handling that was ultimately the issue. This was another case of numerous components interacting with each other and calling for a more thorough understanding when constructing a complex system like this one.

While working with rudimentary AI in VS Code is a good way to learn the basics of coding, in my case it gave me valuable tools to develop my project concept, and it is a good basis for what I envision for my one-man company to be valued at a billion dollars. I believe I am continuously building a great platform for my envisioned clientele.

I took advantage of my productive day to think about what I was doing. I am creating an AI called GIGI that is much more than a mere assistant. I believe that as the AI improves, the user experience and the way they interact with the technology will change. My work will be an important factor in the evolution of spatial AI. I hope to incorporate enhancements to GIGI that go beyond point improvements and provide value to the objectives of hashtag.org and the agentic web.

I think that the day was productive and that the improvements made to GIGI AI were beneficial. The improvements made to the system's speech processing and response time are priority improvements that I hope will lead to major changes. I work hard to achieve my goals, and my vision for this project motivates me to endure the solitude of coding. I'm not just adding features; I'm building a future.

← Back to the full build journal