@agent-native/core 0.94.0 → 0.94.2

package/docs/content/locales/hi-IN/voice-input.mdx

@@ -11,9 +11,9 @@ description: "एजेंट चैट कंपोजर में वॉय
 
 ## रीयलटाइम स्पीच मोड {#realtime-speech-mode}
 
-माइक्रोफ़ोन खोलने पर एक पॉपओवर आपको **रीयलटाइम बातचीत** और **संपादन योग्य डिक्टेशन** में से चुनने देता है। रीयलटाइम मोड के लिए उपयोगकर्ता के दायरे वाली `OPENAI_API_KEY` चाहिए और यह WebRTC के ज़रिए ब्राउज़र को `gpt-realtime-2.1` से जोड़ता है। चैट नीचे दाईं ओर एक वॉइस ऑर्ब में सिमट जाती है; बातचीत समाप्त किए बिना चैट दिखाने या छिपाने के लिए ऑर्ब पर क्लिक करें।
+माइक्रोफ़ोन खोलने पर एक पॉपओवर आपको **रीयलटाइम बातचीत** और **संपादन योग्य डिक्टेशन** में से चुनने देता है। रीयलटाइम मोड के लिए उपयोगकर्ता के दायरे वाली `OPENAI_API_KEY` चाहिए और यह WebRTC के ज़रिए ब्राउज़र को `gpt-realtime-2.1` से जोड़ता है। चैट नीचे दाईं ओर एक वॉइस ऑर्ब में सिमट जाती है; बातचीत समाप्त किए बिना चैट दिखाने या छिपाने के लिए ऑर्ब पर क्लिक करें। चैट अपने-आप खुलने पर भी ऑर्ब उसके ऊपर दिखाई देता रहता है, और एक छोटा वेवफ़ॉर्म आपकी तथा सहायक की आवाज़ की गतिविधि दिखाता है।
 
-स्पीच मॉडल चैट वाले उन्हीं प्रमाणीकृत Agent Native टूल का उपयोग करता है, इसलिए वह बोलते समय ऐप में नेविगेट कर सकता है और कार्रवाइयाँ चला सकता है। जिन कार्रवाइयों के लिए स्वीकृति चाहिए, वे आपकी स्वीकृति मिलने तक रुकी रहती हैं। ऑडियो कभी भी SQL में संग्रहीत नहीं होता; Agent Native केवल सत्र और ट्रांसक्रिप्ट की संक्षिप्त स्थिति रखता है। एक रीयलटाइम सत्र अधिकतम 60 मिनट तक चलता है।
+स्पीच मॉडल चैट वाले उन्हीं प्रमाणीकृत Agent Native टूल का उपयोग करता है, इसलिए वह बोलते समय ऐप में नेविगेट कर सकता है और कार्रवाइयाँ चला सकता है। जिन कार्रवाइयों के लिए स्वीकृति चाहिए, वे आपकी स्वीकृति मिलने तक रुकी रहती हैं। केवल उपयोगकर्ता और सहायक के पूरे हुए टेक्स्ट कथन मूल चैट थ्रेड में जोड़े जाते हैं। वॉइस मोड बंद करने पर चैट खुल जाती है ताकि आप टेक्स्ट में आगे बढ़ सकें; ऑडियो या अंतरिम ट्रांसक्रिप्ट अंश सहेजे नहीं जाते। एक रीयलटाइम सत्र अधिकतम 60 मिनट तक चलता है।
 
 ## यह कैसे काम करता है {#how-it-works}
 

package/docs/content/locales/ja-JP/voice-input.mdx

@@ -11,9 +11,9 @@ description: "エージェント チャット コンポーザーでの音声デ
 
 ## リアルタイム音声モード {#realtime-speech-mode}
 
