Flagship models now start at Plus
The most expensive models, such as Claude Opus and GPT-5.5, are now part of Plus and Ultra. Free and Pro still reach every other model in the picker, including Sonnet, Gemini Pro, Grok and the rest. Flagship models show a small lock in the model picker on plans that can't use them, and tapping one opens the upgrade options. If a conversation was still set to a flagship model, Portail switches it back to the default and tells you why, instead of failing quietly. The same rule applies everywhere you chat: the web app, Telegram, scheduled tasks and Auto mode, which now picks only from models your plan can use. Ratchet follows the same rule when it runs on Portail credits, so a linked Free or Pro account needs to pick a non-flagship model there. We also refreshed the model catalogue: it adds dozens of new models and retires 25 older ones, and chats that were set to a retired model move to its closest successor.
572 words
Flagship models (Claude Opus, GPT-5.5 and similar) are included with Plus and Ultra.
Free and Pro keep every other model, including Sonnet, Gemini Pro and Grok.
Locked models show a lock in the picker, and tapping one opens the upgrade options.
Auto mode and Council only choose models your plan can use.
The model catalogue was refreshed with new models from OpenRouter.
Ratchet on Free or Pro needs a non-flagship model selected.
Portail v2.7.2 shipped on 2026-10-23 as a patch release focused on flagship models now start at plus. The most expensive models, such as Claude Opus and GPT-5.5, are now part of Plus and Ultra. Free and Pro still reach every other model in the picker, including Sonnet, Gemini Pro, Grok and the rest. Flagship models show a small lock in the model picker on plans that can't use them, and tapping one opens the upgrade options. If a conversation was still set to a flagship model, Portail switches it back to the default and tells you why, instead of failing quietly. The same rule applies everywhere you chat: the web app, Telegram, scheduled tasks and Auto mode, which now picks only from models your plan can use. Ratchet follows the same rule when it runs on Portail credits, so a linked Free or Pro account needs to pick a non-flagship model there. We also refreshed the model catalogue: it adds dozens of new models and retires 25 older ones, and chats that were set to a retired model move to its closest successor. 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: flagship models (claude opus, gpt-5.5 and similar) are included with plus and ultra, free and pro keep every other model, including sonnet, gemini pro and grok, locked models show a lock in the picker, and tapping one opens the upgrade options, auto mode and council only choose models your plan can use, the model catalogue was refreshed with new models from openrouter, and ratchet on free or pro needs a non-flagship model selected. 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.7.2 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.