Providers can declare `update(context)`, and the Installation section shows an Update button when an update is available. The daemon owns the operation: one per provider, joined by later requests, kept in memory past client disconnects, streamed to subscribers through an owned subscription, and aborted only when the daemon stops. The provider's answer is the outcome; the daemon adds no verification. After success it drops the cached inspection and update check and refreshes discovery, without restarting agents. Codex and Claude run their own `update` subcommand and pass the output through. Muse has no update subcommand, so it does not declare one. Updater output is capped at 64 KiB per update so a chatty updater cannot grow daemon memory. Starting an update requires daemon.manage because it runs commands on the host.
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.