-マイクを開くと、ポップオーバーで**リアルタイム音声会話**と**編集可能な音声入力**のどちらかを選べます。リアルタイムモードにはユーザー単位の `OPENAI_API_KEY` が必要で、ブラウザから WebRTC 経由で `gpt-realtime-2.1` に接続します。チャットは右下の音声オーブに折りたたまれます。オーブをクリックすると、会話を終了せずにチャットの表示と非表示を切り替えられます。
+マイクを開くと、ポップオーバーで**リアルタイム音声会話**と**編集可能な音声入力**のどちらかを選べます。リアルタイムモードにはユーザー単位の `OPENAI_API_KEY` が必要で、ブラウザから WebRTC 経由で `gpt-realtime-2.1` に接続します。チャットは右下の音声オーブに折りたたまれます。オーブをクリックすると、会話を終了せずにチャットの表示と非表示を切り替えられます。チャットが自動的に開いた場合もオーブはその上に表示され続け、コンパクトな波形がユーザーとアシスタント双方の音声に反応します。
 
-音声モデルはチャットと同じ認証済みの Agent Native ツールを使用するため、話しながらアプリ内を移動したりアクションを呼び出したりできます。承認が必要なアクションは、承認するまで一時停止したままです。音声は SQL に一切保存されず、Agent Native が保持するのは簡潔なセッション状態と文字起こし状態だけです。リアルタイムセッションの上限は 60 分です。
+音声モデルはチャットと同じ認証済みの Agent Native ツールを使用するため、話しながらアプリ内を移動したりアクションを呼び出したりできます。承認が必要なアクションは、承認するまで一時停止したままです。完了したユーザーとアシスタントの発話テキストだけが開始時のチャットスレッドに追加されます。音声モードを終了するとチャットが開き、テキストで続けられます。音声や途中の文字起こしは保存されません。リアルタイムセッションの上限は 60 分です。
 
 ## 仕組み {#how-it-works}
 

package/docs/content/locales/ko-KR/voice-input.mdx

@@ -11,9 +11,9 @@ description: "에이전트 채팅 작성기의 음성 받아쓰기 — Builder G
 
 ## 실시간 음성 모드 {#realtime-speech-mode}
 
-마이크를 열면 팝오버에서 **실시간 음성 대화**와 **편집 가능한 받아쓰기** 중 하나를 선택할 수 있습니다. 실시간 모드에는 사용자 범위의 `OPENAI_API_KEY`가 필요하며, WebRTC를 통해 브라우저를 `gpt-realtime-2.1`에 연결합니다. 채팅은 오른쪽 아래의 음성 오브로 접힙니다. 오브를 클릭하면 대화를 끝내지 않고 채팅을 표시하거나 숨길 수 있습니다.
+마이크를 열면 팝오버에서 **실시간 음성 대화**와 **편집 가능한 받아쓰기** 중 하나를 선택할 수 있습니다. 실시간 모드에는 사용자 범위의 `OPENAI_API_KEY`가 필요하며, WebRTC를 통해 브라우저를 `gpt-realtime-2.1`에 연결합니다. 채팅은 오른쪽 아래의 음성 오브로 접힙니다. 오브를 클릭하면 대화를 끝내지 않고 채팅을 표시하거나 숨길 수 있습니다. 채팅이 자동으로 열려도 오브는 채팅 위에 계속 표시되며, 작은 파형이 사용자와 어시스턴트의 실제 음성 활동에 반응합니다.
 
-음성 모델은 채팅과 동일한 인증된 Agent Native 도구를 사용하므로 말하는 동안 앱을 탐색하고 작업을 호출할 수 있습니다. 승인이 필요한 작업은 사용자가 승인할 때까지 일시 중지된 상태로 유지됩니다. 오디오는 SQL에 저장되지 않으며 Agent Native는 간결한 세션 및 대화 내용 상태만 보관합니다. 실시간 세션은 최대 60분 동안 지속됩니다.
+음성 모델은 채팅과 동일한 인증된 Agent Native 도구를 사용하므로 말하는 동안 앱을 탐색하고 작업을 호출할 수 있습니다. 승인이 필요한 작업은 사용자가 승인할 때까지 일시 중지된 상태로 유지됩니다. 완료된 사용자 및 어시스턴트 발화 텍스트만 처음 시작한 채팅 스레드에 추가됩니다. 음성 모드를 종료하면 채팅이 열려 텍스트로 이어갈 수 있으며, 오디오나 임시 전사 조각은 저장되지 않습니다. 실시간 세션은 최대 60분 동안 지속됩니다.
 
 ## 작동 방식 {#how-it-works}
 

