byGalax
12c66d676a
The scroll-position memory introduced in 0.17.2 still produced a visible "chat appears at the top then jumps" frame when switching back into a conversation. Cause: both scroll-affecting effects (auto-bottom on new messages, restore on chat re-entry) used useEffect, which fires AFTER the browser paints the freshly-committed DOM. So users saw scrollTop=0 for one frame before the effect ran and corrected it. Switching both to useLayoutEffect moves the scroll write into the same commit phase as the message-list DOM update, so the very first paint already shows the correct position — single paint, no flicker. Co-Authored-By: Claude Opus 4.7 (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.