Talk, and it types
Voice mode is gone. The same sound-wave button in the chat box now does dictation: tap it, talk, and your words show up in the box while you speak, with steady background noise kept out. Nothing sends until you say so.
825 words
Tap the sound-wave button while the chat box is empty and start talking. Text appears phrase by phrase while you speak, so you can see it's keeping up. Once there's text, the same button turns into send, like before.
Steady background noise stays out of your message. Fans, traffic, hum and keyboard clicks don't turn into stray words, because only the stretches where someone is talking get sent to be transcribed. Other people talking close by can still be picked up, so dictate where your voice is the loudest one in the room.
A live waveform and a timer show it's listening. The waveform moves with your voice, not with the room.
Press the check button, or Enter, to keep the text. It stays in the box for you to fix up before you send it. Press X, or Escape, to throw the dictated words away and get back exactly what you had typed.
Already typed half a thought? Press and hold the send button until it turns into the sound wave, let go, and say the rest. Your words go after what you typed. Ctrl+Shift+Space (Cmd+Shift+Space on a Mac) does the same from the keyboard.
English, Russian and most other languages work, and the language is detected as you talk.
The old voice mode, which read replies out loud in a full-screen orb, has been removed. The play button on a reply still reads it aloud in the voice you picked under Customization.
Portail v2.7.0 shipped on 2026-10-15 as a minor release focused on talk, and it types. Voice mode is gone. The same sound-wave button in the chat box now does dictation: tap it, talk, and your words show up in the box while you speak, with steady background noise kept out. Nothing sends until you say so. 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.
This was more than a quiet maintenance pass. A minor release changes how a visible part of Portail behaves, how a larger workflow is framed, or how a user understands the product. The important part is not only that the feature exists. The important part is that it joins the rest of the system without making the chat harder to use. Portail is useful because context travels with the user. Every larger release has to protect that feeling.
The main changes were direct: tap the sound-wave button while the chat box is empty and start talking. text appears phrase by phrase while you speak, so you can see it's keeping up. once there's text, the same button turns into send, like before, steady background noise stays out of your message. fans, traffic, hum and keyboard clicks don't turn into stray words, because only the stretches where someone is talking get sent to be transcribed. other people talking close by can still be picked up, so dictate where your voice is the loudest one in the room, a live waveform and a timer show it's listening. the waveform moves with your voice, not with the room, press the check button, or enter, to keep the text. it stays in the box for you to fix up before you send it. press x, or escape, to throw the dictated words away and get back exactly what you had typed, already typed half a thought? press and hold the send button until it turns into the sound wave, let go, and say the rest. your words go after what you typed. ctrl+shift+space (cmd+shift+space on a mac) does the same from the keyboard, english, russian and most other languages work, and the language is detected as you talk, and the old voice mode, which read replies out loud in a full-screen orb, has been removed. the play button on a reply still reads it aloud in the voice you picked under customization. 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.
For this release, the archive points back to the verified commit trail instead of relying on memory. The title, date, and highlights come from the repository history around v2.7.0. That matters because a release log should be boringly checkable. If someone wants to know why a feature appeared, why a page changed, or why a billing rule behaves differently, the public record and the engineering record should not disagree.
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.0 moved that contract forward in its own narrow lane.
The product lesson is also worth naming. Portail grew quickly through chat, admin, billing, Canvas, Omniverse, Agents, and the coding hand-off bridge. Features landed close together, and some releases bundled polish with deeper infrastructure. This post separates the user-facing promise from the implementation noise. It says what the release changed, why that mattered, and where it sits in the product timeline.
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.
Screenshots