package/docs/content/locales/pt-BR/voice-input.mdx

@@ -11,9 +11,9 @@ A estrutura lida com tudo isso automaticamente. Os usuários conectados ao Build
 
 ## Modo de voz em tempo real {#realtime-speech-mode}
 
-Ao abrir o microfone, um popover permite escolher entre **Conversa em tempo real** e **Ditado editável**. O modo em tempo real exige uma `OPENAI_API_KEY` no escopo do usuário e conecta o navegador ao `gpt-realtime-2.1` por WebRTC. O chat se recolhe em uma esfera de voz no canto inferior direito; clique nela para mostrar ou ocultar o chat sem encerrar a conversa.
+Ao abrir o microfone, um popover permite escolher entre **Conversa em tempo real** e **Ditado editável**. O modo em tempo real exige uma `OPENAI_API_KEY` no escopo do usuário e conecta o navegador ao `gpt-realtime-2.1` por WebRTC. O chat se recolhe em uma esfera de voz no canto inferior direito; clique nela para mostrar ou ocultar o chat sem encerrar a conversa. A esfera permanece visível sobre o chat mesmo quando ele abre automaticamente, e uma forma de onda compacta reage à sua voz e à voz do assistente.
 
-O modelo de voz usa as mesmas ferramentas autenticadas do Agent Native que o chat, portanto pode navegar pelo aplicativo e chamar ações enquanto fala. Ações que exigem aprovação permanecem pausadas até você aprová-las. O áudio nunca é armazenado no SQL; o Agent Native mantém apenas um estado compacto da sessão e da transcrição. Uma sessão em tempo real dura no máximo 60 minutos.
+O modelo de voz usa as mesmas ferramentas autenticadas do Agent Native que o chat, portanto pode navegar pelo aplicativo e chamar ações enquanto fala. Ações que exigem aprovação permanecem pausadas até você aprová-las. Somente as falas de texto concluídas do usuário e do assistente são adicionadas à conversa original. Ao encerrar o modo de voz, o chat é aberto para você continuar por texto; o áudio e os trechos provisórios da transcrição não são armazenados. Uma sessão em tempo real dura no máximo 60 minutos.
 
 ## Como funciona {#how-it-works}
 

package/docs/content/locales/zh-CN/voice-input.mdx

@@ -11,9 +11,9 @@ description: "代理聊天编辑器中的语音听写 - Builder Gemini、BYOK
 
 ## 实时语音模式 {#realtime-speech-mode}
 
-打开麦克风后，弹出菜单让你在**实时语音对话**和**可编辑听写**之间选择。实时模式需要用户范围的 `OPENAI_API_KEY`，并通过 WebRTC 将浏览器连接到 `gpt-realtime-2.1`。聊天会收起为右下角的语音球；点击语音球即可显示或隐藏聊天，而不会结束对话。
+打开麦克风后，弹出菜单让你在**实时语音对话**和**可编辑听写**之间选择。实时模式需要用户范围的 `OPENAI_API_KEY`，并通过 WebRTC 将浏览器连接到 `gpt-realtime-2.1`。聊天会收起为右下角的语音球；点击语音球即可显示或隐藏聊天，而不会结束对话。即使聊天自动打开，语音球也会保持显示在聊天上方；紧凑的波形会实时响应你和助手的声音。
 
