5465d66edd
* feat(opencode): fill subagent descriptor with task, type, model, and tokens OpenCode subagent rows rendered with no information: the initial upsert carried only the child session title and status, so the track showed a bare title with an empty second line and the pane tab fell back to "Subagent". Fill the same provider-agnostic descriptor fields Claude populates since #2498, from data OpenCode already emits: - description <- the task tool call's description input (fallback: the child session title), so the task names the row - title <- subagent_type from the task call, else the session's agent - toolCallId <- the parent task tool call id - subtitle <- "agent · model · Variant · Nk tokens", folded from the child's own session record and assistant frames, deduped per child Facts are never inherited from the parent; absent facts render as nothing. Presentation upserts omit status so a late subtitle update cannot revert a finished child (the store's sticky contract). Both task-link orderings are handled, and the hydration path derives the same facts for historical children so restored sessions match live. Server-side only; no protocol or app changes. * fix(opencode): emit subagent type as descriptor title from assistant frames * feat(app): show subagent info line in the provider subagent pane * polish: address subagent presentation review nits * fix(opencode): link subagents from task metadata Current OpenCode task results identify their child session in tool metadata rather than the legacy textual output. Preserve that boundary field so parallel task calls retain the correct description, type, and tool-call association. --------- Co-authored-by: Mohamed Boudra <boudra.moha@gmail.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.