@agent-native/core 0.178.1-nightly-20260910175201 → 0.178.1

package/corpus/templates/clips/shared/finalize-recovery.ts

@@ -10,7 +10,7 @@ export type RecoveredReadyRecording = {
   id: string;
   recordingId: string;
   status: "ready";
-  videoUrl: string;
+  videoUrl?: string;
   durationMs?: number;
   width?: number;
   height?: number;
@@ -97,6 +97,11 @@ export function publicRecordingStatusUrl(
   recordingId: string,
 ): string {
   const url = absoluteUploadUrl(uploadUrl);
+  if (url.pathname.endsWith("/api/clip-intake")) {
+    url.searchParams.set("recordingId", recordingId);
+    url.searchParams.set("operation", "status");
+    return maybeRelativeUrl(url, uploadUrl);
+  }
   const match = url.pathname.match(/^(.*)\/api\/uploads\/[^/]+\/chunk$/);
   const basePath = match?.[1] ?? "";
   url.pathname = `${basePath}/api/public-recording`;
@@ -132,7 +137,10 @@ function optionalBoolean(value: unknown): boolean | undefined {
 export function readyRecordingFromPublicPayload(
   payload: unknown,
   fallbackRecordingId: string,
-  options: { acceptPendingVerification?: boolean } = {},
+  options: {
+    acceptPendingVerification?: boolean;
+    acceptReadyWithoutVideoUrl?: boolean;
+  } = {},
 ): ProbeResult {
   const root =
     payload && typeof payload === "object"
@@ -178,7 +186,10 @@ export function readyRecordingFromPublicPayload(
 
   const videoUrl =
     typeof recording.videoUrl === "string" ? recording.videoUrl : "";
-  if (status !== "ready" || !videoUrl) {
+  if (
+    status !== "ready" ||
+    (!videoUrl && !options.acceptReadyWithoutVideoUrl)
+  ) {
     return { ready: false, terminal: false, status };
   }
 
@@ -195,7 +206,7 @@ export function readyRecordingFromPublicPayload(
       id,
       recordingId: id,
       status: "ready",
-      videoUrl,
+      ...(videoUrl ? { videoUrl } : {}),
       durationMs: optionalNumber(recording.durationMs),
       width: optionalNumber(recording.width),
       height: optionalNumber(recording.height),
@@ -235,6 +246,7 @@ export async function waitForReadyRecordingAfterFinalizeError(args: {
   intervalMs?: number;
   fetchTimeoutMs?: number;
   acceptPendingVerification?: boolean;
+  acceptReadyWithoutVideoUrl?: boolean;
   signal?: AbortSignal;
 }): Promise<RecoveredFinalizeRecording | null> {
   const fetchImpl = args.fetchImpl ?? fetch;
@@ -250,10 +262,19 @@ export async function waitForReadyRecordingAfterFinalizeError(args: {
   const attempts = Math.max(1, Math.ceil(timeoutMs / intervalMs));
   let url: string;
   let authenticatedUrl: string | null = null;
+  let acceptReadyWithoutVideoUrl = false;
   try {
     url = publicRecordingStatusUrl(args.uploadUrl, args.recordingId);
+    const isClipIntake = new URL(
+      args.uploadUrl,
+      typeof globalThis.location?.origin === "string"
+        ? globalThis.location.origin
+        : "http://localhost",
+    ).pathname.endsWith("/api/clip-intake");
+    acceptReadyWithoutVideoUrl =
+      args.acceptReadyWithoutVideoUrl ?? isClipIntake;
     authenticatedUrl =
-      args.authToken || args.preferAuthenticated
+      !isClipIntake && (args.authToken || args.preferAuthenticated)
         ? authenticatedRecordingStatusUrl(args.uploadUrl, args.recordingId)
         : null;
   } catch {
@@ -298,6 +319,7 @@ export async function waitForReadyRecordingAfterFinalizeError(args: {
             args.recordingId,
             {
               acceptPendingVerification: args.acceptPendingVerification,
+              acceptReadyWithoutVideoUrl,
             },
           );
           if (probe.ready) return probe.result;

package/corpus/templates/clips/shared/recording-core.ts

@@ -127,12 +127,12 @@ export function chunkUploadQuery(params: ChunkUploadParams): string {
   return q.toString();
 }
 
-/** Full chunk-upload URL: `<chunkBaseUrl>?<encoded params>`. `chunkBaseUrl` is
- * the per-recording endpoint (e.g. `/api/uploads/<id>/chunk` or its absolute
- * form) with no existing query string. */
+/** Full chunk-upload URL: append the encoded chunk params to the per-recording
+ * endpoint, preserving any capability query already present on the URL. */
 export function chunkUploadUrl(
   chunkBaseUrl: string,
   params: ChunkUploadParams,
 ): string {
-  return `${chunkBaseUrl}?${chunkUploadQuery(params)}`;
+  const separator = chunkBaseUrl.includes("?") ? "&" : "?";
+  return `${chunkBaseUrl}${separator}${chunkUploadQuery(params)}`;
 }

package/corpus/templates/content/CHANGELOG.md

@@ -11,6 +11,7 @@ time from the command menu (Cmd+K → "What's new").
 
 ### Fixed
 
+- Sidebar Search opens the command picker, icon controls have accessible names, and the sidebar can be resized with the keyboard.
 - First title edits no longer hit a stale-version conflict, open databases recover after agent Trash and restore actions, and database settings preserve keyboard focus when closing or returning to Add property. Source-managed database fields stay read-only in tables, page property editors, and agent actions, while local fields remain editable. Property editors stay inside mobile Info so edits can be saved without closing the panel.
 - Remote collaborator cursors in the document editor now stay compact above the text instead of expanding into full-width color bars.
 

package/corpus/templates/design/CHANGELOG.md

@@ -9,15 +9,20 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 - Design editor version history: browse and restore saved checkpoints from the top-left menu or Cmd+K.
 
-### Removed
-
-- Removed the always-visible design system picker above the design editor chat.
-
 ### Improved
 
+- The Layers panel is denser with smaller text, icons, and row height.
 - Opening or closing the left sidebar (or toggling minimal mode) no longer shifts designs on the canvas.
 - Breakpoint add control keeps a clear gap from the screen edge and shows immediate feedback while adding.
 
+### Changed
+
+- Design canvas chrome now overlays instead of resizing the board, so opening or closing the left panel and minimal mode no longer shifts screens on the canvas.
+
+### Removed
+
+- Removed the always-visible design system picker above the design editor chat.
+
 ## 2026-09-09
 
 ### Improved

package/corpus/templates/factory/CHANGELOG.md

@@ -3,6 +3,17 @@
 All notable user-facing changes to Chat are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
+## 2026-09-09
+
+### Improved
+
+- Slack feedback jobs skip threads whose parent already has 👀 or 🤖, instead of tagging Builder again.
+
+### Fixed
+
+- Slack feedback keeps a claimed 👀/🤖 marker after polling, so those threads stay out of the review queue.
+- Slack feedback no longer moves an already-started thread to needs-manual just because the parent already has 👀 or 🤖.
+
 ## 2026-09-08
 
 ### Fixed

package/dist/collab/struct-routes.d.ts

@@ -13,8 +13,8 @@
  * Body: { json: any, fieldName?: string, type?: "map"|"array", requestSource?: string }
  */
 export declare const postCollabJson: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    error: string;
     ok?: undefined;
+    error: string;
 } | {
     error?: undefined;
     ok: boolean;

package/dist/observability/routes.d.ts

@@ -41,22 +41,22 @@ export declare function createObservabilityHandler(): import("h3").EventHandlerW
     thumbsUpRate: number;
     avgEvalScore: number;
 } | {
-    ok?: undefined;
     summary: import("./types.js").TraceSummary;
     spans: import("./types.js").TraceSpan[];
+    ok?: undefined;
     error?: undefined;
     id?: undefined;
 } | {
-    ok?: undefined;
     summary?: undefined;
     spans?: undefined;
     id: string;
+    ok?: undefined;
     error?: undefined;
 } | {
-    ok?: undefined;
     summary?: undefined;
     spans?: undefined;
     error: any;
+    ok?: undefined;
     id?: undefined;
 } | {
     summary?: undefined;

package/dist/progress/routes.d.ts

@@ -15,6 +15,6 @@ export declare function createProgressHandler(): import("h3").EventHandlerWithFe
     error: string;
     ok?: undefined;
 } | {
-    ok: boolean;
     error?: undefined;
+    ok: boolean;
 }>>;

package/dist/resources/handlers.d.ts

@@ -48,8 +48,8 @@ export declare function handleUpdateResource(event: any): Promise<import("./stor
 }>;
 /** DELETE /_agent-native/resources/:id — delete a resource */
 export declare function handleDeleteResource(event: any): Promise<{
-    ok?: undefined;
     error: string;
+    ok?: undefined;
 } | {
     error?: undefined;
     ok: boolean;

package/dist/secrets/routes.d.ts

@@ -53,16 +53,16 @@ export declare function createListSecretsHandler(): import("h3").EventHandlerWit
 /** POST /_agent-native/secrets/:key — write a secret. */
 export declare function createWriteSecretHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
     error: string;
-    ok?: undefined;
     status?: undefined;
+    ok?: undefined;
 } | {
     error?: undefined;
     ok: boolean;
     status: string;
 } | {
-    ok?: undefined;
     error: string;
     removed?: undefined;
+    ok?: undefined;
 } | {
     error?: undefined;
     ok: boolean;
@@ -73,9 +73,9 @@ export declare function createWriteSecretHandler(): import("h3").EventHandlerWit
  * or the current stored value without changing anything.
  */
 export declare function createTestSecretHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    ok?: undefined;
     error: string;
     note?: undefined;
+    ok?: undefined;
 } | {
     error?: undefined;
     ok: boolean;

package/docs/content/template-clips-anonymous-intake.mdx

@@ -0,0 +1,148 @@
+---
+title: "Clips anonymous intake"
+description: "Collect one private Clips recording from an unsigned visitor with a short-lived signed intake URL."
+search: "Clips anonymous intake bug report signed upload token no login"
+---
+
+# Anonymous Clips intake
+
+Anonymous intake lets a customer submit one private Clips recording without signing in to Clips. The product that creates the intake URL still needs an authenticated Clips session or an authenticated backend action caller.
+
+The intake URL is a narrow upload capability. It is not a share link, a library session, or an agent access token.
+
+## Capability boundaries
+
+| Capability | Allows | Does not allow | Lifetime |
+| --- | --- | --- | --- |
+| Intake URL | Create one private recording, upload its chunks, finalize it, or abort it | List recordings, read media, open the library, or use normal agent APIs | One hour by default. Four hours maximum |
+| Agent context link | Read the completed recording through the normal scoped Clips agent surface after an authenticated host-side exchange | Be minted by the anonymous intake bearer, read any other recording, or act as the recording owner | Seven days for bug-report completions |
+| Clips session | Mint intake URLs and use the normal authenticated Clips UI | Nothing is added to the anonymous visitor's browser | Controlled by normal Clips auth |
+
+The intake token is signed with the existing scoped-token mechanism. The token is never stored in SQL. The database stores only the intake id, owner and organization binding, recording id, status, and expiry.
+
+## End-to-end flow
+
+1. Your authenticated product backend calls `create-recording-intake-link`.
+2. Clips returns a short-lived `/bug-report` URL.
+3. Your product opens that URL in an iframe or popup.
+4. The unsigned visitor fills in the report and records the screen.
+5. Clips creates one private recording and sends the media through its existing chunk and finalize pipeline.
+6. The completion page posts the recording id to the host window. It does not mint read access with the anonymous bearer.
+7. Your authenticated host backend exchanges the completed intake for a separate read-only agent context link.
+
+The browser never receives the Clips workspace session. If the create response is lost after Clips attaches the recording, retrying the same signed create request returns that recording's upload URLs instead of creating a second row. Expired or terminal intake URLs remain unusable.
+
+## Mint an intake URL
+
+`create-recording-intake-link` is a UI and HTTP action. It is not exposed as an agent tool because minting a bearer upload capability is an explicit integration operation.
+
+Call it from an authenticated same-origin browser or from an authenticated backend caller:
+
+```ts
+const response = await fetch(
+  "https://clips.example.com/_agent-native/actions/create-recording-intake-link",
+  {
+    method: "POST",
+    headers: { "Content-Type": "application/json" },
+    credentials: "include",
+    body: JSON.stringify({ ttlSeconds: 3600 }),
+  },
+);
+
+if (!response.ok) throw new Error("Could not create the Clips intake URL");
+
+const { result } = await response.json();
+// result.url is safe to give to the unsigned visitor.
+```
+
+`ttlSeconds` is optional. It must be between 60 seconds and four hours. The default is one hour. The response also includes `intakeId`, `expiresAt`, and `ttlSeconds`.
+
+The create request is safe to retry with the same `intakeId` and `intakeToken` if its response is lost. Clips returns the existing recording after attachment; it never creates a second recording for the same intake. Do not retry with a different intake token or reuse the upload URLs after an abort.
+
+Do not mint this URL in an anonymous browser. Do not put a long-lived Clips session or a service credential into the customer-facing page.
+
+## Embed the intake page
+
+Pass the returned URL directly to an iframe. The URL already contains the signed `clip_intake_id` and `clip_intake` query parameters.
+
+```tsx
+<iframe
+  src={result.url}
+  allow="display-capture; camera; microphone"
+  title="Report a problem"
+  style={{ width: 420, height: 560, border: 0 }}
+/>
+```
+
+The recorder opens a top-level popup when the visitor starts capture. Browser media permissions and screen capture require a user gesture in a top-level browsing context. If popups are blocked, the page falls back to navigating the current window.
+
+## Receive the completed recording
+
+The done page posts `agent-native.clips.bug-report.submitted` to the opener and the embedding parent. For anonymous intake, the message intentionally contains `agentAccessStatus: "unavailable"` and no agent link. Retain the `intakeId` from the mint response on the trusted host, then exchange it server-side after receiving the `recordingId`. Validate both the Clips origin and the message source before using the payload.
+
+```ts
+const clipsOrigin = "https://clips.example.com";
+let recorderWindow: Window | null = null;
+
+window.addEventListener("message", (event) => {
+  if (event.origin !== clipsOrigin) return;
+  if (recorderWindow && event.source !== recorderWindow) return;
+  if (event.data?.type !== "agent-native.clips.bug-report.submitted") return;
+
+  if (event.data.agentAccessStatus !== "unavailable") return;
+  // Send event.data.recordingId and the retained intakeId to your trusted
+  // backend. Do not send the anonymous clip_intake token from this page.
+});
+```
+
+The payload includes `recordingId`, `recordingUrl`, `embedUrl`, `agentShareUrl`, `agentContextUrl`, `agentAccessExpiresAt`, and `agentAccessStatus`. For anonymous intake, `agentAccessStatus: "unavailable"` is expected until the trusted host performs the exchange. Do not treat it as an empty recording result or let the visitor call the exchange action.
+
+Use the authenticated `create-intake-agent-link` action from the trusted host backend. Keep the `intakeId` returned by `create-recording-intake-link` with the host's authenticated Clips session, and pass the completed `recordingId` from the message:
+
+```ts
+const response = await fetch(
+  "https://clips.example.com/_agent-native/actions/create-intake-agent-link",
+  {
+    method: "POST",
+    headers: { "Content-Type": "application/json" },
+    credentials: "include",
+    body: JSON.stringify({ intakeId, recordingId }),
+  },
+);
+
+if (!response.ok) throw new Error("Could not create the Clips agent link");
+const { result } = await response.json();
+// Send result.contextUrl to the support agent or backend here.
+```
+
+The exchange verifies the authenticated owner, organization, intake expiry, completed state, and recording binding before delegating to the normal scoped agent-link implementation. If the host already has an authenticated Clips session with access to the recording, it can also call `create-recording-agent-link` with the `recordingId`.
+
+## Self-hosting requirements
+
+Anonymous intake uses the same storage and database prerequisites as an authenticated recording:
+
+- A persistent `DATABASE_URL`.
+- A configured Builder.io or S3-compatible video storage provider.
+- The normal production auth and scoped-token configuration from [Deployment](/docs/deployment).
+- A public `BETTER_AUTH_URL`, such as `https://clips.example.com`, when the intake URL is minted outside a browser request.
+
+The intake action creates the recording with private visibility regardless of the organization's default recording visibility. The normal Clips access checks still protect the recording after intake completes.
+
+## Security checklist
+
+- Use HTTPS for the Clips app and the host product.
+- Treat the intake URL as a bearer credential. Keep it out of logs, analytics events, referrer data, screenshots, and support tickets.
+- Use the shortest useful TTL. One hour is the default.
+- Validate `event.origin` and `event.source` in the completion listener.
+- Keep the intake id and the authenticated exchange on the trusted host. Store the resulting `agentContextUrl` only where the support agent or backend needs it. It is also a bearer credential.
+- Never expose `/api/uploads/:recordingId/chunk` or `/api/uploads/:recordingId/abort` directly to anonymous users. Intake traffic goes through the signed `/api/clip-intake` transport, which checks the intake id, token, recording binding, owner binding, status, and expiry on every request.
+
+## Troubleshooting
+
+**The recorder opens a sign-in page.** Make sure the intake URL includes both `clip_intake_id` and `clip_intake`. The `/record` route is public for the intake handoff, while normal recording creation remains session protected.
+
+**The recording says the intake URL is unavailable.** The URL may have expired, been aborted, or be mid-creation. Retry the original create request once if its response was lost; otherwise mint a new intake URL. Each intake URL still creates at most one recording.
+
+**The completion has no agent link.** That is expected for anonymous intake: the visitor's bearer is write-only. Have the authenticated host exchange the retained `intakeId` and completed `recordingId` with `create-intake-agent-link`. A 409 means the recording is still being verified; retry from the trusted host after it becomes ready.
+
+**The page has no storage setup control.** Anonymous visitors cannot configure a Clips storage provider. Configure storage before minting intake URLs.

package/docs/content/template-clips-developers.mdx

@@ -94,11 +94,11 @@ window.addEventListener("message", (event) => {
 });
 ```
 
-Always validate both `event.origin` and `event.source` in the host. The completion payload includes `recordingId`, `recordingUrl`, `embedUrl`, `agentShareUrl`, `agentContextUrl`, `agentAccessExpiresAt`, and an explicit `agentAccessStatus` of `ready` or `unavailable`. When access is ready, `agentContextUrl` is a temporary, scoped URL that lets an agent read recording metadata, timestamped transcript segments, recommended frames and frame URLs, and browser diagnostics without receiving the user's workspace session. Normal agent links expire after two hours; embedded bug-report completions use a seven-day scoped link so asynchronous support tickets can be triaged. Treat an unavailable or expired link as an access failure, not an empty recording. `embedUrl` remains subject to the recording's normal viewer access.
+Always validate both `event.origin` and `event.source` in the host. The completion payload includes `recordingId`, `recordingUrl`, `embedUrl`, `agentShareUrl`, `agentContextUrl`, `agentAccessExpiresAt`, and an explicit `agentAccessStatus` of `ready` or `unavailable`. When access is ready, `agentContextUrl` is a temporary, scoped URL that lets an agent read recording metadata, timestamped transcript segments, recommended frames and frame URLs, and browser diagnostics without receiving the user's workspace session. Normal agent links expire after two hours; authenticated embedded bug-report completions use a seven-day scoped link so asynchronous support tickets can be triaged. Anonymous intake completions intentionally report `agentAccessStatus: "unavailable"` until the trusted host exchanges the retained intake id and completed recording id through the authenticated `create-intake-agent-link` action. Treat an unavailable or expired link as an access failure, not an empty recording. `embedUrl` remains subject to the recording's normal viewer access.
 
 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. A popup recording only sees diagnostics emitted inside the Clips window. Use the Chrome extension or attach diagnostics from the host product separately when the agent needs console and network context from the source tab.
 
-This pilot requires the reporter to already have an active session in the Clips workspace that owns the recording. The current cross-origin popup cannot preserve its completion channel through a first-time sign-in redirect, so users should sign in to Clips in a separate tab before launching it. A fully anonymous customer-support 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.
+This embedded flow requires the reporter to already have an active session in the Clips workspace that owns the recording. The current cross-origin popup cannot preserve its completion channel through a first-time sign-in redirect, so users should sign in to Clips in a separate tab before launching it. For a no-login customer-support flow, use [Anonymous Clips intake](/docs/template-clips-anonymous-intake). It creates a one-recording, write-only capability and keeps the normal owner-scoped upload endpoints protected.
 
 ## Data model
 
@@ -273,6 +273,7 @@ Two things live outside this schema on purpose: organization/member/invitation r
 | `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`                                                                                                             |
+| `clips_intake_sessions`                          | One-use anonymous intake capabilities bound to an owner, organization, and recording                                                                                           |
 | `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)                                     |
 | `recording_views`                               | Append-only per-view log (who viewed, when) — backs the owner-facing "Viewed by" popover, kept separate from the aggregate counters above                                     |
@@ -344,7 +345,7 @@ Recordings and transcripts are intentionally separate tables so the library and
 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 roughly 110 actions, grouped here by purpose:
 
 - **Recording lifecycle** — `create-recording`, `finalize-recording`, `update-recording`, `set-thumbnail`, `archive-recording` / `restore-recording` / `trash-recording` / `delete-recording-permanent`, `move-recording`, `tag-recording`, `reprocess-recording`, `import-loom-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.
+- **Bug reports** — `save-bug-report-context` stores redacted host-product context for recordings launched from `/bug-report`; `create-recording-intake-link` mints a one-use anonymous intake URL; `create-intake-recording` is the anonymous write step and `create-intake-agent-link` is the authenticated host-side exchange; `get-recording-player-data` returns the sidecar to editors. See [Anonymous Clips intake](/docs/template-clips-anonymous-intake) for the complete flow.
 - **Transcript & AI** — `request-transcript`, `cleanup-transcript`, `save-browser-transcript`, `regenerate-title` / `regenerate-summary` / `regenerate-chapters`, `set-chapters`, `generate-workflow`, `get-clips-ai-prefs` / `update-clips-ai-prefs`, `get-builder-credit-status`. (`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`, `delete-meeting`, plus calendar wiring `connect-calendar` / `disconnect-calendar` / `sync-calendars` / `list-calendar-accounts`.

package/docs/content/template-clips.mdx

@@ -116,6 +116,7 @@ Live demo: [clips.agent-native.com](https://clips.agent-native.com).
 - [**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 customizing or extending the template.
+- [**Anonymous Clips intake**](/docs/template-clips-anonymous-intake) — collect one private recording from an unsigned visitor with a short-lived signed URL.
 - [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.178.1-nightly-20260910175201",
+  "version": "0.178.1",
   "description": "The agentic application framework for building autonomous agents with intuitive UIs",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -446,8 +446,8 @@
     "y-protocols": "^1.0.7",
     "yjs": "^13.6.32",
     "zod": "^4.3.6",
-    "@agent-native/toolkit": "^0.19.7-nightly-20260910175201",
-    "@agent-native/recap-cli": "0.5.28"
+    "@agent-native/recap-cli": "0.5.29",
+    "@agent-native/toolkit": "^0.19.7"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",