-语音模型使用与聊天相同的、经过身份验证的 Agent Native 工具，因此可以一边说话，一边在应用中导航和调用操作。需要审批的操作会保持暂停，直到你批准为止。音频绝不会存储到 SQL 中；Agent Native 只保留精简的会话和转录状态。实时会话最长可持续 60 分钟。
+语音模型使用与聊天相同的、经过身份验证的 Agent Native 工具，因此可以一边说话，一边在应用中导航和调用操作。需要审批的操作会保持暂停，直到你批准为止。只有用户和助手已经完成的文本话语会追加到开始语音时的聊天线程。结束语音模式后，聊天会自动打开，方便你继续输入文字；音频和临时转录片段都不会保存。实时会话最长可持续 60 分钟。
 
 ## 它是如何工作的 {#how-it-works}
 

package/docs/content/locales/zh-TW/voice-input.mdx

@@ -11,9 +11,9 @@ description: "代理聊天編輯器中的語音聽寫 - Builder Gemini、BYOK
 
 ## 即時語音模式 {#realtime-speech-mode}
 
-開啟麥克風後，彈出式選單會讓您在**即時語音對話**和**可編輯聽寫**之間選擇。即時模式需要使用者範圍的 `OPENAI_API_KEY`，並透過 WebRTC 將瀏覽器連線到 `gpt-realtime-2.1`。聊天會收合為右下角的語音球；點選語音球即可顯示或隱藏聊天，而不會結束對話。
+開啟麥克風後，彈出式選單會讓您在**即時語音對話**和**可編輯聽寫**之間選擇。即時模式需要使用者範圍的 `OPENAI_API_KEY`，並透過 WebRTC 將瀏覽器連線到 `gpt-realtime-2.1`。聊天會收合為右下角的語音球；點選語音球即可顯示或隱藏聊天，而不會結束對話。即使聊天自動開啟，語音球也會持續顯示在聊天上方；精簡的波形會即時回應您和助理的聲音。
 
-語音模型使用與聊天相同且經過驗證的 Agent Native 工具，因此可以一邊說話，一邊在應用程式中導覽和呼叫動作。需要核准的動作會維持暫停，直到您核准為止。音訊絕不會儲存到 SQL 中；Agent Native 只保留精簡的工作階段和轉錄狀態。即時工作階段最長可持續 60 分鐘。
+語音模型使用與聊天相同且經過驗證的 Agent Native 工具，因此可以一邊說話，一邊在應用程式中導覽和呼叫動作。需要核准的動作會維持暫停，直到您核准為止。只有使用者和助理已完成的文字發言會附加到開始語音時的聊天討論串。結束語音模式後，聊天會自動開啟，方便您繼續輸入文字；音訊和暫時的轉錄片段都不會儲存。即時工作階段最長可持續 60 分鐘。
 
 ## 它是如何工作的 {#how-it-works}
 

package/docs/content/sharing.mdx

@@ -1,13 +1,13 @@
 ---
 title: "Sharing & Privacy"
-description: "Familiar, consistent sharing built into the framework. Every user-created resource — docs, dashboards, designs, decks, clips, recordings, forms — gets the same private-by-default model with one consistent share UI."
+description: "Google-Docs-style sharing, built into the framework. Every user-created resource — docs, dashboards, designs, decks, clips, recordings, forms — gets the same private-by-default model with one consistent share UI."
 ---
 
 # Sharing & Privacy
 
 Every resource a user creates in an agent-native app — a document, a dashboard, a design, a deck, a screen recording, a meeting transcript, a form, a booking link — is **private to the creator by default**. Other people see it only when the creator explicitly shares it, or changes its visibility to `org` or `public`.
 
-It's one familiar sharing model everywhere: the same share button, the same dialog, the same three-tier visibility model, the same per-user/per-org grants — across every template, with no per-app reinvention.
+It looks and works like Google Docs. The same share button, the same dialog, the same three-tier visibility model, the same per-user/per-org grants — across every template, with no per-app reinvention.
 
 ## Why one model {#why}
 
@@ -92,7 +92,7 @@ Every template that stores user-authored work uses this model. Concretely:
 - **Content** — documents
 - **Slides** — decks
 - **Design** — designs and assets
-- **Clips** — screen recordings
+- **Clips** — screen recordings (Loom-style)
 - **Plan** — visual plans and PR recaps
 - **Forms** — form definitions
 - **Calendar** — events and booking links
