Quick answer: In October 2026 Clipy taught recordings to say what you expected to happen and what they did not capture, added clipy recheck to replay a recorded workflow against today's app, turned folders into help assistants, and started posting to Slack and creating GitHub issues next to Jira, Linear and Confluence. Clipy is ISO 27001 certified and HIPAA compliant alongside its SOC 2 Type II audit. AREC, the format agents read, has its own home at arecformat.org. Every item below has its own dated entry on the Clipy changelog.

  • For coding agents: expected results, a Missing evidence section and clipy recheck make a recording harder to misread and easy to re-verify.
  • For teams: folder help assistants, company workspaces, @mentions, Spaces, SAML SSO and SCIM on Enterprise.
  • On every platform: Homebrew for the Mac app, window and area recording on Windows 10, long tab sessions recorded from the tab's own video track in Chrome, and Google Meet recording.
  • Sharing: Post to Slack and create GitHub issues from the watch page, the CLI and the MCP server.
  • Trust: SOC 2 Type II audited, ISO 27001 certified, HIPAA compliant, plus a service guarantee under the plans.

What did Clipy ship in October 2026?

October had dated shipments on most working days, across the Chrome extension, the desktop apps, the CLI, the MCP server and the AREC format. Here are the headline launches. The sections below group the rest by who they help.

LaunchWhat it doesChangelog
Expected resultAn optional "What did you expect to happen?" on every recording, shown to agentsexpected-result
Missing evidenceThe AREC lists what a recording did not capture, so agents ask instead of guessingmissing-evidence
clipy recheckReplays a recorded workflow and reports, step by step, what still matchesclipy-recheck
Folder help assistantsA folder of training videos answers questions, with links to the exact momentfolder-help-assistant
Slack and GitHubPost a recording to a channel or DM, or open a GitHub issue from itslack-github
arecformat.orgAREC's own site with the spec, research and implementations; AREC 1.3.1arecformat-org
ISO 27001 and HIPAACertified and compliant, alongside SOC 2 Type IIiso-27001-hipaa
SAML SSO and SCIMEnterprise sign-in through your identity provider, membership synced from your directorysso-scim
HomebrewInstall the Mac app from Terminalhomebrew

What does a recording look like to an agent now?

The idea has not changed: record your screen, say what you want, share the normal Clipy link, and your agent or teammate gets it, like showing your screen to someone next to you. October made that handoff much harder to misread.

Say you are building a checkout page and the order total does not change when a coupon is applied. You record the tab with the Chrome extension with bug capture turned on, apply the coupon, and say "this should take 10% off, but the total stays the same." You wait silently for most of a minute while the page reloads, then press Stop.

On the watch page, open the Summary tab and fill in the new line: What did you expect to happen? You type "The total drops by 10% and the coupon shows under the line items." That is the expected result. It is optional, and you can add or change it any time. You can also set it from the CLI with --expected, through the REST API and the SDKs, or have an agent set it with the MCP update_recording tool.

You paste the link into Claude Code, Codex or Cursor. The agent reads the recording's AREC context: your words with timestamps, key moments with frames, the console errors and failed requests the extension captured, and now an Expected result section right after your intent.

Below that sits a new Missing evidence section. It lists exactly what each recording captured, so agents ask instead of guessing. In this take it notes the long silent stretch, so the agent knows there is no narration for that part of the video. In other takes it might flag clicks outside the recorded area or a highlight with no click, while Capture gaps just above says when console, network or cursor data is missing. The Missing evidence section opens with a plain instruction: ask the user instead of inferring across the gap. Capture gaps already said when telemetry was missing; now the recording also names the gaps inside what it did capture.

The agent fixes the bug. A week later, after a refactor, you want to know whether the flow still works. Run clipy recheck with the recording id and the start URL. It drives Chrome for Clipy through the recorded steps in a background window, captures a frame after each, and reports per step: matched, control not found, different screen, or could not map (typing, for example). The frames upload as a new Clipy proof, so the report comes with its own watch link and AREC link. Our guide to recording proof of an agent's UI fix shows the full loop.

What is new for coding agents?

