Fixes a new chat showing a folder that belongs to a different conversation, with
its sync status flashing in the chat bar.
Fixed
-
A new chat no longer inherits the previous conversation.
sessionFolder()with no argument means "whichever conversation is open", and
the shell ignored the chat URL entirely once the web app had reported a
conversation once. Clicking New chat navigates to/chatwith no?s=,
which the shell dismissed as "just the URL again" — so it kept answering with
the chat you had just left, and every session-scoped answer described the
wrong one.Reproduced against a live app before the fix:
clicked New chat t+0s url=/chat?s=cde99de2-… sessionId=cde99de2-… t+1s url=/chat sessionId=cde99de2-… <- nothing is openA URL naming a conversation still never overrules what the page reported —
it may be stale. A URL naming none now clears it, because keeping the old
one is not a harmless guess. This applies only where chat URLs carry?s=at
all; where they never do, an absent id says nothing.
Note for whoever builds the web app
onSyncStatus is an app-wide stream: it fires for every folder this machine
syncs, on every change, and LinkStatus carries no conversation id. Rendering it
directly paints one of the machine's folders into every chat and repaints on
each sync tick. The chat's folder chip should come from onSessionChanged,
which is scoped to the open conversation; filter onSyncStatus by
link.folderId if you want live progress inside it.
Which file
| You have | Download |
|---|---|
| Mac, Apple Silicon (M1-M4) | Redstone-0.2.5-arm64.dmg |
| Mac, Intel | Redstone-0.2.5-x64.dmg |
| Windows | Redstone-Setup-0.2.5.exe |
| Linux, x86_64 | Redstone-0.2.5-x86_64.AppImage or redstone-desktop_0.2.5_amd64.deb |
| Linux, arm64 | Redstone-0.2.5-arm64.AppImage or redstone-desktop_0.2.5_arm64.deb |
macOS builds are signed with an Apple Developer ID and notarized, app and disk
image both. Windows and Linux are unsigned; SmartScreen will ask once.