Seven Embed & Plugin Upgrades for GIGI Assistant — May 17, 2026

Today, I focused on enhancing the SEVEN embed and the GIGI Assistant plugin, which are crucial components of the agentic web experience I'm building. I shipped three significant features and five critical fixes over a long 9-hour day of coding. The most notable feature is the public SEVEN voice embed at /seven-embed, which allows for a seamless voice interaction experience across websites. This is a major step towards making the GIGI Assistant more interactive and user-friendly.

The new voice embed is designed to be iframable and cross-origin, which means it can be integrated into various sites without the usual restrictions. This was a challenge I faced today; I had to exclude the route from the global X-Frame-Options header to ensure the iframe loads correctly across different origins. It’s a delicate balance to maintain security while allowing for flexibility in how users can interact with the SEVEN agent. I also made the HTML and body of the iframe fully transparent, so it overlays the host pages without any unsightly white panels showing up.

The plugin itself received some significant upgrades as well. In version 1.2.15, I replaced the text chat with a SEVEN-style voice avatar that sits at a prominent position on the page. This update mirrors the functionality of the GIGI assistant on hashtag.org, making the experience consistent across platforms. The goal here is to create an intuitive interface that allows users to engage with the assistant effortlessly. Clicking on the avatar opens a popup that auto-engages the voice session, which is a crucial improvement to the user experience.

One of the biggest hurdles today was dealing with some unexpected routing issues. I had to reserve /seven-embed in the PORTAL_SHARE_RESERVED_SEGMENTS to prevent middleware from rewriting it to /p/seven-embed. This misdirection was causing broken iframes in the #SPACE plugin, which was a frustrating dead end that consumed a lot of my time. Diagnosing the issue required a deep dive into the middleware logic, and I'm relieved that I managed to resolve it. It’s moments like these that remind me of the complexities involved in building a robust platform like this.

In addition to these features, I also introduced a floating GIGI launcher on every site, backed by chrome.storage.local, which allows for a persistent and accessible assistant experience. Users can toggle the GIGI assistant on and off easily, enhancing the usability of the platform. This was a feature I had been contemplating for a while, and it feels rewarding to see it come to fruition.

Throughout this process, I’ve been reflecting on the challenges of building this platform solo with AI assistance. It’s a unique experience to have Claude Code in VS Code as my co-developer, allowing me to tackle these problems without the overhead of hiring additional team members. While it’s certainly a grind, the satisfaction of working through these challenges on my own terms is incredibly fulfilling. My vision of building a one-man-show company with a billion-dollar valuation feels increasingly attainable with each feature I ship.

As I wrap up today’s entry, I’m excited about the direction these updates are taking the GIGI Assistant and the SEVEN embed. The progress is tangible, and I’m looking forward to collecting feedback from users about these new enhancements. I’m also aware that there’s always more work to be done, especially in refining the user experience and ensuring everything runs smoothly across different contexts. But for now, I’m proud of what I’ve accomplished today and eager to see how it impacts the overall functionality of the agentic web platform.