Mohamed BoudraandClaude
f5c6bce54f
Problem: SessionContext used useSyncedSessionState which synced every state update from React useState to Zustand, creating double overhead and complexity. Solution: Complete migration to pure Zustand architecture: - session-store.ts is now the single source of truth - Moved ALL state directly into Zustand (no React useState) - Added per-session state: messages, agents, commands, permissions, etc. - Added Zustand actions for all state updates (setMessages, setAgents, etc.) - Exported all types (MessageEntry, Agent, Command, etc.) - session-context.tsx is now a pure WebSocket message handler - Removed useSyncedSessionState hook entirely - Removed all useState calls for session state - Removed sync machinery (syncSessionField, syncSessionPartial) - WebSocket handlers now call Zustand setters directly - Context only provides imperative APIs (ws, audioPlayer, actions) - No state values in context Architecture change: Before: WebSocket → React useState → sync → Zustand (double overhead) After: WebSocket → Zustand directly (single source of truth) Benefits: - Eliminated double overhead from React → Zustand syncing - Single state update per WebSocket message - Better re-render optimization via Zustand selectors - Cleaner separation: SessionProvider = message handler, SessionStore = state - Reduced complexity: removed 400+ lines of hybrid sync code Backward compatibility: - useDaemonSession() already reads from Zustand, no changes needed - Type exports re-exported from session-store for compatibility - Components work exactly the same 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Welcome to your Expo app 👋
This is an Expo project created with create-expo-app.
Get started
-
Install dependencies
npm install -
Start the app
npx expo start
In the output, you'll find options to open the app in a
- development build
- Android emulator
- iOS simulator
- Expo Go, a limited sandbox for trying out app development with Expo
You can start developing by editing the files inside the app directory. This project uses file-based routing.
Get a fresh project
When you're ready, run:
npm run reset-project
This command will move the starter code to the app-example directory and create a blank app directory where you can start developing.
Learn more
To learn more about developing your project with Expo, look at the following resources:
- Expo documentation: Learn fundamentals, or go into advanced topics with our guides.
- Learn Expo tutorial: Follow a step-by-step tutorial where you'll create a project that runs on Android, iOS, and the web.
Join the community
Join our community of developers creating universal apps.
- Expo on GitHub: View our open source platform and contribute.
- Discord community: Chat with Expo users and ask questions.
Dictation debugging
Set EXPO_PUBLIC_ENABLE_AUDIO_DEBUG=1 before running npx expo start to render the in-app audio debug card. Pair it with the server-side STT_DEBUG_AUDIO_DIR flag so every dictation includes a copyable path to the saved raw audio file.