@@ -115,7 +115,7 @@ Every shareable resource gets a share button in its header. Clicking it opens a
 
 - Visibility selector (`Private` / `Organization` / `Public link`).
 - "Add people or teams" autocomplete — search users in the org or paste an email.
-- A `Notify people` checkbox for individual email grants.
+- A Google Docs-style `Notify people` checkbox for individual email grants.
 - A list of current grants with role pickers and a remove control.
 - A copy-link button that respects the current visibility.
 

package/docs/content/template-analytics.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Analytics"
-description: "Ask analytics questions in plain English, get charts and dashboards back — connect your own warehouse and event sources, and own the code and the data."
+description: "Ask analytics questions in plain English, get charts and dashboards back — an open-source replacement for Amplitude, Mixpanel, and Looker that connects your own warehouse and event sources."
 ---
 
 # Analytics
@@ -16,7 +16,7 @@ Ask analytics questions in plain English, get charts and dashboards back. The ag
   />
 </WireframeBlock>
 
-It's an open-source analytics stack for teams that want to own the code, the queries, and the data.
+It's an open-source replacement for Amplitude, Mixpanel, and Looker — for teams that want to own the code, the queries, and the data.
 
 <Diagram id="doc-block-9n9ub7" title="Question to chart" summary="The agent consults the data dictionary, writes SQL, validates it against the warehouse, then renders a chart or saves a panel.">
 

package/docs/content/template-calendar.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Calendar"
-description: "An agent-powered calendar with Google Calendar sync and shareable booking pages. Schedule, find slots, and manage availability through plain English."
+description: "An agent-powered calendar with Google Calendar sync and Calendly-style booking links. Schedule, find slots, and manage availability through plain English."
 ---
 
 # Calendar
 
-An agent-powered calendar app. Connect your Google Calendar and the agent can read your schedule, find free slots, create events, and manage shareable booking links — all in plain English. It brings your calendar and public booking pages into one app you own.
+An agent-powered calendar app. Connect your Google Calendar and the agent can read your schedule, find free slots, create events, and manage Calendly-style booking links — all in plain English. It replaces the Google Calendar + Calendly combo with one app you own.
 
 <WireframeBlock id="doc-block-6wsrao">
   <Screen
@@ -167,7 +167,7 @@ Under the hood the agent calls actions like `list-events`, `check-availability`,
 Defined in `templates/calendar/server/db/schema.ts`. Only non-event data is stored locally:
 
 - `bookings` — confirmed appointments from public booking pages. Stores name, email, start, end, slug, optional notes, custom field responses, meeting link, a `cancelToken` for the public manage URL, and a `confirmed` or `cancelled` status.
-- `booking_links` — the booking-page link definitions. Slug, title, description, primary `duration`, optional `durations` list, `customFields`, `conferencing`, `color`, and an `isActive` flag. Uses the framework's `ownableColumns` so the sharing system applies.
+- `booking_links` — the Calendly-style link definitions. Slug, title, description, primary `duration`, optional `durations` list, `customFields`, `conferencing`, `color`, and an `isActive` flag. Uses the framework's `ownableColumns` so the sharing system applies.
 - `booking_slug_redirects` — remembers old slugs when a link is renamed so existing public URLs keep working.
 - `booking_link_shares` — share grants for booking links.
 
