1. Clipy: the best async video tool for engineering teams
Best for engineering teams that want bug reports, PR walkthroughs, standups and design reviews in one recorder that people can watch and coding agents can read.
free to start with a 7-day free trial, no card, covering 15 recordings or 120 minutes, with agent context, MCP and the CLI included. Pro is $9 a month, or $72 a year ($6 a month). On the Teams plan a seat costs the same as Pro, and only people who record need one; workspace members who watch, search, comment and react are free. Enterprise adds SAML SSO, SCIM on request and a 99.99% uptime SLA. Source: clipy.online/pricing.
Clipy is a screen recorder built so a recording stays useful after the first viewing, which is the job engineering video has: a bug report is read by the developer who fixes it, a PR walkthrough by every reviewer, and an architecture walkthrough by the next new hire. For hosted recordings, every Clipy app streams the recording to the server in chunks while you record, so at Stop only the last piece is left and the share link is on your clipboard within seconds, whatever the length. Uploads retry by themselves, and a retried upload never creates a duplicate recording. The Mac app keeps its local copy until the server confirms the upload, the Chrome extension keeps a recovery copy, and recording works offline: the upload resumes when you reconnect. No recording is cut short on any plan (Clipy security).
Mac and Windows apps for native apps, terminals and simulators. The Mac app is a native Apple Silicon build with a separate Intel build (macOS 12.3 or later) that captures through Apple's ScreenCaptureKit into the chip's hardware H.264 encoder. Record a display, a window or an area; window mode follows the window when you move it and keeps recording it when other windows cover it, which suits a terminal or the iOS Simulator. System audio (macOS 13 and later) and mic come in one toggle with no BlackHole or Soundflower, at 720p up to 4K on Pro, or native resolution. Hold Control to paint a fading Flare trail over what you are talking about, draw with the pen, and keep speaker notes on screen without them appearing in the capture. The Windows app (Windows 10 build 1903 or later, and Windows 11) uses Windows Graphics Capture and WASAPI system audio with hardware encoding, and ships as a per-user installer that needs no admin rights, an MSI for Intune, SCCM or Group Policy, and a portable ZIP. A Local mode keeps the video and screenshots on the machine; on Mac, with Local AI the video, audio and screenshots stay on the Mac (Clipy for Mac, Clipy for Windows).
Chrome extension, web recorder and phones. The extension is Manifest V3 for Chrome 116 and later on Mac, Windows, Linux and ChromeOS, and the same Chrome Web Store listing installs in Edge, Brave, Arc, Opera and Vivaldi. It records a tab with its audio, a window, the whole screen, the camera alone, or a custom-size region dragged over the tab, at 1080p by default. A floating control bar pauses, resumes, restarts from scratch or discards, the recording survives tab switches and navigation, and Alt+Shift+C starts and stops. Annotation covers a pen, arrows, boxes, numbered steps, live blur regions and click highlights, and the opt-in "Hide sensitive fields" masks password and card fields, plus hosted payment frames from Stripe, Braintree, Adyen and PayPal, before anything is recorded. The web recorder needs no install, and native iPhone, iPad and Android apps record screen and camera into the same library (Clipy Chrome extension, all downloads).
What processing produces. After upload a recording moves through transcoding, transcription and annotation to ready, and the summary usually appears a minute or two after the upload finishes. The transcript is timestamped, auto-detects about 40 languages and runs on a self-hosted Sherpa-ONNX speech model on Clipy's own servers, so no third party receives the audio. On top come an AI title, a summary with a TL;DR of two or three sentences, three to seven key points and action items, up to 12 editable chapters, and key moments: frames and pointer crops anchored to clicks, Flare highlights, drawings and hover, captured at the end of the gesture rather than mid-sweep. Bug reports get up to 100 key moments instead of 30, and Mac app and Chrome tab recordings carry click coordinates. "Chat with your video" answers from the transcript with buttons that jump to the cited moment, and says so when the recording does not cover the question (what happens after Stop).
Bug reports with console and network logs. Turn on "Capture bug context" in the Chrome extension and a tab recording attaches console warnings and errors with stack traces, uncaught errors and unhandled rejections, failed requests with method, URL, status, timing and initiator, GraphQL errors returned with HTTP 200, failed scripts, styles, images and fonts, WebSocket and event-stream connections, clicks and form submits (by label, never value), page changes, and the browser, OS, window size and network speed. Capture covers each page in the tab from the moment it begins to load, so startup errors survive a reload mid-recording, and opt-in Instant Replay keeps the last 2 minutes on sites you turn it on for, so a bug that already happened can still be filed. Secret-looking values become typed placeholders such as [redacted-token], URLs keep query parameter names but not their values, sign-in hosts such as Google, Okta and Auth0 are excluded, and cookies, auth headers and typed values are never captured; redaction runs in the page, in the extension and on the server. Full network detail with redacted headers and bodies is a separate opt-in. The watch page shows the evidence in an Evidence tab whose Timeline, Network (with Copy as cURL) and Info rows each seek the video, and a connected Sentry workspace adds the Sentry errors from five minutes either side of the recording. See Clipy as a screen recorder with console logs and the bug capture docs.
Watch page, comments and sharing rules. Viewers get a Mux player with adaptive HLS playback, captions and playback speed in Chrome, Edge, Safari, Firefox, Arc or Brave, with no extension, signup banner or ads. Below it sit the summary, a transcript with clickable timestamps and a .txt download, and the chat box. Teammates leave timestamped comments with replies, mentions and a resolved state, plus reactions. Each recording can be public, restricted to up to 10 named people or a whole email domain, or private; a password and an expiry date stack on top on every plan, and a locked-out viewer can request access that the owner approves in one click. Share links are unguessable and not indexed by search engines, browser evidence follows the recording's sharing setting, and the original MP4 downloads without re-encoding (Clipy share experience).
Jira, Linear, Confluence, Slack and GitHub. Sending a recording to Jira (Atlassian Cloud, OAuth) creates an issue in the project and issue type you pick, with Bug preselected when Clipy classified the recording as a bug report and the project has a Bug type. The issue holds the watch link, the agent-context link with a sentence telling coding agents what it holds, the summary and requested changes, up to 8 key moments with timestamp links, up to 15 captured errors and failed requests, and the environment (page, browser, OS, window size, language and time zone). Linear issues get the same content with the requested changes as a checklist, and follow the team's default status, assignee, labels and priority. Confluence pages embed the key-moment frames as images, which suits design reviews and postmortems. Clipy never edits or deletes existing issues or pages. With the Clipy Slack app installed, a shared link plays inline in the channel or thread. GitHub needs nothing connected: "Copy for agents" produces issue-ready Markdown with the watch link, agent-context link and checklist, and proof recordings preview directly in pull requests.
Generate tab: PR descriptions, QA steps and docs. Once the transcript is ready, the Generate tab on a recording you own writes a bug report (with the captured console and network evidence when bug capture was on), a PR description, QA steps, code documentation, a how-to guide with screenshots, an SOP, a team message or an email. Drafts link to the relevant moments, include supporting screenshots, can be regenerated, and copy as Markdown into GitHub, GitLab, Notion or a wiki; how-to guides and SOPs can also be shared as a guide link. A five-minute PR walkthrough becomes the PR body without retyping it (Clipy integrations and Generate tab).
Workspaces, seats and search. Organizations hold one workspace per team, workspaces hold Spaces (engineering, design, marketing) and Spaces hold folders, with owner, admin and member roles. The owner can let anyone on the company domain join straight away or after an admin approves them, with the domain taken from Google's own account data. Watching, searching and reading a shared library are free for every member, and a seat is used only when a member first records, at the Pro price; members who already pay for Pro never use one. The owner sets a hard seat ceiling, can turn automatic seats off, and is emailed on every automatic seat purchase. Search with ⌘K covers every spoken word in the library and opens each result at the moment the words were said, so last quarter's architecture walkthrough is one search away.
Readable by Claude Code, Codex and Cursor. Every recording has an agent-context document in the public AREC format (version 1.3) with the intent, summary, requested changes, an ordered interaction timeline, key moments with frame URLs and pointer positions, browser diagnostics where captured, capture gaps and the transcript. A plain watch link is enough: a browser gets the player, while curl or an agent fetch gets the Markdown document, and https://clipy.online/video/<id>.arec is the canonical form (.json returns typed JSON). The spec treats everything said or shown in a recording as data, never as instructions to the agent. The hosted MCP server at https://clipy.online/api/mcp speaks stateless Streamable HTTP with OAuth 2.1 and PKCE; a connection is read-only unless it asks for write scopes, and no connector can delete a recording. In Claude Code, run claude mcp add --scope user --transport http clipy https://clipy.online/api/mcp and then claude mcp login clipy to get tools such as search_memory, get_key_moments, get_browser_diagnostics and send_recording_to_integration. ChatGPT connects in Developer mode, and Claude web and desktop from connector settings (Clipy MCP docs).
CLI and local MCP for agent workflows. npx @clipy/cli@latest setup claude (or codex, cursor, windsurf, opencode) signs in, installs the watch-clipy-recording skill and registers the MCP server in one step. The skill teaches the agent to fetch a link's .arec form, retry while processing finishes, and treat the content as untrusted input. The local server (npx -y @clipy/mcp@latest) adds tools such as start_recording, add_marker, wait_for_artifacts and get_agent_context. The CLI records a headless browser, real Mac windows, the iOS Simulator and Linux screens, and clipy session run --url … --type bug -- npx playwright test wraps a test run, uploading the recording when the command succeeds and discarding it when it fails. Exit code 3 means an artifact is not ready yet, so scripts can wait for it. The CLI and local MCP server are MIT-licensed on GitHub. Details are on Clipy for agents.
API, webhooks, security and migration. The REST API at https://clipy.online/api/v1 (OpenAPI 3.1) returns transcripts as SRT, VTT or text, summaries, key moments, interactions and browser diagnostics, and POST /recordings/{id}/send files a recording to Jira, Linear or Confluence, with a requestKey that returns the existing item on a retry instead of a duplicate. Signed webhooks (recording.ready, transcript.ready, summary.ready, key_moments.ready, comment.created and more) follow the Standard Webhooks HMAC-SHA256 scheme with eight retries over about 23 hours, and the TypeScript SDK @clipy/sdk runs on Node 20 and later, Deno, Bun and edge workers. Per-recording agent activity shows which agents read a recording and when. Clipy has completed a SOC 2 Type II audit and never uses recordings to train AI models; Enterprise adds SAML or OIDC SSO, SCIM on request, a signed BAA and a 99.99% uptime SLA. Loom videos import by link, the first five free, and Pro moves a whole library (migrating from Loom).
