Weekly Agentic-Web Newsroom & App Store Launch — July 16, 2026

Today, I set out to enhance the user experience on the platform by launching the weekly agentic-web newsroom and the App Store, while also addressing various performance issues and bugs that had been hampering the overall functionality. After a long 18-hour day, I made significant strides, shipping 34 commits in total, with 30 dedicated to new features and improvements, and 4 focused on critical fixes.

The highlight of the day was the launch of the weekly agentic-web newsroom, which can now be accessed through the new /news hub. This feature includes an article template and a Thursday cron generator to automate content updates. I utilized Firecrawl research and Claude as my writing assistant to ensure the content is relevant and engaging. The newsroom will help keep users informed about the latest developments in the agentic web space and has its own dedicated report section at /news/agentic-web-companies. I also reserved slugs for future articles, ensuring that the architecture is set for easy expansion.

In addition to the newsroom, I launched the App Store, which provides a centralized location for all live hashtag.org applications. This feature is crucial for streamlining user access and enhancing the discoverability of our apps. It features footer links and is easily accessible at /apps, making it a one-stop shop for users looking to explore what we offer. The App Store not only improves user experience but also reinforces our commitment to providing a comprehensive ecosystem for our community.

While these features were exciting to deliver, they didn’t come without their challenges. I spent a considerable amount of time debugging and optimizing various aspects of the platform. For instance, I had to implement a fix for the AI calls related to Tavus voice, which needed to survive changes in the scanner filter. The initial implementation only accounted for Jitsi JWT calls, which resulted in failures for other types of calls. After some deep diving into the code, I was able to implement call-liveness guards that addressed this issue effectively, but it did eat up several hours of my day.

I also focused on performance improvements. One of the significant changes was optimizing the cookie-consent banner by server-side rendering it with a pre-paint consent guard. Previously, this element was causing a delay of about a second in loading, which negatively impacted the user experience. By addressing this, I managed to improve the largest contentful paint (LCP) metric, which is critical for keeping our site fast and responsive.

Another performance enhancement involved deferring the loading of Stripe resources to improve initial load times. This was a necessary step, as the Stripe integration was dynamically loading about 239KB of data that could be loaded later. Additionally, I converted the GIGI avatars from PNG to WebP format, reducing their size significantly from 659KB to just 262KB. Such optimizations are crucial as they contribute to the overall performance of the site, which is a key factor in retaining users and improving SEO.

Reflecting on the entire day, I am proud of the progress made while managing the complexities of building this platform solo, using AI as my primary team member. The combination of Claude Code in VS Code and my own determination has allowed me to tackle these challenges without the need for costly team resources. Every feature I shipped today brings me one step closer to realizing my vision of a one-man-show company with a billion-dollar valuation. It’s a long road ahead, but each commit, each bug fix, and each feature launch is a testament to that ambition.

As I wrap up this entry, I look forward to seeing how users engage with the new newsroom and App Store. The next steps will involve gathering feedback to iterate on these features and ensure they meet the needs of our growing community. Building in public is a journey filled with lessons, and I’m eager to share what comes next.