@@ -181,7 +181,7 @@ Defined in `templates/calendar/server/db/schema.ts`. Only non-event data is stor
     {
       id: "booking_links",
       name: "booking_links",
-      note: "Booking-page link definitions (ownable)",
+      note: "Calendly-style link definitions (ownable)",
       fields: [
         {
           name: "id",

package/docs/content/template-clips.mdx

@@ -17,7 +17,7 @@ A capture-everything app: screen recordings, meeting notes from your calendar, a
   />
 </WireframeBlock>
 
-Async screen recordings, calendar-synced meeting notes, and push-to-talk voice dictation rolled into one app — the agent is a first-class editor across every surface, and the recordings, meetings, and dictations are yours, not a SaaS vendor's. Clips also makes shared recordings agent-readable: paste a public Clips share link or a temporary **Copy for agent** link into an agent and it can "hear" the transcript as text and "see" timestamped screen frames as images — no raw video needed. Frame-viewing works in any image-capable agent (ChatGPT, Claude Code, Cursor, Codex); text-only web chats still get the full transcript and can take a frame you upload.
+Think along the lines of Loom + Granola + Wispr Flow rolled into one app: async screen recordings, calendar-synced meeting notes, and push-to-talk voice dictation — but the agent is a first-class editor across every surface, and the recordings, meetings, and dictations are yours, not a SaaS vendor's. Clips also makes shared recordings agent-readable: paste a public Clips share link or a temporary **Copy for agent** link into an agent and it can "hear" the transcript as text and "see" timestamped screen frames as images — no raw video needed. Frame-viewing works in any image-capable agent (ChatGPT, Claude Code, Cursor, Codex); text-only web chats still get the full transcript and can take a frame you upload.
 
 <Diagram id="doc-block-pqnd4p" title="Capture, transcribe, reuse" summary={"Three capture types land in one library; the agent transcribes, titles, and summarizes, then every transcript is searchable and shareable."}>
 
@@ -85,7 +85,7 @@ Async screen recordings, calendar-synced meeting notes, and push-to-talk voice d
 - **Get an auto-generated title, summary, and chapter markers** for every recording — the agent fills them in and keeps them current.
 - **Search across every transcript** — screen recordings, meetings, and dictations all in one library. "Find the clip where we discussed the rollout plan."
 - **Share clips** with per-clip permissions (public, team, private). Link tracking and threaded comments work too.
-- **Preview public clips in Slack** with a playable video unfurl after the
+- **Preview public clips in Slack** with a Loom-style playable unfurl after the
   workspace installs your Clips Slack app.
 - **Capture browser logs with the Chrome extension.** Browser recordings can
   attach redacted console logs and fetch/XHR metadata, which is helpful for

package/docs/content/template-content.mdx

@@ -1,15 +1,15 @@
 ---
 title: "Content"
-description: "A local-file-friendly document workspace: edit Markdown/MDX files, generate rich interactive custom blocks, and write together with an AI agent."
+description: "Open-source Obsidian for MDX: edit local Markdown/MDX files, generate rich interactive custom blocks, and write with an AI agent."
 ---
 
 # Content
 
-Content is a local-file-friendly document workspace where the agent can read,
-write, reorganize, and publish pages for you. Open a doc, ask "rewrite this
-paragraph to be more concise" or "create a page called Q4 Planning with
-sub-pages for Goals, Metrics, and Risks" - same result whether you do it
-yourself or ask.
+Content is open-source Obsidian for MDX: a local-file-friendly document
+workspace where the agent can read, write, reorganize, and publish pages for
+you. Open a doc, ask "rewrite this paragraph to be more concise" or "create a
+page called Q4 Planning with sub-pages for Goals, Metrics, and Risks" - same
+result whether you do it yourself or ask.
 
 <WireframeBlock id="doc-block-1i1ubpx">
   <Screen
@@ -90,7 +90,7 @@ When you open the app, you'll see a page tree next to the editor. The agent alwa
 - **Write rich text** with headings, lists, tables, code blocks, images, and links. Slash commands (`/`) insert blocks; selecting text pops up a formatting toolbar.
 - **Organize pages in a tree** — nest infinitely, drag to reorder, favorite pages you use often.
 - **Search across everything** with full-text search across titles and content.
-- **Edit local Markdown/MDX files with your own tools.** Use the `/local-files` view
+- **Edit local Markdown/MDX files like Obsidian.** Use the `/local-files` view
   to export your workspace to files, edit them in your own tools, preview
   changes, and import them back. In Local File Mode, Content writes straight to
   the selected `.md` or `.mdx` file.
@@ -119,8 +119,9 @@ Select text and hit Cmd+I to focus the agent with that selection pre-loaded —
 ## Local Markdown/MDX files {#local-files}
 
 Content can round-trip documents through local files without cloning or running
-the Content app locally. Files stay inspectable and editable on disk, while the
-app gives you a rich editor, agent actions, sharing, and custom blocks. Open
+the Content app locally. It feels like Obsidian for MDX: files stay inspectable
+and editable on disk, while the app gives you a rich editor, agent actions,
+sharing, and custom blocks. Open
 `/local-files`, choose a folder in your browser or Agent Native Desktop, and
 export the current document tree as Markdown/MDX under `content/`.
 
@@ -141,7 +142,7 @@ truth instead of SQL documents. Add `agent-native.json` to a repo, set
 `content/`, and `resources/`. The standard Content editor then populates its
 left sidebar from those local `.md`/`.mdx` files and writes edits back to the
 selected file through the normal document actions. Use this for repo-first docs,
-blogs, resource libraries, or a personal MDX-powered notes vault; switch back to
+blogs, resource libraries, or an Obsidian-style personal MDX-powered notes vault; switch back to
 database mode when you want hosted collaboration and SQL-backed sharing. See [Local File Mode](/docs/local-file-mode) for the
 standalone repo layout, configuration, custom MDX components, local
 `extensions/` widgets, and production safety guide.
@@ -218,7 +219,7 @@ Local file workspaces can also provide repo-local React components through the
 configured `components` folder. The Content dev server imports PascalCase
 exports from those files, renders matching MDX tags such as `<ImpactCounter />`
 inside the editor, and exposes them in the slash menu under Local components.
-This is the local-first custom-block layer: custom MDX blocks stay local to the
+This is the "Obsidian for MDX" layer: custom MDX blocks stay local to the
 workspace, but the editor can render them and the agent can generate or update
 their source without cloning the Content app. A minimal workspace component can
 be:

package/docs/content/template-mail.mdx

@@ -5,7 +5,7 @@ description: "An agent-powered email client. Connect your Gmail and the agent ca
 
 # Mail
 
-An agent-powered email client. Connect your Gmail account and the agent can read, draft, send, and organize email for you — alongside a fast, keyboard-first inbox you can drive yourself, with the agent as a first-class citizen and the codebase yours to own.
+An agent-powered email client. Connect your Gmail account and the agent can read, draft, send, and organize email for you — alongside a fast, keyboard-first inbox you can drive yourself. Think Superhuman, but the agent is a first-class citizen and the codebase is yours to own.
 
 <WireframeBlock id="doc-block-ofadgy">
   <Screen

package/docs/content/template-slides.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Slides"
-description: "Generate decks from a prompt, edit visually, and present full-screen — an open-source deck editor with import/export, design systems, and real-time collaboration built in."
+description: "Generate decks from a prompt, edit visually, and present full-screen — an open-source replacement for Google Slides, Pitch, and PowerPoint, with import/export, design systems, and real-time collaboration built in."
 ---
 
 # Slides
 
-Generate full presentation decks from a prompt, edit slides visually, and present full-screen. Ask the agent for "a 10-slide pitch deck for a coffee subscription service" and watch it stream slide-by-slide into the editor in seconds. It's an open-source deck editor you own end to end — generate, import, edit, present, and export without a subscription.
+Generate full presentation decks from a prompt, edit slides visually, and present full-screen. Ask the agent for "a 10-slide pitch deck for a coffee subscription service" and watch it stream slide-by-slide into the editor in seconds. It's an open-source replacement for Google Slides, Pitch, and PowerPoint — a deck editor you own end to end: generate, import, edit, present, and export without a subscription.
 
 <WireframeBlock id="doc-block-eqogw6">
   <Screen

package/docs/content/voice-input.mdx

@@ -125,9 +125,9 @@ You don't need to call this directly — the composer does. If you're building a
 
 ## Realtime speech mode {#realtime-speech-mode}
 
-Beyond one-shot dictation, the composer also offers a live, hands-free conversation mode. When the mic opens, a popover lets you choose **Realtime speech** or **Editable dictation**. Realtime speech requires a user-scoped `OPENAI_API_KEY` and connects the browser to `gpt-realtime-2.1` over WebRTC. The chat collapses into a speech orb in the bottom-end corner; click the orb to show or hide chat without ending the conversation.
+Beyond one-shot dictation, the composer also offers a live, hands-free conversation mode. When the mic opens, a popover lets you choose **Realtime speech** or **Editable dictation**. Realtime speech requires a user-scoped `OPENAI_API_KEY` and connects the browser to `gpt-realtime-2.1` over WebRTC. The chat collapses into a speech orb in the bottom-end corner; click the orb to show or hide chat without ending the conversation. The orb stays visible above the chat even if the chat opens automatically, and its compact waveform reacts to your voice and the assistant's voice.
 
-The speech model uses the same authenticated Agent Native tools as chat, so it can navigate the app and call actions while it talks. Approval-gated actions remain paused until you approve them. Audio is never stored in SQL; Agent Native keeps only compact session and transcript state. A realtime session lasts at most 60 minutes.
+The speech model uses the same authenticated Agent Native tools as chat, so it can navigate the app and call actions while it talks. Approval-gated actions remain paused until you approve them. Only completed user and assistant text turns are appended to the original chat thread. Ending voice mode opens that chat so you can continue over text; audio and interim transcript fragments are never stored. A realtime session lasts at most 60 minutes.
 
 ## Customizing the provider {#customizing}
 

package/docs/content/workspace.mdx

@@ -86,7 +86,7 @@ The twist: **it's SQL rows, not filesystem files.** Each user gets their own wor
 | Per-project `CLAUDE.md` / skills | Per-app `AGENTS.md` + workspace memory resources   |
 | MCP config in a JSON file        | MCP config in JSON _or_ the settings UI, per scope |
 
-Same capabilities. Different economics. See [Apps](/docs/cloneable-saas) for why this matters for SaaS.
+Same capabilities. Different economics. See [Templates](/docs/cloneable-saas) for why this matters for SaaS.
 
 ## Overview {#overview}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.94.0",
+  "version": "0.94.2",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {

package/src/templates/workspace-core/.agents/skills/voice-transcription/SKILL.md

@@ -46,8 +46,11 @@ from the dictation providers below. It requires the authenticated user's
 configuration, and keeps the key out of browser code.
 
 - Starting voice mode collapses the chat into a persistent bottom-end speech
-  orb. Clicking the orb shows or hides chat without ending the session; ending
-  the session is a separate, explicit control.
+  orb. The orb stays visible above the chat even when the chat opens
+  automatically. Clicking it shows or hides chat without ending the session;
+  ending the session is a separate, explicit control.
+- The orb's compact waveform must reflect actual microphone or assistant audio
+  activity. It is an audio-level indicator, not a decorative animation.
 - Semantic VAD keeps listening, starts responses automatically, and supports
   barge-in while the agent is speaking.
 - Function calls must cross the authenticated realtime tool bridge and enter
@@ -57,9 +60,12 @@ configuration, and keeps the key out of browser code.
 - Preserve the active browser-tab id in request context so `set-url`,
   `set-search-params`, `view-screen`, and tab-scoped application state affect
   the app the user is actually speaking to.
-- Do not persist audio. Store only compact lifecycle and latest-transcript
-  context at `application_state["realtime-voice-session"]`; delete it when the
-  session ends.
+- Do not persist audio or interim transcript deltas. Append completed user and
+  assistant utterances as ordinary text messages to the exact chat thread
+  captured when the session starts. Ending voice mode opens that chat so the
+  user can continue over text. Store only compact lifecycle and latest context
+  at `application_state["realtime-voice-session"]`; delete it when the session
+  ends.
 - Missing-key failures should open Settings focused on the user-scoped
   `OPENAI_API_KEY` field. Never send, log, or echo the key to the browser.