Model picker and Incognito notice stay in place
The model picker in the chat composer now opens lined up with the composer instead of sliding off the right edge of a phone screen, and the Incognito notice sits centered above the composer.
387 words
The model picker opens inside the screen on phones.
The Incognito notice is centered over the composer.
Portail v2.6.21 shipped on 2026-10-12 as a patch release focused on model picker and incognito notice stay in place. The model picker in the chat composer now opens lined up with the composer instead of sliding off the right edge of a phone screen, and the Incognito notice sits centered above the composer. 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: the model picker opens inside the screen on phones, and the incognito notice is centered over the composer. 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.21 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.