@agent-native/core 0.122.3 → 0.123.0

package/corpus/core/docs/content/template-clips.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Clips"
-description: "Async screen recording, calendar-synced meeting notes, bug reports, and push-to-talk voice dictation — paste Clips links into agents and they can read transcripts, visuals, and summaries."
-search: "Clips browser logs developer logs console logs network logs fetch XHR Chrome extension diagnostics recorder desktop app bug report widget embed"
+description: "Async screen recording, calendar-synced meeting notes, and push-to-talk voice dictation, with the agent as a first-class editor across every clip you capture."
+search: "Clips screen recording meeting notes dictation Loom import video sharing transcript library"
 ---
 
 # Clips
@@ -17,7 +17,7 @@ A capture-everything app: screen recordings, meeting notes from your calendar, a
   />
 </WireframeBlock>
 
-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.
+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 clip's share link into an agent and it can "hear" the transcript as text and "see" timestamped screen frames as images, no raw video needed. See [Sharing, Teams, and Agent-Readable Clips](/docs/template-clips-sharing-and-teams) for how that works.
 
 <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."}>
 
@@ -74,220 +74,31 @@ Think along the lines of Loom + Granola + Wispr Flow rolled into one app: async
 
 </Diagram>
 
-## What you can do with it
+## Recording, importing, and meetings
 
 - **Record your screen** with a built-in recorder, webcam overlay, audio capture, and pause/trim.
-- **Import public Loom videos.** On the web, select **Record → Import Loom**,
-  then paste a Loom share or embed URL. Clips saves a copy in your library and
-  imports the public transcript when one is available.
+- **Import public Loom videos.** On the web, select **Record → Import Loom**, then paste a Loom share or embed URL. Clips saves a copy in your library and imports the public transcript when one is available.
 - **Capture meetings from your calendar.** Connect Google Calendar, see upcoming meetings in the sidebar, and hit record on any one. You get a live transcript plus AI summary, bullet notes, and action items the moment it ends.
-- **Push-to-talk dictation.** Hold Fn on your machine, speak, and the cleaned-up text drops into whatever app you're using. Every dictation is kept in a searchable history with originals and AI-cleaned versions side by side.
-- **Get an auto-generated title, summary, and chapter markers** for every recording — the agent fills them in and keeps them current.
+- **Get an auto-generated title, summary, and chapter markers** for every recording — the agent fills them in and keeps them current. See [AI Pipeline, Editing, and Insights](/docs/template-clips-ai-and-editing) for how that pipeline works and how to edit the result.
 - **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 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
-  product bugs and browser-only repros.
-- **Paste Clips links into agents** so they can discover the agent-readable context: metadata, transcript segments, recommended frames, and timestamped frame images without receiving the raw video file. Private clips use a temporary scoped link instead of changing visibility.
 - **Smart library views.** Group by project, filter by speaker, auto-tag based on content.
