Start a watcher right from the chat
Watchers no longer have to be set up in settings. Ask Portail something like "tell me when the XM5 drops under $280" or "let me know when my university posts exam dates", and it answers what it can right now, then offers to keep an eye on it. A Start watching card appears under the reply with the exact condition it would watch for, how often it will check on your plan and where it will tell you. One tap starts it. Customize opens the full watcher form with the condition filled in, if you want a different speed, delivery or model. Nothing is set up until you tap: Portail only proposes, and the watcher goes through the same plan and limit checks as one you create in settings. New watchers start on a fast, cheap model, because every check uses a few credits. If you've reached your plan's limit on watchers and tasks, the card says so and points you to Manage watchers or a bigger plan instead. Every message you send also has a new Watch for this button next to Schedule this, which opens a watcher with your message as the condition. Offers never appear in incognito chats, and the card remembers that you started a watcher, so it shows as done after a reload.
619 words
Ask Portail to tell you when something happens and it offers a Start watching card under its reply.
One tap starts the watcher; Customize opens the full form with the condition filled in.
Nothing is created until you tap, and the usual plan speeds and limits apply.
A Watch for this button now sits next to Schedule this on your messages.
No offers in incognito chats.
Portail v2.9.1 shipped on 2026-11-06 as a patch release focused on start a watcher right from the chat. Watchers no longer have to be set up in settings. Ask Portail something like "tell me when the XM5 drops under $280" or "let me know when my university posts exam dates", and it answers what it can right now, then offers to keep an eye on it. A Start watching card appears under the reply with the exact condition it would watch for, how often it will check on your plan and where it will tell you. One tap starts it. Customize opens the full watcher form with the condition filled in, if you want a different speed, delivery or model. Nothing is set up until you tap: Portail only proposes, and the watcher goes through the same plan and limit checks as one you create in settings. New watchers start on a fast, cheap model, because every check uses a few credits. If you've reached your plan's limit on watchers and tasks, the card says so and points you to Manage watchers or a bigger plan instead. Every message you send also has a new Watch for this button next to Schedule this, which opens a watcher with your message as the condition. Offers never appear in incognito chats, and the card remembers that you started a watcher, so it shows as done after a reload. 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: ask portail to tell you when something happens and it offers a start watching card under its reply, one tap starts the watcher; customize opens the full form with the condition filled in, nothing is created until you tap, and the usual plan speeds and limits apply, a watch for this button now sits next to schedule this on your messages, and no offers in incognito chats. 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.9.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.