MetaMask Sign-In & Privy Session Fixes for GIGI Projects — April 22, 2026

Today, I set out to streamline the authentication process for my GIGI Projects by implementing a direct sign-in with MetaMask that bypasses the Privy app. This was crucial because it allows users to log in seamlessly without encountering session issues that previously plagued the experience. After a long 11-hour day of coding and debugging, I successfully shipped a total of 17 commits, including 13 features and improvements, alongside 4 critical fixes.

The core of today's work revolved around the authentication pathway. The initial problem I faced was that the Privy app's custom API URL was not aligned with the domain of hashtag.org, leading to session cookies not being recognized. This resulted in users being unable to log in or maintain their sessions properly. To address this, I created a direct sign-in route with MetaMask, which bypasses the problematic Privy integration. This change not only simplifies the login process but also enhances user experience by reducing friction when accessing GIGI Projects.

While implementing this feature, I stumbled upon several bugs related to Privy's session management. One significant issue was that the app would silently log users out if the access token returned null, leaving them confused with a generic error message. To remedy this, I introduced an auto-wipe for stale browser sessions and an explicit reset call-to-action. This fix required careful debugging to ensure that users were guided smoothly through the login process, rather than facing frustrating roadblocks.

Another bug involved the timing of the authentication state. Privy would indicate that a user was authenticated before the access token was actually available, leading to errors like 'Could not read Privy session. Try again.' I resolved this by implementing a wait for the access token, along with utilizing onComplete and onError callbacks. This change not only improved the reliability of the authentication flow but also provided clearer feedback to users during the login process.

Beyond authentication, I also made substantial progress on the GIGI Projects management functionality. I integrated a new ideas-to-delivery workflow that allows project owners to fill out a structured questionnaire detailing their project's goals and needs. This form submission automatically enters a workflow that includes stages for proposal readiness and payment processing via Stripe. This feature is designed to streamline project management and ensure that users have a clear path from idea conception to project execution.

I also focused on enhancing the dashboard experience by adding an analytics overview and a GIGI site embed snippet. The revamped dashboard now features animated stat cards that provide insights into portal performance, keyword rankings, and competitor tracking. It was important for me to create a visually appealing and informative dashboard that gives users quick access to critical data about their projects.

Throughout the day, I faced a few hiccups that tested my patience, particularly with the dashboard's integration of various metrics and ensuring that the data displayed was accurate and up-to-date. I had to refactor some of the code to prevent fallback links pointing to localhost in production, which could lead to confusion for end-users. Ensuring that the dashboard is polished and functional is vital as I work towards building a one-man-show company with a billion-dollar valuation.

Working solo with AI tools like Claude Code in VS Code has been a game changer, allowing me to navigate through these challenges without the need for extensive team collaboration. It's empowering to know that I can rely on AI to assist with coding, debugging, and even brainstorming ideas, all while keeping my focus on creating a superior product in the agentic web space.

In summary, today’s progress not only reinforced my commitment to enhancing the GIGI Projects platform but also highlighted the importance of thorough testing and user feedback in the development process. As I continue this journey, I remain aware of the hurdles that come with solo building but also take pride in the strides I’m making toward achieving my ambitious goals. The road ahead is long, but with each commit, I see the vision of a successful, scalable platform becoming clearer.