-- **Edit the transcript through chat.** "Fix the mis-transcribed word at 1:42." "Pull three quotes for a blog post." The agent edits the transcript and the UI updates live.
-
-## Browser logs and developer diagnostics
-
-Use the Clips Chrome extension when you need a recording plus browser logs from
-the tab you are debugging. The extension starts an active-tab recording and can
-save redacted console logs, JavaScript exceptions, and fetch/XHR network
-metadata such as method, redacted URL, status, duration, and failure text. It
-does not save request bodies, response bodies, or headers.
-
-The regular browser recorder page can save diagnostics from the recorder page
-itself. The Chrome extension is the path for active-tab developer logs and
-browser-only repros. In the Clips UI, use the Chrome option for browser logs and
-the desktop app for the most seamless everyday capture path.
-
-The Agent-Native Clips Chrome extension listing is
-`https://chromewebstore.google.com/detail/baoipacpchggcdigagnajakiidcgcffn`.
-If you host your own Clips server, keep the Chrome extension option hidden until
-your Web Store listing is live. Set `VITE_CLIPS_CHROME_EXTENSION_ENABLED=1`
-after approval to show the extension beside desktop-app download prompts. Set
-`VITE_CLIPS_CHROME_EXTENSION_URL` only if you need to override the default
-listing URL.
-
-## Embedded bug reports
-
-Clips can be embedded into an existing product as a lightweight bug-report
-launcher. The embedded page collects issue metadata, opens the real recorder in
-a top-level browser window, and then posts a completion message back to the host
-product when the recording is saved.
-
-Use `/bug-report` as the iframe URL. The page accepts either plain query
-parameters or the `bugReport*` prefixed parameters that the recorder stores:
-
-```html
-<iframe
-  src="https://clips.example.com/bug-report?projectId=web-app&sourceUrl=https%3A%2F%2Fapp.example.com%2Fsettings&pageTitle=Settings&appVersion=2026.06.26&environment=production&returnUrl=https%3A%2F%2Fapp.example.com%2Fsettings"
-  allow="display-capture; camera; microphone"
-  style="width: 420px; height: 560px; border: 0"
-></iframe>
-```
-
-Supported metadata fields are `projectId`, `title`, `description`, `severity`
-(`low`, `normal`, `high`, `urgent`), `sourceUrl`, `pageTitle`, `appVersion`,
-`environment`, `reporterEmail`, `reporterName`, `reporterId`, `metadata` (JSON
-object), and `returnUrl`. The recorder redirects to `/bug-report/done` after
-upload and sends this browser message to `window.opener` and the parent frame:
-
-```js
-window.addEventListener("message", (event) => {
-  if (event.data?.type !== "agent-native.clips.bug-report.submitted") return;
-  console.log(event.data.recordingId, event.data.recordingUrl);
-});
-```
-
-Bug-report recordings default to workspace visibility instead of public
-visibility. The saved `recording_bug_reports` sidecar includes the redacted host
-metadata, while the recording itself remains the canonical media/transcript
-resource. URLs have credentials, fragments, and query values removed before
-storage, and the browser-diagnostics pipeline still omits request/response
-bodies, headers, and cookies.
-
-This first version assumes the reporter can sign in to the Clips workspace that
-owns the recording. A fully anonymous customer intake should add a signed intake
-token that can create, upload, and finalize a recording without granting broad
-recording access; do not expose the existing owner-scoped upload endpoints
-directly to anonymous users.
-
-## Agent-readable clips
 
-Paste a public Clips share link into an agent, or use **Share → Copy** in the
-**Share with agents** row to mint a temporary private agent link. Private,
-organization, and passworded clips do not need to become public: the copied URL
-carries a recording-scoped `agent_access` token that expires after two hours.
+Recording from your phone, from a browser tab you're debugging, or picking up the last few minutes you forgot to record? See [Capturing Everywhere](/docs/template-clips-capture-everywhere).
 
-The share page advertises a compact agent context URL, and that context points
-to the transcript and frame APIs, so models that only accept text or still
-images can still understand what happened in the recording.
+## Dictation
 
