Incognito moves to the top right
The Incognito button now lives in the top right corner of the chat, next to Upgrade and Share, which is where you would look for it in other chat apps. It used to sit on the left of the header beside the menu. It is a quiet icon with a label, and on phones the label drops away so only the icon shows, which keeps the header from getting crowded. When incognito is on, the button lights up in the accent color so you can tell at a glance that the chat is not being saved. Nothing about how incognito works has changed: an incognito chat is still never saved to your account or this browser, it still stays out of your memory and learned preferences, it still can't be shared by link, and it still disappears when you leave it. The button only appears on chats that are not part of a project, and it locks once an incognito chat has messages, so you can't flip a chat that may already have been saved. This is purely a change of position and styling, made so the feature is easy to find the moment you need it. Credits are still used in incognito chats because the models cost the same to run, and the in-chat explanation of what incognito does is unchanged in both English and Russian.
588 words
The Incognito button moved to the top right of the chat header.
On phones it shows as an icon only, and it highlights while incognito is on.
Portail v2.6.20 shipped on 2026-10-10 as a patch release focused on incognito moves to the top right. The Incognito button now lives in the top right corner of the chat, next to Upgrade and Share, which is where you would look for it in other chat apps. It used to sit on the left of the header beside the menu. It is a quiet icon with a label, and on phones the label drops away so only the icon shows, which keeps the header from getting crowded. When incognito is on, the button lights up in the accent color so you can tell at a glance that the chat is not being saved. Nothing about how incognito works has changed: an incognito chat is still never saved to your account or this browser, it still stays out of your memory and learned preferences, it still can't be shared by link, and it still disappears when you leave it. The button only appears on chats that are not part of a project, and it locks once an incognito chat has messages, so you can't flip a chat that may already have been saved. This is purely a change of position and styling, made so the feature is easy to find the moment you need it. Credits are still used in incognito chats because the models cost the same to run, and the in-chat explanation of what incognito does is unchanged in both English and Russian. 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 incognito button moved to the top right of the chat header, and on phones it shows as an icon only, and it highlights while incognito is on. 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.20 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.