Multi-account switcher, chat reliability, Bedrock profiles

You can now sign into multiple accounts and switch between them from the workspace picker, the updater shows install progress in a clear card on both the login screen and sidebar, and a broad pass on chat closes long-standing reliability gaps in presence, channel membership, DMs, and rate limiting. Bedrock now supports AWS profile authentication, and a stack of follow-up fixes hardens reconnect recovery and scheduled background tasks behind the scenes.

Multi-account workspace switcher

The workspace switcher now manages multiple signed-in accounts. Add a second account, switch between them from the same dropdown, and the app reuses your existing session instead of forcing a full re-login. Each account keeps its own workspace list, so jumping between a personal account and an organization account no longer means signing out and back in.

Updater card

The small updater indicator has been replaced with a card that shows download and install progress clearly. The card appears on both the login screen and the authenticated sidebar, so you can see what is happening regardless of where you are in the app. The app also checks for pending updates far less aggressively, since the live update notice already fires immediately when one is ready.

Chat reliability

Channel membership, presence, and reconnect recovery have been substantially overhauled. Public channel member lists now load for non-members, private channels and DMs stay restricted, and rate limits are scoped per user per room with looser thresholds, so concurrent rooms no longer share a single budget and trigger spurious “Rate limit exceeded” errors during normal use.

DMs have their own streamlined path. The fake “No specialists are connected” notice that sometimes appeared in DMs is gone, and DM rename and update flows no longer fail with a permissions error for non-admin users. When a channel does have no specialists, your message now appears before the notice, in the right order. Specialists are also remembered as channel members when you @mention them, so they show up in the Members panel, and an “Invite Specialist” button is back in the channel sidebar for proactive adds.

Presence indicators now resolve display names from your workspace member list, so you no longer see raw account IDs after a reload, and the DM sidebar prefers the workspace member name over a stale participant name. Presence, typing indicators, reactions, and reconnect recovery now share a unified path, and thread replies persist reliably with thread-aware history loading.

AWS profile mode for Bedrock

Bedrock authentication now supports an AWS profile credential mode alongside IAM and personal access keys. Pick a named profile (or leave blank to use the default credential chain), and the app validates the credentials live against Bedrock before saving. AWS CLI and SSO refresh guidance is surfaced inline when validation fails, while the existing IAM-only expired-session re-entry flow stays unchanged.

Chat backend hardening

A handful of follow-up fixes shipped in 0.3.1 to address production issues. Scheduled background tasks and message archival now run reliably, restoring snapshot backups and presence processing that had been silently failing. Chat rooms also self-heal when their stored metadata is incomplete, including after the server sleeps, and connections are rejected cleanly when a room is genuinely unrecoverable instead of hanging.

Polish & fixes

Mention chips now align vertically with adjacent text in messages and use tighter padding. Channel participants load alongside the channel itself instead of after, eliminating a brief loading delay and a startup crash when a channel ID was missing. Internal data plumbing between the app and its native layer is more reliable.