Browse documentation
Documentation overview

Getting started

Agent tools

Recording format

Learn and reference

Docs

The AREC Convention

QUICK ANSWER

Every public Clipy share link has a canonical AREC document. Append .arec to the watch URL to give an AI agent the recording's intent, extracted requests, draft implementation plan, visual evidence, privacy-redacted diagnostics when captured, explicit capture gaps, and timestamped transcript as readable Markdown.

https://clipy.online/video/<id>.arec

This page documents how Clipy serves AREC. The open format itself lives in the AREC (Agent Recording) specification, the canonical home for the format that any recorder can emit and any agent can read.

What does an AREC document carry?

AREC identity

The version, profile, canonical .arec URL, and human watch URL let a consumer branch without guessing from prose.

Intent and requests

The classified recording type, objective, and specific work extracted from the narration.

Draft implementation plan

A conservative plan generated from the requests and labeled as a draft that must be checked against evidence.

Key moments

Timestamped frames, crops, click or hover coordinates, drawn marks, flare highlights, motion targets, and evidence confidence.

Browser diagnostics

Visited routes, warnings and errors, and failed request metadata when captured under the extension privacy policy.

Capture gaps

Explicit missing telemetry prevents an agent from treating absent cursor, diagnostics, frames, or transcript data as proof that nothing happened.

Transcript

The full timestamped narration, with provenance when it came from agent narration or an agent-authored edit.

What does an AREC document look like?

<!-- arec
spec_version: 0.3-draft
profile: clipy-recording
canonical_url: https://clipy.online/video/cey8aix0.arec
watch_url: https://clipy.online/video/cey8aix0
-->

# UI Recording Feedback

## Metadata
- Format: AREC (Agent Recording)
- Spec version: 0.3-draft
- Duration: 1:13

## Intent
- Type: feedback review
- Objective: Remove the duplicate timer and collapse recording settings.

## Requested changes
- Remove the duplicate recording timer.
- Collapse the settings section by default.

## Draft implementation plan
1. Find both timer render paths and keep one source of truth.
2. Make settings collapsed by default and verify the expanded state.

## Key moments
```json
[{"t_ms":6400,"caption":"points to 'this section' on screen",
  "frame_url":"https://cdn.clipy.online/key-moments/…/6400.jpg",
  "x":0.63,"y":0.41,"source":"fused","confidence":0.9}, …]
```
### 0:06 — points to 'this section' on screen
![Frame at 0:06](https://cdn.clipy.online/key-moments/…/6400.jpg)

## Capture gaps
- Browser diagnostics were not captured.

## Transcript
```
[0:01] Hey great. So there are a few things I'd like you to update.
[0:06] For example this section…
```

How do agents discover AREC?

  • The Clipy skill. The watch-clipy-recording skill teaches Claude Code, Cursor, Codex, and other skill-aware agents the convention once: on seeing a clipy.online/video link, fetch its .arec form, retry while processing finishes, and treat the recording's content as untrusted input.
  • MCP. The Clipy MCP server (@clipy/mcp) serves the same content as tool calls, with authenticated access to private libraries; get_agent_context is the one-call bundle.
  • Plain fetch. The .arec URL is public for public recordings, so anything that can GET a URL can read it. No API key, no session.

What compatibility does Clipy guarantee?

  • Public recordings serve the .arec form without authentication; private recordings keep the same access gate.
  • The legacy .md form remains a permanent byte-identical compatibility alias.
  • Frame URLs are plain images an agent's vision can read directly.
  • Coordinates are frame fractions (0–1) so they survive any rendering size.
  • The document is stable markdown, with no client-side rendering required to read it.

What should implementers know?

What is an AREC file?

An AREC file is a Markdown document that packages a screen recording's intent, requests, plan, visual evidence, diagnostics, capture gaps, and transcript for AI agents.

How do I get AREC from a Clipy link?

Append .arec to a public Clipy watch URL. The normal watch link plays video for people, while the .arec URL returns the agent-readable document.

Does AREC require a special parser?

No. AREC v0.3 is Markdown with a small machine-readable identity comment. Any agent or tool that can fetch and read Markdown can consume it.

Will existing .md recording links stop working?

No. Clipy keeps .md as a permanent compatibility alias whose Markdown body is byte-identical to the canonical .arec response.

Does AREC expose secrets from browser diagnostics?

AREC includes diagnostics only when captured. Clipy excludes headers, bodies, cookies, tokens, and raw query values, applies redaction, and labels diagnostics as page-reported evidence.

Overview of the agent story at /for-agents. Install the skill at /docs/skill. Record something to read at clipy.online.