byGalax
89003f71a4
The residual flicker on chat switch was a loading/reveal artifact, not scroll. listReady gated the MessageList reveal on reactionsReady OR a 300ms timeout, so on a cache-hit switch (messages already present from the first render) the list sat at opacity:0 for up to 300ms and then popped in. Drop the reactions/timeout gate: reveal as soon as messages exist. Reaction chips stream in a beat later; because the list is pinned to the bottom their height growth re-pins with no visible jump, and MessageList still defers its own reveal a few frames until the row-height measurement settles so it appears already at the final bottom. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@chat-app/desktop
Tauri v2 + React + Vite + Tailwind desktop client (macOS / Windows / Linux).
Prerequisites
- Node 22+, pnpm 9+
- Rust + Cargo (install via https://rustup.rs)
- Platform build deps:
- macOS: Xcode Command Line Tools
- Linux:
libwebkit2gtk-4.1-dev,build-essential,libssl-dev(Debian/Ubuntu) - Windows: Microsoft C++ Build Tools + WebView2
Dev
# from repo root
pnpm install
pnpm desktop:dev # tauri dev — launches Vite + native window
pnpm desktop:build # production bundle per platform
Layout
src/— React app (Vite bundles intodist/).src-tauri/— Rust backend.main.rswires Tauri plugins.vite.config.ts— port1420, HMR on1421, aliases to shared packages.
Secure Storage
Session tokens + user private keys live in Stronghold (tauri-plugin-stronghold).
Local message history lives in SQLite (tauri-plugin-sql), DB file encrypted at rest.