Ratchet's desktop app, one click from code.portail.cc
The Ratchet site now has a Desktop app card in its Install section. The Linux build downloads straight from the page, checked against a SHA-256 before it is served, so a swapped or damaged file is refused instead of handed to you. It needs no Python, adds Ratchet to your app menu, and shares keys, sessions and your Portail link with the terminal app, so a conversation started in one picks up in the other. The Windows build is still being packaged, so its button reads not available yet instead of linking somewhere that does not work. The terminal install steps are still right below it, and the FAQ and the page's search metadata now mention the desktop app too.
498 words
Download Ratchet's Linux desktop app from the Install section of code.portail.cc.
Downloads are verified against a SHA-256 before they are served.
Windows shows as not available yet until its installer is ready.
The FAQ, structured data and llms.txt now describe the desktop app.
Portail v2.7.1 shipped on 2026-10-17 as a patch release focused on ratchet's desktop app, one click from code.portail.cc. The Ratchet site now has a Desktop app card in its Install section. The Linux build downloads straight from the page, checked against a SHA-256 before it is served, so a swapped or damaged file is refused instead of handed to you. It needs no Python, adds Ratchet to your app menu, and shares keys, sessions and your Portail link with the terminal app, so a conversation started in one picks up in the other. The Windows build is still being packaged, so its button reads not available yet instead of linking somewhere that does not work. The terminal install steps are still right below it, and the FAQ and the page's search metadata now mention the desktop app too. 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: download ratchet's linux desktop app from the install section of code.portail.cc, downloads are verified against a sha-256 before they are served, windows shows as not available yet until its installer is ready, and the faq, structured data and llms.txt now describe the desktop app. 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.7.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.