One composer, one focus
The place you type got simpler. A new chat now shows one question and the composer, nothing else competing for your eye; your activity grid moved to Profile, under General. The composer keeps the same rounded shape whether the chat is empty or full, with bigger text that no longer makes phones zoom in when you tap it. The model name sits there as plain text, and the cost hint lives in the model list where you actually compare models. The round button on the right does one job at a time: with an empty box it starts a voice conversation, and as soon as you type or attach something it becomes send. In a running chat the composer floats over the conversation with a soft fade instead of sitting under a divider line. The box on the home page and the demo below it got the same composer, so what you see before signing up is what you get after.
545 words
New chats show just the question and the composer; the activity grid moved to Profile > General.
One round button: voice when the box is empty, send once there's something to send.
Bigger composer text, no more zoom-in on phones.
The composer floats over the chat instead of sitting under a divider.
Portail v2.6.15 shipped on 2026-10-10 as a patch release focused on one composer, one focus. The place you type got simpler. A new chat now shows one question and the composer, nothing else competing for your eye; your activity grid moved to Profile, under General. The composer keeps the same rounded shape whether the chat is empty or full, with bigger text that no longer makes phones zoom in when you tap it. The model name sits there as plain text, and the cost hint lives in the model list where you actually compare models. The round button on the right does one job at a time: with an empty box it starts a voice conversation, and as soon as you type or attach something it becomes send. In a running chat the composer floats over the conversation with a soft fade instead of sitting under a divider line. The box on the home page and the demo below it got the same composer, so what you see before signing up is what you get after. 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: new chats show just the question and the composer; the activity grid moved to profile > general, one round button: voice when the box is empty, send once there's something to send, bigger composer text, no more zoom-in on phones, and the composer floats over the chat instead of sitting under a divider. 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.15 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.