Watch the model work, step by step
When a model thinks or uses a tool before answering, you now see it happen in the order it happens. Before, all the thinking sat in one folded box and every tool call was grouped by type above the reply, so you could not tell what came first. Now each step appears the moment it starts. The model's thinking opens by itself and streams its text as it is written. When the model moves on, for example to search the web, look something up in your memory, or read your calendar, that thinking folds shut into a short "Thought for 3s" style line, and the next step shows up right below it with its own animated status. If the model thinks again after a tool call, that becomes a new step in the right place instead of being glued to the first one. You can still click any thinking line to open or close it whenever you like. Older conversations keep the layout they were saved with, so nothing you wrote before changes or disappears. Nothing about credits, plans or privacy changes: the same thinking and tool details that were shown before are shown now, just in a clearer order and in real time.
574 words
Thinking and tool calls appear in order as they happen, with the live step open and finished steps folded.
Each search, memory lookup and connector action sits right under the thinking that led to it.
Portail v2.6.24 shipped on 2026-10-12 as a patch release focused on watch the model work, step by step. When a model thinks or uses a tool before answering, you now see it happen in the order it happens. Before, all the thinking sat in one folded box and every tool call was grouped by type above the reply, so you could not tell what came first. Now each step appears the moment it starts. The model's thinking opens by itself and streams its text as it is written. When the model moves on, for example to search the web, look something up in your memory, or read your calendar, that thinking folds shut into a short "Thought for 3s" style line, and the next step shows up right below it with its own animated status. If the model thinks again after a tool call, that becomes a new step in the right place instead of being glued to the first one. You can still click any thinking line to open or close it whenever you like. Older conversations keep the layout they were saved with, so nothing you wrote before changes or disappears. Nothing about credits, plans or privacy changes: the same thinking and tool details that were shown before are shown now, just in a clearer order and in real time. 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: thinking and tool calls appear in order as they happen, with the live step open and finished steps folded, and each search, memory lookup and connector action sits right under the thinking that led to it. 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.24 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.