Show It Works

Verify an uploaded recording and publish it.

Write title, taskName, ownerContext and publicContext in English (code en, locale en-US) — this project's language — and follow that locale for dates and numbers. The answer says so when what you sent is not in it. Leave code, identifiers, commands and file paths exactly as they appear in the repository, and leave worktreeName as the checkout's own directory name rather than translating it. This creates a direct R2 upload for an MP4 or WebM recording, filed under the project this API key belongs to. Worktree and task are public; ownerContext is shown to project members only, never through the public link; publicContext is shown only when explicitly supplied as public-safe.

Permanently delete a recording.

Get a public link for a ready recording, with the retainUntil deadline after which the link stops working. Report the expiry alongside the link.

List the task names already used in this API key's project, so you can reuse an existing one instead of inventing a near-duplicate. Copy `taskName` verbatim into `create_video_upload`. Names are folded case-insensitively and on whitespace, so one entry can cover several spellings, listed as `variants`. `recordingCount` is how many recordings carry the task right now, and `untagged` counts the recordings filed under no task at all. A name is listed while at least one of its recordings is still inside its retention window — 14 to 60 days after upload depending on the project's plan — and once the last of them reaches that deadline the name goes from this list with it. `firstUsedAt`/`lastUsedAt` are upload times. Only your own uploads are counted by default; pass `mine: false` to count every project member's. Without `query`, entries come back most-recently-used first, `truncated` means more names exist than `limit` returned, and `totalTasks` says how many. Other optional filters: `taskName` (substring), `createdAfter`/`createdBefore` (ISO timestamps), `limit`. A filter narrows the recordings that are counted, so the counts and dates then describe that window rather than the project's whole history. Optional `query` instead returns the tasks of the recordings that best match a description of the work, ordered by match quality — only the best-matching recordings nominate a task, so that answer is a shortlist rather than the project's whole vocabulary, `totalTasks` and `truncated` describe just those tasks, and `untagged` is omitted. The counts and dates of a task shown that way still cover every one of its recordings, not only the matching ones. `query` matches by meaning in any language, and a query in English (code en, locale en-US) — this project's language — also matches on wording.

List the recordings in this API key's project, including dashboard reviewer comments and viewed status. Expired recordings are omitted; each row's retainUntil is when that recording and its public link are deleted, and firstViewedAt is when someone first played the public link, or null if nobody has. Ignore expiresAt, which is upload-authorization plumbing and always reads as past on a published recording.

Find recordings in this API key's project by meaning as well as by wording — describe what the session was about, or name a task, and the closest recordings come back ranked. Use it before inventing a new TASK value, to find the recordings an earlier session already filed under one. Optional filters: taskName (substring), mine (only your own uploads — unlike list_tasks, this one searches every project member's recordings unless you pass it), createdAfter/createdBefore (ISO timestamps) and limit. Expired recordings are never returned. A query in any language works, because matching is semantic; this project works in English (code en, locale en-US), and a query in that language also matches on wording, which is the more precise half.