Incognito chats

Portail v2.6.19 shipped on 2026-10-10 as a patch release focused on incognito chats. Sometimes you want to ask something without it following you around. Incognito chats are a new way to do that: pick the Incognito button at the top of an empty chat and everything you say in it stays out of your history. The conversation is never saved to your account or to this browser, it doesn't appear in your chat list, and it is gone the moment you leave it or reload the page. Portail also keeps your Enhanced Context memory and your learned preferences out of the picture in both directions. Nothing from your saved memory is used to answer you, and nothing you say is added to it or used to tune how Portail talks to you later. The chat can't be shared as a link either, since a shared link would be a saved copy. Two things stay the same on purpose: credits are still used for every reply, because the models cost the same to run, and a chat that already has messages can't be switched into incognito halfway through, since it may already have been saved. To start one, open an empty chat and press Incognito, or press it from anywhere to begin a fresh incognito chat. The button works the same on phones, and the explanation of what incognito does shows right in the empty chat so you never have to guess. Incognito is available in 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: new incognito button on empty chats: nothing is saved to your account or browser, and the chat disappears when you leave, incognito chats don't read from or add to your enhanced context memory or learned preferences, and credits still apply, and incognito chats can't be shared by link. 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.19 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.