Vorno 0.22.0-beta.1

This is a prerelease. Pages ships off by default in every workspace — nothing changes for a workspace until someone turns it on in Settings → Workspace → Pages, and publishing additionally needs sharing configured, which a default install doesn't have.

Features

• Workspace Pages foundation — persistent local pages, sandboxed rendering, data refresh, and mediated action contracts are present as an upstream compatibility baseline. Pages and publication remain unavailable by default in Vorno until the per-workspace authority and service boundaries land. (from upstream v0.13.0–v0.13.3)
• Per-workspace Pages availability — Pages now stays disabled until enabled in a workspace's Settings, with its navigation, authoring tools, refresh scheduling, and publication controls following the same persisted host authority. Cleanup remains available if Pages is turned back off. #200, SUV-0058, 891060be
• Host-consented Page actions — Page capabilities now require approval in a native dialog tied to the requesting workspace window. Approvals are digest-bound, expiring, revocable, and safely serialized when multiple Pages request access. #201, SUV-0059, 74ccdac
• Confirmed Page actions — a Page that wants to act on your behalf now asks first. The action it is about to run is described in a native dialog the first time you use each approved capability in a view, and every action afterwards needs a real click you just made. Actions cannot fire on page load, on a timer, from a hover, or from a stale window, and approving one action never approves a different one — if the underlying command changes, you are asked again. Available in the desktop app, which is the only place a click can be confirmed; the web interface can still view Pages and read data, but will decline actions that change things. #204, SUV-0065, 9a8531ba
• Page buttons that message a session — a Page can now ask for permission to send one fixed message to one of your existing sessions, turning a dashboard into something that nudges the work it is showing you. Both the message and the session are fixed when you approve, so a Page can never choose a different session, write different text, or decide either at click time; the approval dialog names the session and shows you the exact wording. A Page can only reach sessions in its own workspace, can never close, archive, delete, or re-status a session, and is refused if the session is finished or already mid-turn. Delivered messages are labelled with the Page that sent them, so they never read as something you typed. Approvals last a day by default, are revocable at any time from the Page's Approved actions list, and a Page holding one cannot be published. Desktop only, since it needs a confirmed click. #205, SUV-0064, c711929b
• Secure optional Pages sharing — publish Pages to an isolated public service with password protection, immediate logical revocation, and explicit cleanup recovery; sharing remains disabled until a workspace enables it. #202, SUV-0060, 06de5295
• Published pages expire after 30 days — a page you share publicly stays up for 30 days from the last time you updated it, and updating it again starts the 30 days over. Setting, changing, or removing its password counts as an update too. After that the link stops working and the copy is deleted. An expired link looks exactly like a link that never existed, so nobody can tell from the outside that you once published something there. You can still unpublish and clean up a page after it expires. #208, SUV-0069, 9a1db5a7
• Expanded model catalog — upstream additions include Claude Fable 5.1 across Anthropic and Bedrock profiles, GPT-6 Astra for OpenAI and ChatGPT connections, and newer Pi-provider model families. Existing saved connections retain explicit defaults; new OpenAI and ChatGPT connections default to GPT-6 Astra. (from upstream v0.13.1–v0.13.3)

Improvements

• Pages documentation that matches Vorno — the built-in Pages guide now says what actually happens here: Pages stays off until you enable it for a workspace, publishing is a separate thing again and is unavailable unless it has been set up, and approvals for the riskier actions expire in a day rather than a month. It states plainly who a published page is attributed to, what a published copy is and is not allowed to do, and how long published content and operational logs are kept. Opening Pages in a workspace where it is turned off now explains that and points at the setting, instead of showing an empty panel. #209, SUV-0061, 07196c15
• More resilient Pi conversations — upstream retry/recovery work keeps eligible transient provider failures open with visible backoff progress, discards failed partial output, and bounds utility-query execution. (from upstream v0.13.3)
• Updated Claude and Pi SDKs — upstream SDK updates add improved usage/cost reporting, MCP resource links, model catalog coverage, and streaming/recovery fixes. (from upstream v0.13.1–v0.13.3)

Bug Fixes

• Reliable session saving across workspaces and windows — session saving is now tracked per workspace as well as per session, serialized so two saves for one session cannot overlap, and reconciled field by field against outside edits. Several faults went with it. Two workspaces holding the same session id — which happens whenever a workspace is copied, restored from a backup, or cloned between machines — were treated as one session, so deleting the session in one could delete the other's live transcript. A session renamed, relabelled, flagged, or marked read in another window, by a sync tool, or by a second running copy of Vorno could have that edit undone a moment later by a save already in flight. A plan accepted with "Accept & Compact" was kept only on disk, so the next save deleted it and the plan never ran. Quitting the app now also finishes what it started: a reply still being written is allowed to complete and is saved before the app exits, a turn that paused for a submitted plan or a sign-in prompt is saved in that paused state rather than lost, a save already in progress is waited for instead of being cut off mid-write, a message you send in the same moment you quit is either saved or clearly refused rather than acknowledged and lost, and a save that fails no longer causes the next one to overwrite your unsaved change with whatever was on disk. A save that fails while the app is closing is now reported instead of passing silently. #206, SUV-0066, 07c3d27c
• Safer diagnostics redaction — shared Sentry and diagnostic redaction now removes sensitive headers and breadcrumb fields consistently across main and renderer processes. (from upstream v0.13.3)
• Clearer CLI failures — upstream CLI runs now preserve structured provider errors, return nonzero exit status on failure, and mark discarded partial output explicitly. (from upstream v0.13.3)

Breaking Changes