Russian requests no longer turn into pictures by mistake

Portail v2.8.4 shipped on 2026-10-31 as a patch release focused on russian requests no longer turn into pictures by mistake. Portail decides on its own when a message is asking for a picture, so you don't have to switch modes: on a model that can draw, a request like "create an image of a fox" goes straight to image generation. In the last release that check learned Russian, but it matched too loosely. On an image-capable model, everyday requests such as "сделай план на март" or "создай карту сайта" could be read as picture requests, because a few letters inside ordinary words looked like the start of a word for "art" or "picture". That sent a text question to image generation and charged for an image nobody asked for. This update fixes the check so it only recognizes picture words at the start of a word, and it now also understands "нарисуй" (draw) on image models, which it missed before. Carousels got two small fixes too: a page whose picture comes from an outside link is left out instead of showing only its title, and the page number and swipe arrow stay visible on bright custom backgrounds. 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: ordinary russian requests on an image-capable model stay text replies: plans, reports, site maps and names are no longer sent to image generation, "нарисуй кота" and other drawing requests in russian are now recognized as picture requests on image models, tapping the image shortcut and then clearing the chat box, or switching to another chat, ends the picture draft, so a later message isn't turned into an image, carousel pages with a picture that can't be loaded are skipped rather than left with only a title, and on bright custom carousel backgrounds, the page number and the swipe arrow keep enough contrast to read. 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.8.4 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.