Portail calls: meet right inside Portail, with Portail in the call
Meets now has a third way in. Until today, Portail could listen in the room through your microphone, and it was getting ready to join Google Meet, Zoom and Teams calls as a participant. Now you don't need another call app at all. Open Meets, press Start a call, and send the link. Up to six people talk on video, share their screens and type in a chat everyone sees, and Portail sits in the call as its own tile, taking notes the whole time. Because every person's own browser transcribes their own microphone, every line of the transcript carries the real name of whoever said it. There's no guessing who spoke and no echo from speakers, and when you mute yourself, Portail stops hearing you too. Anyone in the call can say "Portail," and a question, or type it in the chat, and Portail answers in the chat for everyone, using only what was said in the meeting. Ask it for a plan, a checklist or a follow-up email and it drafts one on the host's meeting page. The notes fill in as you go: a summary, the decisions, and action items with owners. Everyone in the call can read the transcript and notes, and the host's private Ask Portail chat and docs stay private. Joining takes a signed-in Portail account, and everyone sees a short notice before they join: Portail transcribes the call, keeps the text and notes, and never keeps the audio. The calls run on Portail's own call server, not a third party's, and nothing is ever recorded. The host stays in charge: copy the invite link, make a new link so the old one stops working, remove someone from the call, or end it for everyone. Every plan can host. Calls on the free plan run for up to an hour, and paid plans get up to eight hours. The host's credits pay for transcription and answers, so guests never spend their own. When the call ends, the host gets the usual meeting page with the full transcript and notes, plus the recap email if it's turned on.
1047 words
Start a call from Meets, send the link, and meet on video with up to six people: camera, microphone, screen sharing and a shared chat.
Portail is in the call as its own tile. It transcribes everyone under their real name and keeps live notes with decisions and action items.
Say or type "Portail," and a question, and the answer appears in the call's chat for everyone. It only uses what was said in the meeting.
A notice before joining tells everyone Portail transcribes the call and keeps the text, never the audio. Nothing is recorded.
The host can copy or reset the invite link, remove someone, and end the call for everyone. Every plan can host; free plan calls last up to an hour.
It works in the browser on phones too, with the chat and notes in a sheet that slides up from the bottom.
Portail v2.13.0 shipped on 2026-11-14 as a minor release focused on portail calls: meet right inside portail, with portail in the call. Meets now has a third way in. Until today, Portail could listen in the room through your microphone, and it was getting ready to join Google Meet, Zoom and Teams calls as a participant. Now you don't need another call app at all. Open Meets, press Start a call, and send the link. Up to six people talk on video, share their screens and type in a chat everyone sees, and Portail sits in the call as its own tile, taking notes the whole time. Because every person's own browser transcribes their own microphone, every line of the transcript carries the real name of whoever said it. There's no guessing who spoke and no echo from speakers, and when you mute yourself, Portail stops hearing you too. Anyone in the call can say "Portail," and a question, or type it in the chat, and Portail answers in the chat for everyone, using only what was said in the meeting. Ask it for a plan, a checklist or a follow-up email and it drafts one on the host's meeting page. The notes fill in as you go: a summary, the decisions, and action items with owners. Everyone in the call can read the transcript and notes, and the host's private Ask Portail chat and docs stay private. Joining takes a signed-in Portail account, and everyone sees a short notice before they join: Portail transcribes the call, keeps the text and notes, and never keeps the audio. The calls run on Portail's own call server, not a third party's, and nothing is ever recorded. The host stays in charge: copy the invite link, make a new link so the old one stops working, remove someone from the call, or end it for everyone. Every plan can host. Calls on the free plan run for up to an hour, and paid plans get up to eight hours. The host's credits pay for transcription and answers, so guests never spend their own. When the call ends, the host gets the usual meeting page with the full transcript and notes, plus the recap email if it's turned on. 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: start a call from meets, send the link, and meet on video with up to six people: camera, microphone, screen sharing and a shared chat, portail is in the call as its own tile. it transcribes everyone under their real name and keeps live notes with decisions and action items, say or type "portail," and a question, and the answer appears in the call's chat for everyone. it only uses what was said in the meeting, a notice before joining tells everyone portail transcribes the call and keeps the text, never the audio. nothing is recorded, the host can copy or reset the invite link, remove someone, and end the call for everyone. every plan can host; free plan calls last up to an hour, and it works in the browser on phones too, with the chat and notes in a sheet that slides up from the bottom. 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.13.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.13.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
