The new-tab menu handler registered itself as `workspace-new-tab-menu:<serverId>:<paneId>`, leaving out the workspace. Pane ids are namespaced per workspace — every workspace's default pane is called "main" — so all workspaces on a host produced the same handler id. The deck keeps several workspaces mounted at once, the dispatcher stores one live handler per id, and useKeyboardActionHandler registers once per id and never re-registers on focus change. So the second workspace to mount evicted the first, and switching back left a mounted, focused workspace with no handler at all: Cmd+T and Cmd+Shift+A/T/C/E silently did nothing until the newer entry expired from the deck. Handler ids are now built from the surface's full identity rather than assembled at the call site, so the workspace can't be dropped again. The three workspace-wide handlers move onto the same constructor; they were already correct, but the shape belongs in one place.
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.