Search-Mode Enhancements & Hero UI Fixes for Agentic Web — April 18, 2026

My main task for today was improving the search-mode and hero UI components on my agentic web platform. I shipped eight new features and improvements along with eleven bug fixes. I had a very productive four hour coding session where I solved a lot of the issues that came up, especially in relation to the map and the search integrations.

One of the biggest pieces I worked on is the ability to alter preferences for the map provider. I had to change some underlying logic to make Google’s satellite view appear first. This change is important because a lot of users trust Google more than other options. I also fixed a huge bug that caused the CARTO flash during searches, which was a really annoying bug. The problem was that Google would appear by default when a key existed, so I fixed the issue by changing the perspective map to Google.

I could also make some additional changes and improvements in the hero UI, especially in the process of handing off searches. I changed the z-index so that Google’s search mode is selectable above the topic panel, which was the cause of some confusion. This change was made by creating a programmatic click handler to avoid pop up blockers, which took significantly longer to do than I expected. Overall, users will find it a lot simpler to switch search modes.

I also spent time improving the overall look and feel of the hero UI. I adjusted the spacing of the Gigi logo above the search bar to make it look cleaner. I also spent some time working on the topic cards, where I had to do a lot of trial and error to determine the best spacing while maintaining readability. I wanted to ensure that the 'Chat with Gigi' feature stood out, but I did not want it to be overwhelming in the user interface.

I also encountered some bugs that I did not anticipate which took a lot of my time while I was implementing these features. One such problem was the ability to smoothly position the topic panel without causing unintended jumps during user interaction. After some troubleshooting, I found that modifying the flex centering properties and assigning absolute positions would fix the problem. These tweaks were also important because they improved the overall quality of the user experience.

Today, I also reached another important milestone by integrating the portal AI assistant and Voicebox. I implemented support for OpenRouter-based portal DM replies and the optional Voicebox text-to-speech feature. Although there were some challenges with caching images, which required me to implement a long cache strategy to improve performance, this integration allows users to communicate with the portal in a more intuitive way.

Reflecting on my work today describes the challenges and positives of building this platform by myself, with Claude Code helping in VS Code. I often find myself trying to rationalize the positives of using AI, versus the time I may spend debugging problems caused by the AI code. Regardless, the freedom and control I have over the project are priceless. It brings me one step closer to my goal of being a one-man billion-dollar company.

I learned some good lessons about user experience and clean coding today. Each feature I ship and each bug I fix brings me closer to my vision for this agentic web platform. As I refine these components, I will be eager to see where users are impacted by my modifications and what new changes I will be able to implement in the following sessions.