mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-10 18:35:17 +00:00
Mohamed Boudra
dc85c2bfbc
Reload agent used to delete the timeline and replay the provider's history under a new epoch. That brought back turns the user had rewound and dropped anything the provider no longer had. Archive deleted the timeline too. Paseo's timeline is now the owner of the conversation. Reload agent keeps it and reconciles the provider's history append-only: turns are aligned by provider prompt id and compared exactly (prompt text, assistant and reasoning text, tool calls). When the owned conversation is a whole-segment prefix of the provider's, the rows after it are appended as new live rows. Any other difference changes nothing and agent_refreshed reports historyDiverged, which the app shows as a warning on Reload agent and Unarchive. Divergence is deliberately conservative: - An answer or tool call Paseo saw only partly can never be completed by a reload. History rows carry no turn id to update a live row in place. - A prompt sent with attachments diverges on every reload. Providers store the rendered attachment text, and the owned row keeps only the typed text. Recording the sent prompt is left to provider handoff work. Archive now only closes the runtime. Stored history, including provider children, is read without resuming or even requiring the provider. Forced provider replacement is removed. Tradeoff: an archived chat's history stays in memory until the daemon exits, measured at about 1.1-1.2x its JSON size (about 0.5 MB for a typical session, about 16 MB for a heavy tool session). Moving retained history to disk belongs to the persisted backend, not eviction, which would drop the rewinds this change keeps.
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.