@agent-native/core 0.92.12 → 0.94.0

package/corpus/templates/calendar/server/handlers/events.ts

@@ -43,10 +43,17 @@ async function resolveAccountEmail(
   requestAccountEmail: string | undefined,
   ownerEmail: string,
 ): Promise<string> {
-  if (!requestAccountEmail || requestAccountEmail === ownerEmail) {
+  if (requestAccountEmail === ownerEmail) {
     return ownerEmail;
   }
   const status = await googleCalendar.getAuthStatus(ownerEmail);
+  if (!requestAccountEmail) {
+    return (
+      status.accounts.find((account) => account.email === ownerEmail)?.email ??
+      status.accounts[0]?.email ??
+      ownerEmail
+    );
+  }
   const isOwned = status.accounts.some((a) => a.email === requestAccountEmail);
   if (!isOwned) {
     throw new ForbiddenError("Account not owned by current user");
@@ -290,6 +297,7 @@ export const createEvent = defineEventHandler(async (event: H3Event) => {
     }
 
     const result = await googleCalendar.createEvent(calEvent, {
+      account: { ownerEmail: email, accountEmail: acctEmail },
       addGoogleMeet: shouldAutoAddGoogleMeet(calEvent, {
         addGoogleMeet:
           typeof addGoogleMeet === "boolean" ? addGoogleMeet : undefined,
@@ -372,7 +380,10 @@ export const updateEvent = defineEventHandler(async (event: H3Event) => {
 
     let existingEvent: CalendarEvent | undefined;
     const loadExistingEvent = async () => {
-      existingEvent ??= await googleCalendar.getEvent(googleEventId, acctEmail);
+      existingEvent ??= await googleCalendar.getEvent(googleEventId, {
+        ownerEmail: email,
+        accountEmail: acctEmail,
+      });
       return existingEvent;
     };
 
@@ -415,6 +426,7 @@ export const updateEvent = defineEventHandler(async (event: H3Event) => {
 
     try {
       const result = await googleCalendar.updateEvent(googleEventId, updates, {
+        account: { ownerEmail: email, accountEmail: acctEmail },
         sendUpdates:
           sendUpdates ?? (guestNotificationMessage ? "all" : undefined),
         addGoogleMeet: addGoogleMeet === true,
@@ -521,7 +533,10 @@ export const deleteEvent = defineEventHandler(async (event: H3Event) => {
     const shouldNotifyGuests = !!guestNotificationMessage && !removeOnly;
     const effectiveSendUpdates = removeOnly ? "none" : sendUpdates;
     const eventForNotification = shouldNotifyGuests
-      ? await googleCalendar.getEvent(googleEventId, accountEmail)
+      ? await googleCalendar.getEvent(googleEventId, {
+          ownerEmail: email,
+          accountEmail,
+        })
       : undefined;
 
     try {
@@ -529,15 +544,19 @@ export const deleteEvent = defineEventHandler(async (event: H3Event) => {
         // Non-organizer: decline the event to remove from calendar
         await googleCalendar.removeEventFromCalendar(
           googleEventId,
-          accountEmail,
+          { ownerEmail: email, accountEmail },
           { scope, sendUpdates: effectiveSendUpdates },
         );
       } else {
         // Organizer: actually delete the event
-        await googleCalendar.deleteEvent(googleEventId, accountEmail, {
-          scope,
-          sendUpdates: effectiveSendUpdates,
-        });
+        await googleCalendar.deleteEvent(
+          googleEventId,
+          { ownerEmail: email, accountEmail },
+          {
+            scope,
+            sendUpdates: effectiveSendUpdates,
+          },
+        );
       }
     } catch (error: any) {
       setResponseStatus(event, 500);
@@ -614,7 +633,7 @@ export const rsvpEvent = defineEventHandler(async (event: H3Event) => {
       await googleCalendar.rsvpEvent(
         googleEventId,
         status,
-        acctEmail,
+        { ownerEmail: email, accountEmail: acctEmail },
         scope,
         note,
         sendUpdates,

package/corpus/templates/calendar/server/lib/google-calendar.ts

@@ -574,6 +574,54 @@ export async function getClient(
   return { accessToken };
 }
 
+export interface GoogleAccountSelection {
+  ownerEmail: string;
+  accountEmail: string;
+}
+
+export async function getDefaultAccountSelection(
+  ownerEmail: string,
+): Promise<GoogleAccountSelection> {
+  const accounts = await listOAuthAccountsByOwner("google", ownerEmail);
+  const account =
+    accounts.find(
+      (candidate) =>
+        candidate.accountId.trim().toLowerCase() ===
+        ownerEmail.trim().toLowerCase(),
+    ) ?? accounts[0];
+  if (!account) {
+    throw new Error(
+      "Google Calendar not connected. Connect via Settings first.",
+    );
+  }
+  return { ownerEmail, accountEmail: account.accountId };
+}
+
+/** Resolve one connected Google account beneath its signed-in owner. */
+export async function getClientForAccount({
+  ownerEmail,
+  accountEmail,
+}: GoogleAccountSelection): Promise<{ accessToken: string }> {
+  const normalizedAccountEmail = accountEmail.trim().toLowerCase();
+  const accounts = await listOAuthAccountsByOwner("google", ownerEmail);
+  const account = accounts.find(
+    (candidate) =>
+      candidate.accountId.trim().toLowerCase() === normalizedAccountEmail,
+  );
+  if (!account) {
+    throw new Error(
+      `Google Calendar account not connected for this user: ${accountEmail}`,
+    );
+  }
+
+  const accessToken = await getValidAccessToken(
+    account.accountId,
+    account.tokens as unknown as GoogleTokens,
+    ownerEmail,
+  );
+  return { accessToken };
+}
+
 /**
  * Get OAuth credentials. When `forEmail` is provided, returns only that
  * user's credentials (multi-user mode). Otherwise returns an empty array.
@@ -1006,14 +1054,9 @@ export async function listOverlayEvents(
 
 export async function getEvent(
   googleEventId: string,
-  accountEmail: string,
+  account: GoogleAccountSelection,
 ): Promise<CalendarEvent> {
-  const client = await getClient(accountEmail);
-  if (!client) {
-    throw new Error(
-      `Google Calendar account not connected: ${accountEmail || "selected account"}`,
-    );
-  }
+  const client = await getClientForAccount(account);
 
   const event = await calendarGetEvent(
     client.accessToken,
@@ -1035,7 +1078,7 @@ export async function getEvent(
     source: "google",
     googleEventId: event.id || undefined,
     htmlLink: event.htmlLink || undefined,
-    accountEmail,
+    accountEmail: account.accountEmail,
     responseStatus: selfAttendee?.responseStatus || undefined,
     transparency: event.transparency || undefined,
     ...mapColor(event),
@@ -1060,7 +1103,8 @@ export async function getEvent(
 
 export async function createEvent(
   event: CalendarEvent,
-  opts?: {
+  opts: {
+    account: GoogleAccountSelection;
     addGoogleMeet?: boolean;
     sendUpdates?: "all" | "externalOnly" | "none";
   },
@@ -1070,8 +1114,7 @@ export async function createEvent(
   meetLink?: string;
   conferenceData?: CalendarEvent["conferenceData"];
 }> {
-  const client = await getClient(event.accountEmail);
-  if (!client) return {};
+  const client = await getClientForAccount(opts.account);
   if (
     (event.eventType === "outOfOffice" || event.eventType === "focusTime") &&
     event.allDay
@@ -1131,7 +1174,8 @@ export async function createEvent(
 export async function updateEvent(
   googleEventId: string,
   event: Partial<CalendarEvent>,
-  options?: {
+  options: {
+    account: GoogleAccountSelection;
     sendUpdates?: "all" | "none";
     addGoogleMeet?: boolean;
     scope?: UpdateEventScope;
@@ -1142,12 +1186,7 @@ export async function updateEvent(
   conferenceData?: CalendarEvent["conferenceData"];
   attendees?: CalendarEvent["attendees"];
 }> {
-  const client = await getClient(event.accountEmail);
-  if (!client) {
-    throw new Error(
-      `Google Calendar account not connected: ${event.accountEmail ?? "selected account"}`,
-    );
-  }
+  const client = await getClientForAccount(options.account);
 
   let targetEventId = googleEventId;
   let eventPatch = event;
@@ -1252,18 +1291,13 @@ export async function updateEvent(
 
 export async function deleteEvent(
   googleEventId: string,
-  accountEmail?: string,
+  account: GoogleAccountSelection,
   options?: {
     scope?: "single" | "all" | "thisAndFollowing";
     sendUpdates?: "all" | "none";
   },
 ): Promise<void> {
-  const client = await getClient(accountEmail);
-  if (!client) {
-    throw new Error(
-      `Google Calendar account not connected: ${accountEmail ?? "selected account"}`,
-    );
-  }
+  const client = await getClientForAccount(account);
 
   const scope = options?.scope || "single";
   const sendUpdates = options?.sendUpdates;
@@ -1358,16 +1392,13 @@ export async function deleteEvent(
  */
 export async function removeEventFromCalendar(
   googleEventId: string,
-  accountEmail: string,
+  account: GoogleAccountSelection,
   options?: {
     scope?: "single" | "all" | "thisAndFollowing";
     sendUpdates?: "all" | "none";
   },
 ): Promise<void> {
-  const client = await getClient(accountEmail);
-  if (!client) {
-    throw new Error(`Google Calendar account not connected: ${accountEmail}`);
-  }
+  const client = await getClientForAccount(account);
 
   const scope = options?.scope || "single";
   const sendUpdates = options?.sendUpdates;
@@ -1444,22 +1475,19 @@ async function rsvpSingleEvent(
 export async function rsvpEvent(
   googleEventId: string,
   responseStatus: "accepted" | "declined" | "tentative",
-  accountEmail: string,
+  account: GoogleAccountSelection,
   scope: "single" | "all" | "thisAndFollowing" = "single",
   comment?: string,
   sendUpdates?: string,
 ): Promise<void> {
-  const client = await getClient(accountEmail);
-  if (!client) {
-    throw new Error(`Google Calendar account not connected: ${accountEmail}`);
-  }
+  const client = await getClientForAccount(account);
 
   if (scope === "single") {
     await rsvpSingleEvent(
       client.accessToken,
       googleEventId,
       responseStatus,
-      accountEmail,
+      account.accountEmail,
       comment,
       sendUpdates,
     );
@@ -1481,7 +1509,7 @@ export async function rsvpEvent(
       client.accessToken,
       recurringEventId,
       responseStatus,
-      accountEmail,
+      account.accountEmail,
       comment,
       sendUpdates,
     );
@@ -1516,7 +1544,7 @@ export async function rsvpEvent(
         client.accessToken,
         e.id,
         responseStatus,
-        accountEmail,
+        account.accountEmail,
         comment,
         sendUpdates,
       ),

package/corpus/templates/calendar/server/plugins/db.ts

@@ -206,6 +206,11 @@ CREATE INDEX IF NOT EXISTS idx_bookings_slug_start ON bookings (slug, "start");`
       version: 20,
       sql: `ALTER TABLE booking_links ADD COLUMN IF NOT EXISTS hosts TEXT`,
     },
+    {
+      version: 21,
+      name: "bookings-calendar-account-id",
+      sql: `ALTER TABLE bookings ADD COLUMN IF NOT EXISTS calendar_account_id TEXT`,
+    },
   ],
   { table: "calendar_migrations" },
 );

package/corpus/templates/chat/.agents/skills/capture-learnings/SKILL.md

@@ -11,11 +11,14 @@ metadata:
 
 # Capture Learnings
 
-This is background knowledge, not a slash command. **Your memory index is loaded at the start of every conversation.** Use `save-memory` proactively when you learn something worth remembering.
+This is background knowledge, not a slash command. **Organization learnings and your personal memory index are loaded at the start of every conversation, including Slack/integration turns.** Capture durable context proactively when you learn something worth remembering.
 
 ## How to Read & Write Memories
 
-Memories are stored as **resources** in the SQL database (personal scope), not as files on disk.
+Memories are stored as **resources** in the SQL database, not as files on disk.
+
+- **Team/organization knowledge:** shared `LEARNINGS.md`. Read it first, merge the new fact, then write the full updated file with the `resources` tool using `scope: "shared"`. Shared scope resolves to the active organization; it must never leak to another organization in the same deployment.
+- **Personal knowledge:** `memory/MEMORY.md` plus `memory/<name>.md`, written with `save-memory`.
 
 - **Save a memory:** `save-memory --name <name> --type <type> --description "..." --content "..."`
 - **Read a memory:** `resource-read --path memory/<name>.md`
@@ -33,6 +36,14 @@ Memories are stored as **resources** in the SQL database (personal scope), not a
 
 ## When to Capture
 
+### Team and organization knowledge (`LEARNINGS.md`, shared scope)
+- Canonical destinations and workflows (for example, which Content database receives a type of Slack request)
+- Required intake fields, ownership, prioritization conventions, metric definitions, and approved terminology
+- Durable external references that the whole team needs, including the canonical page/database URL
+- Corrections or decisions that should affect every organization member's future Slack and app conversations
+
+Store the fact and a concise provenance link when available. Do not paste full private conversations, customer data, credentials, or secrets into learnings. Put stable always-on policy in shared `AGENTS.md`; put learned facts and evolving conventions in shared `LEARNINGS.md`.
+
 ### User Preferences & Memory (`user`)
 - **Tone and style** — "I prefer casual tone", "don't use emojis", "keep replies short"
 - **Personal context** — contacts, relationships, habits ("my wife's email is...", "I'm in PST timezone")
@@ -58,19 +69,21 @@ Memories are stored as **resources** in the SQL database (personal scope), not a
 - Things obvious from reading the code
 - Standard language/framework behavior
 - Temporary debugging notes
-- Anything already in AGENTS.md or skills
+- Anything already in AGENTS.md, shared LEARNINGS.md, or skills
 - Ephemeral task details (use tasks/plans instead)
 
 ## Key Rules
 
-1. **Save proactively — don't ask permission.** When you learn something, save it immediately.
-2. **One memory per topic** — e.g. `coding-style`, `project-alpha`, not one giant dump
-3. **Read before updating** — if a memory exists, read it first and merge, don't overwrite
-4. **Keep descriptions concise** — the index is loaded every conversation
-5. **Memories are SQL-backed** — safe for personal info, persist across sessions, not in git
+1. **Save proactively — don't ask permission.** When you learn something durable, save it immediately at the correct scope.
+2. **Choose scope by audience.** Organization workflow or reference → shared `LEARNINGS.md`; one person's preference/context → personal memory.
+3. **One memory per topic** — e.g. `coding-style`, `project-alpha`, not one giant dump
+4. **Read before updating** — if a memory exists, read it first and merge, don't overwrite
+5. **Keep descriptions concise** — the index is loaded every conversation
+6. **Memories are SQL-backed** — they persist across sessions and are not in git; still minimize sensitive content
 
 ## Graduation
 
 When a memory is referenced repeatedly, it may belong in AGENTS.md or a skill:
-- Saving a memory is lightweight (auto-apply, personal scope)
+- Saving a personal memory is lightweight (auto-apply, personal scope)
+- Shared LEARNINGS.md is the lightweight organization knowledge layer
 - Updating AGENTS.md or a skill is heavier (affects all users/agents)

package/corpus/templates/chat/changelog/2026-07-10-chat-now-makes-ai-connection-setup-clear-without-shifting-th.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-10
+---
+
+Chat now makes AI connection setup clear without shifting the composer.

package/corpus/templates/clips/.agents/skills/ai-video-tools/SKILL.md

@@ -28,9 +28,9 @@ The agent is already the user's primary interface — it has full project contex
 | Feature                   | Trigger                                                                               | What the action does                                                                                  |
 | ------------------------- | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
 | Include full video        | User toggles "Include full video" in the AI tools menu                                | `update-clips-ai-prefs --includeFullVideoInAi=true\|false` → stored in `clips-user-prefs`; default off |
-| Default title             | Native transcript is saved and the recording still has the default title              | `regenerate-title --recordingId=<id>` → writes `clips-ai-request-:id`; the UI bridge sends it to the agent chat. If Include full video is on, skips the transcript-only Gemini fast path and always delegates so the agent watches the recording |
+| Default title             | Native/cloud transcript becomes ready and the recording still has an automatic title   | `regenerate-title --recordingId=<id> --includeSummary=true` tries the transcript-only Gemini fast path, keeps any local heuristic title replaceable, and queues a `generate-metadata` agent refinement that writes a specific title plus description. If Include full video is on, it always delegates so the agent watches the recording |
 | Manual title suggestion   | User asks the agent "rename this"                                                     | Agent reads transcript and calls `update-recording --id=<id> --title=...`                             |
-| Summary / description     | Upload completes, or user clicks "Summarize" / "Regenerate description"               | `regenerate-summary` / `generate-ai-metadata --id=<id> --kind=summary` → agent writes `update-recording --description=...`. With Include full video, agent must watch the clip, not transcript alone |
+| Summary / description     | Transcript becomes ready, or user clicks "Summarize" / "Regenerate description"       | The automatic metadata handoff or `regenerate-summary` asks the agent to write `update-recording --description=...`. Existing user-authored descriptions are preserved. With Include full video, the agent must watch the clip, not transcript alone |
 | Chapters                  | User clicks "Add chapters" or transcript > 3 minutes                                  | `generate-chapters --id=<id>` / `regenerate-chapters` → agent writes `chapters_json` (same full-video preference) |
 | Tags                      | On upload complete                                                                    | `generate-ai-metadata --id=<id> --kind=tags` → agent inserts `recording_tags` rows                    |
 | Filler-word removal       | User clicks "Remove ums and uhs"                                                      | `generate-filler-removal --id=<id>` → agent writes proposed cuts into `editor-draft` for user review  |
@@ -57,7 +57,9 @@ on-screen text.
   `get-recording-player-data` / `create-recording-agent-link` and follow
   recommended frames / the frame API across the timeline — not transcript only.
 - Default title generation also honors this: `regenerate-title` skips the
-  transcript-only Gemini cleanup path and always queues the agent.
+  transcript-only Gemini cleanup path and always queues the agent. Automatic
+  post-transcription work uses one `generate-metadata` request so title and
+  description are not competing application-state entries.
 
 Do not invent a parallel "video LLM" path in the UI. Keep the preference on the
 shared user-prefs object and keep delegation through the agent chat.
@@ -133,6 +135,13 @@ Clips never routes recording/meeting audio to OpenAI for transcription. (Groq's
 
 If no native transcript exists and no cloud fallback is available (no Builder connection and no Groq key), the action writes `status="failed"` so the UI can show a friendly prompt.
 
+When a transcript becomes ready, `request-transcript` must await native cleanup
+and the metadata handoff before its durable post-finalize worker returns.
+Do not leave title/summary work as an unawaited promise in that worker:
+serverless runtimes may freeze it immediately. A local heuristic title uses
+`titleSource: "context"` so it remains a temporary UI fallback until the
+`generate-metadata` agent request replaces it with a transcript-backed title.
+
 If Builder transcription fails because credits are exhausted, explain that
 Builder.io credits/upgrade or a Groq key are the supported speech-to-text
 fallbacks. Generic OpenAI or Anthropic chat keys power chat, but they do not

package/corpus/templates/clips/.agents/skills/capture-learnings/SKILL.md

@@ -11,11 +11,14 @@ metadata:
 
 # Capture Learnings
 
-This is background knowledge, not a slash command. **Your memory index is loaded at the start of every conversation.** Use `save-memory` proactively when you learn something worth remembering.
+This is background knowledge, not a slash command. **Organization learnings and your personal memory index are loaded at the start of every conversation, including Slack/integration turns.** Capture durable context proactively when you learn something worth remembering.
 
 ## How to Read & Write Memories
 
-Memories are stored as **resources** in the SQL database (personal scope), not as files on disk.
+Memories are stored as **resources** in the SQL database, not as files on disk.
+
+- **Team/organization knowledge:** shared `LEARNINGS.md`. Read it first, merge the new fact, then write the full updated file with the `resources` tool using `scope: "shared"`. Shared scope resolves to the active organization; it must never leak to another organization in the same deployment.
+- **Personal knowledge:** `memory/MEMORY.md` plus `memory/<name>.md`, written with `save-memory`.
 
 - **Save a memory:** `save-memory --name <name> --type <type> --description "..." --content "..."`
 - **Read a memory:** `resource-read --path memory/<name>.md`
@@ -33,6 +36,14 @@ Memories are stored as **resources** in the SQL database (personal scope), not a
 
 ## When to Capture
 
+### Team and organization knowledge (`LEARNINGS.md`, shared scope)
+- Canonical destinations and workflows (for example, which Content database receives a type of Slack request)
+- Required intake fields, ownership, prioritization conventions, metric definitions, and approved terminology
+- Durable external references that the whole team needs, including the canonical page/database URL
+- Corrections or decisions that should affect every organization member's future Slack and app conversations
+
+Store the fact and a concise provenance link when available. Do not paste full private conversations, customer data, credentials, or secrets into learnings. Put stable always-on policy in shared `AGENTS.md`; put learned facts and evolving conventions in shared `LEARNINGS.md`.
+
 ### User Preferences & Memory (`user`)
 - **Tone and style** — "I prefer casual tone", "don't use emojis", "keep replies short"
 - **Personal context** — contacts, relationships, habits ("my wife's email is...", "I'm in PST timezone")
@@ -58,19 +69,21 @@ Memories are stored as **resources** in the SQL database (personal scope), not a
 - Things obvious from reading the code
 - Standard language/framework behavior
 - Temporary debugging notes
-- Anything already in AGENTS.md or skills
+- Anything already in AGENTS.md, shared LEARNINGS.md, or skills
 - Ephemeral task details (use tasks/plans instead)
 
 ## Key Rules
 
-1. **Save proactively — don't ask permission.** When you learn something, save it immediately.
-2. **One memory per topic** — e.g. `coding-style`, `project-alpha`, not one giant dump
-3. **Read before updating** — if a memory exists, read it first and merge, don't overwrite
-4. **Keep descriptions concise** — the index is loaded every conversation
-5. **Memories are SQL-backed** — safe for personal info, persist across sessions, not in git
+1. **Save proactively — don't ask permission.** When you learn something durable, save it immediately at the correct scope.
+2. **Choose scope by audience.** Organization workflow or reference → shared `LEARNINGS.md`; one person's preference/context → personal memory.
+3. **One memory per topic** — e.g. `coding-style`, `project-alpha`, not one giant dump
+4. **Read before updating** — if a memory exists, read it first and merge, don't overwrite
+5. **Keep descriptions concise** — the index is loaded every conversation
+6. **Memories are SQL-backed** — they persist across sessions and are not in git; still minimize sensitive content
 
 ## Graduation
 
 When a memory is referenced repeatedly, it may belong in AGENTS.md or a skill:
-- Saving a memory is lightweight (auto-apply, personal scope)
+- Saving a personal memory is lightweight (auto-apply, personal scope)
+- Shared LEARNINGS.md is the lightweight organization knowledge layer
 - Updating AGENTS.md or a skill is heavier (affects all users/agents)

package/corpus/templates/clips/.agents/skills/meetings/SKILL.md

@@ -58,7 +58,7 @@ Both fields are set by `start-meeting-recording`. Agents that operate on a recor
 
 ## Calendar reminders
 
-Calendar events fire a desktop notification **1 minute before** the meeting start and keep it visible until **5 minutes after** start unless dismissed (consumer: the desktop tray in `src-tauri/`). The tray polls `list-meetings`, which reads Google Calendar live, so upcoming reminders do not depend on a manual sync or pre-created `meetings` rows. Agents do not need to schedule reminders manually.
+Calendar events fire a desktop notification **1 minute before** the meeting start and keep it visible until **5 minutes after** start unless dismissed (consumer: the desktop tray in `src-tauri/`). The tray polls `list-meetings`, which reads Google Calendar live, so upcoming reminders do not depend on a manual sync or pre-created `meetings` rows. Desktop Zoom joins use Zoom's native `zoommtg://` link so the Zoom app opens directly without an intermediate browser tab; unsupported Zoom link shapes and other providers retain their HTTPS join URL. Agents do not need to schedule reminders manually.
 
 ## Adhoc Zoom / Teams detection (desktop)
 

package/corpus/templates/clips/.agents/skills/recording/SKILL.md

@@ -32,7 +32,11 @@ Some recordings are linked to a meeting — when `meeting_id` is non-null on the
 5. **Upload each chunk.** `ondataavailable` POSTs the chunk bytes to `/api/uploads/chunk` with headers `X-Recording-Id` and `X-Chunk-Index`. Don't retry inline — buffer failed chunks in `IndexedDB` and let a background worker re-send.
 6. **Live transcription.** Alongside the MediaRecorder, `useLiveTranscription` runs the Web Speech API to accumulate transcript text in real time. On stop, the client calls `save-browser-transcript` to persist the result immediately — no API key needed. Desktop recordings use local Whisper/macOS speech first when available, and fall back to Web Speech in the webview on non-mac before relying on upload transcription.
 7. **Finalize.** On stop, send the final chunk to `/api/uploads/:id/chunk?isFinal=1`. The route calls `finalize-recording`, which stitches chunks, makes the media seekable (see below), uploads the finished media when storage is configured, transitions `status` to `ready`, then kicks off `request-transcript` for higher-quality output (see `ai-video-tools`).
-8. **Navigate.** Once the row is `ready` the UI navigates to `/r/:id`.
+8. **Navigate immediately.** Desktop recorders open `/r/:id` as soon as Stop
+   starts finalization. The recording row already exists, so the page can show
+   the title, share link, and upload progress while it polls from `uploading` or
+   `processing` to `ready`. Do not wait for the upload/finalize response before
+   opening the page.
 
 ## Seekable playback (don't ship raw MediaRecorder output)
 
@@ -63,6 +67,18 @@ idempotent (already-seekable clips are skipped unless `--force`) and only touche
 provider-hosted clips owned by the caller. This is the right tool when a user
 reports a specific slow/buffering clip.
 
+Seekability remuxing cannot repair a recording whose audio continues while the
+video track has a large timestamp gap (common when a mobile browser suspends the
+camera after the user switches apps). For a clip that freezes or appears to stop
+before its declared duration, call `reprocess-recording` with
+`--normalizeTimeline=true`. That explicit mode uses the same owner-scoped fetch
+and upload flow but fully transcodes to a constant-30-fps faststart MP4 (H.264 +
+AAC). It preserves audio and duplicates the last decoded video frame through
+missing-frame gaps. The action uploads to a new media object and atomically
+repoints the row only after verified output is stored; any transcode, audio
+verification, upload, or concurrent-update failure leaves the original URL and
+format untouched.
+
 ## Loom import
 
 Use `import-loom-recording` for Loom share or embed URLs. The action validates

package/corpus/templates/clips/.agents/skills/video-sharing/SKILL.md

@@ -77,6 +77,14 @@ import { ShareDialog } from "@agent-native/core/client";
 
 The password and expiry fields call `update-recording --password=...` / `--expiresAt=...`. Keep Clips' share-dialog wrapper minimal — any new generic sharing feature belongs in the framework component, not here.
 
+## Shared with me
+
+Use `list-recordings --view=shared` to list recordings the current user can
+access but does not own. The filter composes with `accessFilter`, so it includes
+direct user/org grants and organization-visible recordings while excluding
+public-link-only clips. The UI exposes the same collection at `/shared`; use
+`navigate --view=shared` to open it.
+
 ## Access resolution
 
 The player and `/api/video/:id` route check access in this exact order:

package/corpus/templates/clips/AGENTS.md

@@ -32,8 +32,10 @@ Detailed media, meeting, dictation, editing, and sharing rules live in
   Clips-hosted recording, and imports Loom's public transcript when the share
   page exposes one. If Loom does not expose a downloadable MP4, ask the user to
   download the original from Loom and use "Upload video".
-- Native transcript first. Cleanup and title generation can run in the
-  background; do not hide a usable native transcript behind a failed cleanup.
+- Native transcript first. Cleanup and transcript-backed title/summary
+  generation run in the durable post-finalize path; do not hide a usable native
+  transcript behind failed metadata work, and keep heuristic titles replaceable
+  until the agent refinement lands.
 - Use `request-transcript --recordingId=<id> --force=true` to retry a failed
   transcript. Pass `--regenerate=true` to replace an existing ready transcript
   from the stored recording media; if regeneration fails, keep the prior ready
@@ -63,6 +65,9 @@ Detailed media, meeting, dictation, editing, and sharing rules live in
   sharing/status boundary.
 - Use framework sharing actions for recordings. Password and expiry are extra
   controls on top of visibility/share grants.
+- Use `list-recordings --view=shared` for the current user's "Shared with me"
+  collection. It returns recordings admitted by sharing access that are owned
+  by someone else; public-link-only clips remain out of this list.
 - Public recordings expose AI-readable URLs for external agents:
   `/api/agent-context.json?id=<recordingId>` for metadata, transcript, and frame
   API discovery; `/api/agent-transcript.json?id=<recordingId>` for transcript
@@ -132,9 +137,11 @@ Detailed media, meeting, dictation, editing, and sharing rules live in
 
 ## Application State
 
-- `navigation` exposes library, recording, share, meeting, dictation, settings,
-  and transcript context. `selection` exposes selected library recording ids
-  when the user is in selection mode.
+- `navigation` exposes library, shared-with-me, recording, share, meeting,
+  dictation, settings, and transcript context. `selection` exposes selected
+  library recording ids when the user is in selection mode.
+- `navigate --view=shared` opens the shared-with-me collection, and
+  `view-screen` returns its currently visible recordings.
 - `recording-setup.import` exposes Loom import UI state while the `/record`
   surface is open, without storing the pasted URL in ambient screen context.
 - `navigate` moves the UI to recording/library/meeting/share surfaces.