October also filled in the agent workflow from capture to verification.

  • Chrome for Clipy grew up. Chrome for Clipy is a separate Chrome that belongs to your agent. It records one tab with its audio, with no picker or click, without taking your cursor or focus, and it runs on Windows too.
  • Complete browser bug capture. Bug-report tab recordings in the Chrome extension collect console output from the moment the page starts loading, uncaught errors, failed requests with GraphQL errors, and WebSocket and event-stream totals. Cookies and authorization headers are never kept. The bug capture docs cover every field.
  • The CLI records the real screen on Linux, including a private virtual display where agents run apps without touching yours. See the CLI docs.
  • A fuller developer platform. The REST API now uploads videos, deletes recordings, reads and posts comments, and serves captions as SRT, VTT or text. Signed webhooks fire when a recording, transcript, summary or key moments are ready, and official TypeScript and Python SDKs verify them for you.
  • Better YouTube imports. The CLI and MCP server read the original-language captions on auto-dubbed YouTube videos.
  • A guide for vibe coders. The new vibe coding guide shows how to use Clipy as the feedback layer for whatever AI builder or coding agent you already use.

AREC has its own home

AREC is the agent-readable recording format Clipy writes for every recording. In October it reached version 1.3, a stable spec that readers parse leniently and that stays backward compatible within 1.x. It now lives at arecformat.org, with the spec, schema, validator, research and implementations pages. The reference implementation moved to 1.3.1, which enforces the security rules for diagnostics precisely: access tokens and similar keys are caught in any spelling. The spec is public domain (CC0) and the validator is MIT licensed.

If you want the evidence behind the format, the AREC coding benchmark gives a coding agent the same landing-page task as raw video, a transcript, a Clipy AREC recording or a written spec, and compares the results. For the reasoning, read why agents need a recording format.

What is new for teams and enterprise?

For teams: folder help assistants, company workspaces, Spaces, SSO and SCIM.

  • Folder help assistants. Turn any folder into a help assistant on Pro. People ask a question in plain words and get an answer drawn from that folder's recordings, with a link to the exact moment and the screen shown there. Share it with a link: anyone can ask with no signup, and it only answers from recordings that person could already watch. A valid-since date flags older recordings as possibly out of date.
  • Company workspaces. Anyone signed in with a company Google account can set up or join their company's workspace with no invite. Recordings stay private to their maker until shared.
  • Teams and Enterprise plans. Pricing shows Pro, Teams and Enterprise, with a 7-day free trial, no card needed. On Teams, viewers are free and only people who record need a seat.
  • Collaboration. @mentions, resolved threads and Spaces keep feedback moving, and timestamped reactions land at the moment they are about.
  • Guides and SOPs from a recording. Share as a guide writes a how-to guide or SOP from a recording, with the video playing beside it.
  • Enterprise identity. SAML SSO and SCIM provisioning work with Microsoft Entra ID, Google Workspace, Okta or any SAML or OIDC provider, and owners can require single sign-on.
  • Teams help docs. The new Teams docs cover invites, roles, sharing, Spaces, comments, seats and onboarding.

What changed on Mac, Windows, Chrome and mobile?

Clipy runs on Mac, Windows, iPhone and iPad, Android and Chrome. Here is what improved.

Screenshots on the web, Mac and Windows

The screenshot editor on the web and in the Mac and Windows apps now has 18 tools. Point at something with a callout bubble, number your steps, dim everything except what matters with a spotlight, or enlarge fine print with a magnifier. Hide private details with pixelate, blur or a solid bar, then set the image on a gradient, colors taken from the screenshot or a blurred copy of it, with padding, rounded corners, a shadow and a window frame. Save a look to reuse it, and everything stays editable after you save. The full list is on the changelog.

Mac

  • Homebrew. Install the Mac app with brew install --cask clipy-recorder/tap/clipy-recorder. Details are on the changelog and the Mac screen recorder page.
  • Record a window by itself. Window recordings capture only that window, even under other windows, and follow it when it moves.
  • Clipboard history. Press Shift+Cmd+V (Ctrl+Shift+V on Windows) to paste anything you copied earlier. Clipboard history now keeps up to 10,000 items for up to 90 days, and favorites stay until you remove them.
  • Local AI on macOS 26. Local mode transcribes on the Mac with Apple's newest speech model while you record, so the transcript is ready the moment you stop.

