Your question makes it to the chat
The ask box on the home page now reliably gets your question into the chat. Before, a question typed there could be dropped on the way, or land in the wrong place if you were already signed in. Now it always goes into a fresh chat, on Auto or the model you picked, and your older conversations stay untouched. The send button also answers the moment you press it, so a slow connection no longer looks like nothing happened.
501 words
Asking from portail.cc while signed in now opens a new chat and sends your question there. It never lands inside an older conversation.
Your question could previously be lost if the chat redrew itself just before sending. That timing bug is fixed.
New accounts work as before: finish sign-up and your first question goes out on its own in your first chat.
The send button on the home page shows a spinner right away, and the next page is loaded in advance, so moving on feels instant.
Portail v2.6.10 shipped on 2026-10-09 as a patch release focused on your question makes it to the chat. The ask box on the home page now reliably gets your question into the chat. Before, a question typed there could be dropped on the way, or land in the wrong place if you were already signed in. Now it always goes into a fresh chat, on Auto or the model you picked, and your older conversations stay untouched. The send button also answers the moment you press it, so a slow connection no longer looks like nothing happened. 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: asking from portail.cc while signed in now opens a new chat and sends your question there. it never lands inside an older conversation, your question could previously be lost if the chat redrew itself just before sending. that timing bug is fixed, new accounts work as before: finish sign-up and your first question goes out on its own in your first chat, and the send button on the home page shows a spinner right away, and the next page is loaded in advance, so moving on feels instant. 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.6.10 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.