Free accounts sharing one browser now share one allowance

Portail v1.7.1 shipped on 2026-09-10 as a patch release focused on free accounts sharing one browser now share one allowance. Signing up for a fresh free account from the same browser or device used to reset the free credit pool from zero every time. Free accounts that repeat a strong signal, a random installation id, a verified phone or email alias, or a Telegram id, now draw from one shared allowance instead. A separate gap in account creation was also closed: the captcha check ran as a standalone call that scripted signups could skip entirely, so it now runs as a single-use, action-scoped token inside the signup request itself. 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: free accounts that repeat a strong device, browser, or verified-identity signal now share one free-tier credit pool instead of each signup starting a fresh allowance, closed a signup bypass where the captcha verification step could be called on its own and skipped: turnstile tokens are now single-use and checked inline during account creation, the telegram side of portail (omniverse) joins the same free-allowance graph through the account's telegram id and phone number, so free usage is shared across web and telegram rather than doubled, and the onboarding "which ai tools have you used" picker now shows each provider's real icon instead of a plain letter. 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. v1.7.1 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.