New chats stay in your chat list
A chat you had just started, often one opened from the Finance page, could disappear from the chat list a minute later. Its save had failed quietly, for example when the page had made a lot of requests in a short time, and the list then reloaded from the server without it. Now a chat stays in the list while its save is still on its way, a failed save is tried again on every refresh, and saving chats no longer competes with the rest of the app for the same request budget.
459 words
Chats opened from Finance, and any new chat, no longer drop out of the list a minute after you start them.
A chat that fails to save is saved again automatically.
Portail v2.11.2 shipped on 2026-11-10 as a patch release focused on new chats stay in your chat list. A chat you had just started, often one opened from the Finance page, could disappear from the chat list a minute later. Its save had failed quietly, for example when the page had made a lot of requests in a short time, and the list then reloaded from the server without it. Now a chat stays in the list while its save is still on its way, a failed save is tried again on every refresh, and saving chats no longer competes with the rest of the app for the same request budget. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: chats opened from finance, and any new chat, no longer drop out of the list a minute after you start them, and a chat that fails to save is saved again automatically. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.11.2 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.