Windows

  • Window and area recordings on Windows 10. The app checks what the OS supports and records windows and custom areas on Windows 10.
  • Window check. Clipy checks the selected window before every take.
  • Reduce background noise works in the Windows app. See the Windows screen recorder page.

Chrome and mobile

  • Long tab recordings. Chrome extension 2.1.53 records long tab sessions from the tab's own video track.
  • Google Meet. Record a Meet call from the extension, with the other participants' audio from the tab and your microphone. The Google Meet recorder page walks through it.
  • Android. Clipy for Android added push notifications for comments, replies and reactions, App Links that open Clipy links in the app, and search across what was said in your library.
  • Search shows dates. Library search now shows when each result was recorded, so the right take is easy to spot.

How do recordings reach Slack, GitHub and your other tools?

In October Clipy started posting to Slack and creating GitHub issues. Connect GitHub and Clipy creates an issue in a repository you pick, with the summary, key moments, captured errors and the agent context link. Post to Slack sends a recording to a channel or DM, where it plays inline. Both live on the watch page under Copy for agents, in the CLI as clipy send, and in the MCP server.

They sit beside the Jira, Confluence and Linear integrations, which shipped earlier in the month: create a Jira or Linear issue or publish a Confluence page from a recording, carrying the summary, key moments with screenshots, the watch link and the agent context link. The integrations page lists everything Clipy connects to. See also how to generate a bug report from a screen recording.

What is new in trust and security?

Clipy is ISO 27001 certified and HIPAA compliant, alongside its SOC 2 Type II audit. Enterprise includes a signed BAA for teams handling health information, and Enterprise customers can request the SOC 2 report under NDA. The security page has the details.

Under the hood, Clipy keeps an append-only audit log of consequential account and sharing actions and backs up the database and audit log daily to a private bucket.

There is also a service guarantee, right under the Subscribe buttons on the plan screen: a fix within 24 hours for anything you report, and if Clipy does not work out, a full refund within 14 days. Message us from the chat.

Where can I see every change as it ships?

This post is the hub. Each feature above has its own dated entry on the Clipy changelog, with a stable anchor you can link to, and the October section lists dozens of smaller shipments this roundup leaves out. We ship most days. For the bigger picture, start at the Clipy for agents page.

Frequently asked questions

Where can I see every change Clipy ships?

The Clipy changelog at clipy.online/changelog lists every user-facing change with its date. Major features get their own entry with a stable anchor, such as /changelog#clipy-recheck, so you can link straight to one.

What is the expected result on a Clipy recording?

It is an optional answer to "What did you expect to happen?" that the recording's owner can fill in any time on the watch page, in the Summary tab, or set from the CLI with --expected, the REST API, the SDKs or the MCP update_recording tool. Agents see it in the recording's AREC context, and Jira, Linear and Confluence reports include it, so the agent compares what happened against what should have happened.

Does clipy recheck click anything destructive?

No, not by default. clipy recheck replays clicks by their recorded label, never by raw screen position, and it skips controls whose names read as irreversible, such as delete, pay, send or submit, unless you pass --allow-destructive. Steps it cannot map, like typing, are reported rather than guessed.

Is Clipy ISO 27001 certified and HIPAA compliant?

Yes. Clipy is SOC 2 Type II audited, ISO 27001 certified and HIPAA compliant. Enterprise includes a signed BAA, SAML SSO and SCIM provisioning, and Enterprise customers can request the SOC 2 report under NDA.

How do I install the Clipy Mac app with Homebrew?

Run brew install --cask clipy-recorder/tap/clipy-recorder in Terminal. The fully qualified name matters, because it points at Clipy's own tap.

How do I try the new features?

Clipy is free to start with a 7-day free trial, no card needed. Sign in with Google, record, and share the normal Clipy link. People you share with need no signup to watch. Some features, like folder help assistants, are on Pro.

Every one of these features is live today. Record your next bug, walkthrough or handoff, share the normal Clipy link, and see how much more your agent and your team get from it. Clipy is free to start with a 7-day free trial, no card needed: download Clipy for Mac or Windows, or add the Chrome extension, and check pricing when you are ready for Pro.