Today we completed one of the important final blocks before release: we added Google sign-in and Google account linking for existing profiles.
Simply put, llmgirl is now even closer to becoming a complete product, where sign-in, account management, Telegram and the Web dashboard all work as one connected system.
The system now has another convenient authorization method: Google sign-in.
This is not just a new login button. We integrated Google authorization into the existing project architecture so that it does not break the current Telegram login flow, personal dashboard logic or account behavior.
To support the new logic, we added separate Google-related fields to the user model:
This is useful not only for the current sign-in flow, but also for future interface updates, where users will be able to clearly see which login and account linking methods they use.
During development, we found an important issue: the Google callback was tied to guest-only logic. Because of that, when a user already had an active session, they could simply be redirected back to the dashboard without the Google link actually being saved.
We caught this issue, fixed it and brought the flow to a proper state. Now account linking goes through the full cycle:
While preparing the environment, an old issue appeared in one of the migrations related to dialogs and backfill logic.
We brought the migration chain into a working state so the project can be installed not only on an existing live database, but also from scratch.
Along the way, we also had to fix local infrastructure: Docker mounts, compose scenarios, local Caddy configuration and differences between local and production setups.
This is not the most “beautiful” type of work, but these are exactly the things that can block development and make deployments chaotic.
We also cleaned up parts of the default Breeze/Laravel flow, so after sign-in users go not to an abstract dashboard, but to the actual llmgirl personal dashboard.
At the final stage of product development, it is especially important that the user account feels unified and clear.
If Telegram works separately, Google works separately, Web works separately, and every login method behaves differently, users lose trust in the service.
Our task now is to make llmgirl feel like one connected product:
At this point, llmgirl is no longer a raw prototype. It is in the final stage of preparation before release.
The main product contours are already assembled:
The focus is now shifting from “building the foundation” to final stabilization, polishing and real-world scenario testing.
The next stage is final large-scale testing.
During this stage we will closely test:
This is no longer the stage of major architectural crossroads. The task now is to bring the product to a confident, stable state and release it without unnecessary chaos.
Today's update is not just another sign-in method. It is another important step toward making llmgirl a unified, convenient and understandable product.
We continue to finish the last important details. After that, the project will move into final large-scale testing and then to release.
And yes — it is really getting close.