-Any agent that can fetch an image URL into its vision — ChatGPT, Claude Code,
-Cursor, Codex, and MCP-connected agents — reads the transcript and sees the
-frames. A few text-only web chats read the transcript but won't pull frame images
-in on their own; there, upload a key frame or open the clip in an image-capable
-agent.
-
-| Endpoint                                          | What agents get                                                                                                |
-| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
-| `/api/agent-context.json?id=<recordingId>`        | Clip metadata, transcript status, chapters, CTAs, recommended frames, and links to the transcript/frame APIs   |
-| `/api/agent-transcript.json?id=<recordingId>`     | Timestamped transcript segments with `startMs`, `endMs`, readable timestamps, text, and optional source labels |
-| `/api/agent-frame.jpg?id=<recordingId>&atMs=<ms>` | A JPEG frame extracted from the video at an original-video timestamp                                           |
-
-The endpoints follow the same public/password/expiry rules as the share page,
-or accept the scoped `agent_access` token from a temporary agent link.
-Password-protected clips require the password once; successful responses return
-short-lived tokenized links so downstream agents do not need the plaintext
-password.
-
-Implementation note: use the shared core agent-access helpers
-(`createScopedAgentAccessGrant`, `verifyScopedAgentAccessToken`,
-`buildAgentAccessUrl`, and `buildAgentAccessApiUrl`) for the SSR/bot-visible
-URL contract. Keep Clips-specific visibility checks, transcript/frame payloads,
-and player UI local. New links use `agent_access`; routes should continue
-accepting the legacy `t` query where existing agent API URLs may already use it.
-
-When `transcript.status` is `pending`, agents should wait 15-30 seconds and
-retry the context or transcript URL a few times before falling back to frames or
-reporting that no transcript is available. Long recordings can take several
-minutes to finish. Failed transcripts include `failureReason`; if Builder
-transcription credits are exhausted, the agent should explain that the user
-needs Builder.io credits/upgrade or a Groq key for backup speech-to-text.
-Pending transcript responses also include `retryAfterSeconds` for agents that
-want a structured polling hint.
-
-Slack previews use the same sharing boundary. The `/api/slack/unfurl` webhook
-only returns a playable Slack `video` block for ready, public clips without a
-password, expiry hit, archive marker, or trash marker. Other clips still get the
-normal share-page title/thumbnail metadata and require opening Clips.
-
-<Endpoint id="doc-block-6q76u0" title="Agent context entry point" method="GET" path="/api/agent-context.json" summary="Compact, agent-readable description of a shared clip" auth="Same public / password / expiry rules as the share page, or a scoped agent_access token" params={[
-  {
-    "name": "id",
-    "in": "query",
-    "type": "string",
-    "required": true,
-    "description": "Recording id"
-  },
-  {
-    "name": "agent_access",
-    "in": "query",
-    "type": "string",
-    "required": false,
-    "description": "Temporary token from Copy for agent links"
-  }
-]} responses={[
-  {
-    "status": "200",
-    "description": "Clip metadata, transcript status/failureReason/retryAfterSeconds, agent instructions, and transcript/frame API links"
-  }
-]}>
-
-Returns clip metadata, transcript status, chapters, CTAs, recommended frames, and links to the transcript and frame APIs. Advertised by public share pages and temporary private agent links so a text- or image-only agent can understand a recording without ingesting raw video.
-
-</Endpoint>
-
-<Endpoint id="doc-block-8ryota" title="Timestamped transcript" method="GET" path="/api/agent-transcript.json" summary="Timestamped transcript segments for a shared clip" params={[
-  {
-    "name": "id",
-    "in": "query",
-    "type": "string",
-    "required": true,
-    "description": "Recording id"
-  }
-]} responses={[
-  {
-    "status": "200",
-    "description": "Transcript status, failureReason, retryAfterSeconds, full text, and segments with startMs, endMs, readable timestamps, text, and optional source labels"
-  }
-]}>
-
-</Endpoint>
-
-<Endpoint id="doc-block-jlizey" title="Frame at a timestamp" method="GET" path="/api/agent-frame.jpg" summary="A JPEG frame extracted from the video at an original-video timestamp" params={[
-  {
-    "name": "id",
-    "in": "query",
-    "type": "string",
-    "required": true,
-    "description": "Recording id"
-  },
-  {
-    "name": "atMs",
-    "in": "query",
-    "type": "integer",
-    "required": true,
-    "description": "Original-video timestamp in milliseconds"
-  }
-]} responses={[
-  {
-    "status": "200",
-    "description": "image/jpeg frame"
-  }
-]}>
-
-</Endpoint>
+- **Push-to-talk dictation.** Hold Fn on your machine, speak, and the cleaned-up text drops into whatever app you're using. Every dictation is kept in a searchable history with originals and AI-cleaned versions side by side.
+- **Dictate from your phone**, too — see [Capturing Everywhere](/docs/template-clips-capture-everywhere) for the mobile companion app.
+- **Edit through chat.** "Fix the mis-transcribed word at 1:42." "Turn that ramble into bullet points." The agent edits the transcript and the UI updates live.
 
 ## Getting started
 
 Live demo: [clips.agent-native.com](https://clips.agent-native.com).
 
-1. **Open Library.** Browse screen recordings, meeting recordings, dictations,
-   folders, and spaces from one place.
-2. **Record or import.** Capture a screen recording, start from a calendar
-   meeting, or use push-to-talk dictation.
-3. **Let the agent clean it up.** Generate a title, summary, chapters, action
-   items, or cleaned-up transcript text.
-4. **Search and reuse.** Ask for the clip, quote, action item, or decision you
-   need, then share the result with the right visibility.
+1. **Open Library.** Browse screen recordings, meeting recordings, dictations, folders, and spaces from one place.
+2. **Record or import.** Capture a screen recording, start from a calendar meeting, or use push-to-talk dictation.
+3. **Let the agent clean it up.** Generate a title, summary, chapters, action items, or cleaned-up transcript text.
+4. **Search and reuse.** Ask for the clip, quote, action item, or decision you need, then share the result with the right visibility.
 
 ### Useful prompts
 
@@ -297,312 +108,12 @@ Live demo: [clips.agent-native.com](https://clips.agent-native.com).
 - "Create action items from the last sales call."
 - "Clean up this dictation and turn it into a Linear ticket."
 
-## For developers
-
-The rest of this doc is for anyone forking the Clips template or extending it.
-
-### Quick start
-
-```bash
-npx @agent-native/core@latest create my-clips --standalone --template clips
-cd my-clips
-pnpm install
-pnpm dev
-```
-
-Clips is a larger template with a native recorder (it ships a desktop companion for local capture). Three setup steps are needed before recordings can upload:
-
-1. **Video storage (required).** Connect a storage backend through the onboarding wizard or Clips Settings. The easiest path is Builder.io (free during beta, one-click). For self-hosted storage, save `S3_ENDPOINT`, `S3_BUCKET`, `S3_ACCESS_KEY_ID`, `S3_SECRET_ACCESS_KEY`, and optionally `S3_REGION` and `S3_PUBLIC_BASE_URL` in the app; the values are stored as scoped DB secrets. Cloudflare R2 and DigitalOcean Spaces use the same key names with the `R2_*` prefix.
-2. **Google Calendar (optional).** To sync upcoming meetings, connect a Google Calendar account from Settings. The OAuth callback URL in dev is `http://localhost:8094/_agent-native/google/callback`. Set up a Google OAuth client in [Google Cloud Console](https://console.cloud.google.com/) with the Gmail and Google Calendar APIs enabled.
-3. **Screen-capture permissions.** On macOS, grant Screen Recording permission to the browser (or the desktop companion app) in System Settings → Privacy & Security → Screen Recording. Browser recordings can save redacted console and fetch/XHR diagnostics from the recorder page. Once the Chrome extension listing is available, enable `VITE_CLIPS_CHROME_EXTENSION_ENABLED=1` so users can choose the extension for active-tab browser logs or the desktop app for the smoothest native capture path.
-4. **Slack previews (optional).** Create a Slack app with `links:read`, `links:write`, and `links.embed:write`; subscribe to `link_shared`; add your Clips share domain under **App Unfurl Domains**; set the Request URL to `https://your-clips.example.com/api/slack/unfurl`; and add the OAuth redirect URL `https://your-clips.example.com/api/slack/oauth/callback`. Configure `SLACK_CLIENT_ID`, `SLACK_CLIENT_SECRET`, and `SLACK_SIGNING_SECRET`, then connect workspaces from Clips Settings.
-
-### Host your own Clips server
-
-The hosted Clips app at [clips.agent-native.com](https://clips.agent-native.com)
-is just a deployed copy of the Clips template. To run your own server, scaffold
-the template, deploy it like any other agent-native app, then point the desktop
-tray app at your deployment.
-
-1. **Create the app.**
-
-   ```bash
-   npx @agent-native/core@latest create my-clips --standalone --template clips
-   cd my-clips
-   pnpm install
-   ```
-
-2. **Configure production state.** Set a persistent `DATABASE_URL`, the normal
-   production auth/secrets variables from [Deployment](/docs/deployment), and a
-   video storage provider. Builder.io Connect is the easiest storage path; for
-   self-hosted storage, save `S3_*` or `R2_*` keys from Clips Settings for an
-   S3-compatible bucket.
-
-3. **Deploy the web app.** For a plain Node deploy:
-
-   ```bash
-   pnpm build
-   node .output/server/index.mjs
-   ```
-
-   You can also use any Nitro target from [Deployment](/docs/deployment), such
-   as Netlify, Vercel, Cloudflare Pages, AWS Lambda, or Deno Deploy. Make sure
-   `BETTER_AUTH_URL` is the public Clips origin, for example
-   `https://clips.example.com`.
-
-4. **Connect the desktop tray app.** Open Clips Desktop settings and set
-   **Clips server URL** to the public base URL of your deployment, for example
-   `https://clips.example.com`. If the app is mounted under a workspace path,
-   include that path, such as `https://example.com/clips`. Click **Connect**,
-   then sign in with an account on that Clips server.
-
-5. **Enable the Chrome extension after publishing.** Keep
-   `VITE_CLIPS_CHROME_EXTENSION_ENABLED` unset until the Chrome Web Store listing
-   is approved. Then set it to `1` to reveal the browser-log option beside the
-   desktop app prompts. The default listing URL is
-   `https://chromewebstore.google.com/detail/baoipacpchggcdigagnajakiidcgcffn`;
-   set `VITE_CLIPS_CHROME_EXTENSION_URL` only if your deployment uses a
-   different extension listing.
-
-6. **Connect optional integrations.** Google Calendar powers the Meetings tab,
-   `GEMINI_API_KEY` or Builder.io Connect powers transcript cleanup and titles,
-   `GROQ_API_KEY` can provide speech-to-text fallback, and the Slack OAuth
-   connection in Settings enables playable Slack unfurls.
-
-For local development, run the web app with `pnpm dev` and point the desktop
-tray app at `http://localhost:8094`.
-
-### Key features
-
-**One library, three capture types.** Screen recordings, calendar meetings, and push-to-talk dictations share one searchable library.
-
-**Transcript and AI pipeline.** Recordings get timestamped transcript segments, generated titles, summaries, and chapter markers.
-
-**Non-destructive editing.** Trim, split, filler-word removal, silence removal, and stitching stay in `edits_json` so original media remains intact.
-
-**Agent-readable share links.** Public share links and temporary private agent links expose transcript and frame APIs so agents can understand recordings without ingesting raw video.
-
-**Slack playable unfurls.** Public share links can render a Slack `video` block
-that points at the existing `/embed/:id` player. This is a workspace Slack app
-install, not a global crawler behavior: normal Open Graph/Twitter metadata is
-the fallback when the app is not installed.
-
-### Data model
-
-All data lives in SQL via Drizzle ORM. Schema: `templates/clips/server/db/schema.ts`. Recordings, meetings, dictations, calendar accounts, and vocabulary all carry the standard `ownableColumns` and have a matching framework shares table, so they slot into the per-user / per-org sharing model.
-
-<DataModel
-  id="doc-block-oitg2"
-  title="Clips core data model"
-  summary={
-    "recordings is the source of truth for media; transcripts, meetings, and dictations compose with it rather than duplicating video. (Engagement and org tables omitted for clarity — see the full table below.)"
-  }
-  entities={[
-    {
-      id: "recordings",
-      name: "recordings",
-      note: "Core resource; source of truth for media. ownableColumns",
-      fields: [
-        {
-          name: "id",
-          type: "text",
-          pk: true,
-        },
-        {
-          name: "title",
-          type: "text",
-        },
-        {
-          name: "video_url",
-          type: "text",
-          note: "plus format / size / duration / thumbnails",
-        },
-        {
-          name: "status",
-          type: "text",
-        },
-        {
-          name: "edits_json",
-          type: "text",
-          note: "Non-destructive edits",
-        },
-        {
-          name: "chapters_json",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "password",
-          type: "text",
-          nullable: true,
-          note: "Privacy: password / expiry",
-        },
-      ],
-    },
-    {
-      id: "recording_transcripts",
-      name: "recording_transcripts",
-      note: "Split out so the library and transcript views render fast",
-      fields: [
-        {
-          name: "recording_id",
-          type: "text",
-          fk: "recordings.id",
-        },
-        {
-          name: "segments_json",
-          type: "text",
-          note: "{ startMs, endMs, text }",
-        },
-        {
-          name: "full_text",
-          type: "text",
-        },
-        {
-          name: "language",
-          type: "text",
-        },
-        {
-          name: "status",
-          type: "text",
-        },
-      ],
-    },
-    {
-      id: "clips_meetings",
-      name: "clips_meetings",
-      note: "Calendar-sourced or ad-hoc; owns a recording",
-      fields: [
-        {
-          name: "id",
-          type: "text",
-          pk: true,
-        },
-        {
-          name: "recording_id",
-          type: "text",
-          fk: "recordings.id",
-          nullable: true,
-        },
-        {
-          name: "summary_md",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "bullets_json",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "action_items_json",
-          type: "text",
-          nullable: true,
-        },
-      ],
-    },
-    {
-      id: "clips_dictations",
-      name: "clips_dictations",
-      note: "Push-to-talk dictation history; ownableColumns",
-      fields: [
-        {
-          name: "id",
-          type: "text",
-          pk: true,
-        },
-        {
-          name: "full_text",
-          type: "text",
-          note: "Raw",
-        },
-        {
-          name: "cleaned_text",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "source",
-          type: "text",
-          note: "fn-hold, etc.",
-        },
-        {
-          name: "target_app",
-          type: "text",
-          nullable: true,
-        },
-      ],
-    },
-  ]}
-  relations={[
-    {
-      from: "recordings",
-      to: "recording_transcripts",
-      kind: "1-1",
-      label: "transcript",
-    },
-    {
-      from: "recordings",
-      to: "clips_meetings",
-      kind: "1-1",
-      label: "captured by",
-    },
-  ]}
-/>
-
-| Table                                           | What it holds                                                                                                                                                                 |
-| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `recordings`                                    | The core resource — title, video URL/format/size, duration, thumbnails, status, non-destructive `edits_json`, `chapters_json`, privacy (password, expiry), and player toggles |
-| `recording_transcripts`                         | Per-recording transcript: `segments_json` (`{startMs,endMs,text}`), `full_text`, language, and status                                                                         |
-| `recording_tags`                                | Free-form tags on a recording                                                                                                                                                 |
-| `recording_ctas`                                | Call-to-action buttons (label, url, color, placement) overlaid on a recording                                                                                                 |
-| `recording_comments`                            | Threaded, timestamped comments with emoji-reaction map and resolved flag                                                                                                      |
-| `recording_bug_reports`                         | Redacted host-product bug report metadata keyed by `recording_id`                                                                                                             |
-| `recording_reactions`                           | Emoji reactions pinned to a video timestamp (anonymous viewers allowed)                                                                                                       |
-| `recording_viewers` / `recording_events`        | View analytics: per-viewer watch time and completion, plus granular events (view-start, watch-progress, seek, pause, cta-click, reaction)                                     |
-| `clips_meetings`                                | Calendar-sourced or ad-hoc meetings — schedule/actual spans, platform, user notes, AI `summary_md`, `bullets_json`, `action_items_json`, and the link to its `recording_id`   |
-| `meeting_participants` / `meeting_action_items` | Attendees and extracted action items for a meeting                                                                                                                            |
-| `calendar_accounts` / `calendar_events`         | Connected calendar accounts (OAuth tokens live in `app_secrets`, only referenced here) and synced event snapshots                                                             |
-| `clips_dictations`                              | Push-to-talk dictation history — raw `full_text`, optional `cleaned_text`, source (`fn-hold`, etc.), and target app                                                           |
-| `clips_vocabulary`                              | Personal vocabulary corrections (term → preferred replacement) that bias future dictations                                                                                    |
-| `spaces` / `space_members` / `folders`          | Library organization — spaces (topic-scoped containers), their members, and nestable folders                                                                                  |
-| `organization_settings`                         | Per-org Clips sidecar: brand color, logo, default visibility                                                                                                                  |
-
-Recordings and transcripts are intentionally separate tables so the library and transcript views can each render fast. Meetings compose with recordings rather than duplicating media: a meeting owns the recording it captures, but the `recordings` row remains the source of truth for the video and per-segment transcript.
-
-Routes in the UI live under `templates/clips/app/routes/` — the authenticated app sits under `_app.*` (library, spaces, folders, meetings, dictate, insights, trash, settings), with public surfaces at `r.$recordingId`, `share.$shareId`, `embed.$shareId`, and `invite.$token`.
-
-### Key actions
-
-Every agent-callable operation is a TypeScript file in `templates/clips/actions/`, auto-mounted at `POST /_agent-native/actions/:name` and runnable from the CLI as `pnpm action <name>`. There are about 100 actions; the useful groupings:
-
-- **Recording lifecycle** — `create-recording`, `finalize-recording`, `update-recording`, `set-thumbnail`, `archive-recording` / `restore-recording` / `trash-recording` / `delete-recording-permanent`, `move-recording`, `tag-recording`.
-- **Bug reports** — `save-bug-report-context` stores redacted host-product context for recordings launched from `/bug-report`; `get-recording-player-data` returns the sidecar to editors.
-- **Transcript & AI** — `request-transcript`, `cleanup-transcript`, `regenerate-title` / `regenerate-summary` / `regenerate-chapters`, `set-chapters`, `generate-workflow`. (`cleanup-transcript` and `finalize-meeting` are server-side media-pipeline calls; most other AI features delegate to the agent chat.)
-- **Editing** — non-destructive `trim-recording`, `split-recording`, `remove-filler-words`, `remove-silences`, plus `stitch-recordings`, `undo-edit`, `clear-edits`. Edits accumulate in `edits_json`; the client concatenates/exports via ffmpeg.wasm.
-- **Meetings** — `create-meeting`, `start-meeting-recording` / `stop-meeting-recording`, `finalize-meeting`, `update-meeting`, `get-meeting`, `list-meetings`, plus calendar wiring `connect-calendar` / `disconnect-calendar` / `sync-calendars` / `list-calendar-accounts`.
-- **Dictation** — `create-dictation`, `cleanup-dictation`, `update-dictation`, `list-dictations`, and `add-vocabulary-term` / `list-vocabulary` for personal vocabulary biasing.
-- **Library organization** — `create-space` / `rename-space` / `delete-space`, `add-space-member` / `remove-space-member`, `create-folder` / `rename-folder` / `delete-folder`, `add-recording-to-space`.
-- **Sharing, comments & engagement** — framework sharing actions plus `create-cta` / `update-cta` / `delete-cta`, `add-comment` / `reply-to-comment` / `resolve-comment` / `react-to-comment` / `delete-comment`, `react-to-recording`, `list-viewers`.
-- **Organizations & members** — `create-organization`, `set-organization-branding`, `invite-member` / `accept-invite` / `decline-invite` / `get-invite`, `remove-member`, `update-member-role`, `list-organization-state`, `list-notifications`.
-- **Search, insights & export** — `search-recordings` (matches titles, descriptions, transcript text, and comments, with timestamps), `get-recording-insights`, `get-organization-insights`, `export-insights-csv`, `export-to-brain`.
-- **Context & navigation** — `view-screen` (current clip, playhead, selected transcript range) and `navigate`; `refresh-list` after mutations.
-
-### Customizing it
-
-Clips is a complete, cloneable template — fork it and ask the agent to extend it. Some examples:
-
-- "Add a filler-word removal button that strips ums and uhs from the transcript and re-stitches the video."
-- "Auto-post my standup notes to Slack #eng whenever a meeting ends." (Connect Slack first via [Messaging](/docs/messaging).)
-- "Add a hotkey that drops the last dictation into Linear as a new ticket."
-- "Group the library by project — detect the project from the first words of each transcript."
-- "Add a 'Generate blog post from this clip' button that drafts a post from the transcript and saves it as a draft."
-- "Let viewers leave timestamped reactions on a shared clip."
-
-The agent edits routes, components, the transcript pipeline, and the schema as needed. See [Templates](/docs/cloneable-saas) for the full clone, customize, deploy flow, and [Getting Started](/docs/getting-started) if this is your first agent-native template.
-
 ## What's next
 
+- [**Capturing Everywhere**](/docs/template-clips-capture-everywhere) — the desktop app, the mobile companion, Rewind quick-save, Screen Memory, and the Chrome extension.
+- [**Sharing, Teams, and Agent-Readable Clips**](/docs/template-clips-sharing-and-teams) — visibility, passwords, organizations, and pasting a clip link into an agent.
+- [**AI Pipeline, Editing, and Insights**](/docs/template-clips-ai-and-editing) — transcription, non-destructive editing, and view analytics.
+- [**Extending Clips**](/docs/template-clips-developers) — for anyone forking or extending the template.
 - [**Templates**](/docs/cloneable-saas) — the clone-and-own model
 - [**Context Awareness**](/docs/context-awareness) — how the agent knows the current clip and playhead
 - [**Agent Teams**](/docs/agent-teams) — delegate transcript cleanup to a specialist sub-agent