Clips: Record a Bug Once and Let Your Coding Agent Pull the Full Context From a URL

Steve demos Clips, a free open source screen recording app with a Chrome extension, built as an agent-native alternative to Loom. Instead of manually typing bug reports to a coding agent and pasting in screenshots and debug logs, you record your screen once. Clips captures the video plus network requests, browser logs, and client errors, redacts sensitive information, and gives you a link.

The point of the link is that it works for both humans and agents. A person can play the recording. An agent can pull the transcript, grab video snapshots at any timestamp, and read the captured logs and network requests directly from the URL through metadata and APIs. The video ends with a broader argument: free, forkable, canonical open source apps beat paid SaaS for this kind of tooling.

The Problem: Typing Bug Reports to Agents by Hand

The video opens on a Claude Code session where a bug report has been typed out manually. The prompt describes a dashboard panel issue, references pasted images, and trails off into frustrated gibberish. This is the workflow Clips replaces: describing visual bugs in text, attaching screenshots one at a time, and copying in logs yourself.

Recording With the Chrome Extension

Clips now ships as a Chrome extension, shown installed from the Chrome Web Store as "Agent-Native Clips." From any tab you hit record, talk through the issue, and demonstrate the flow on screen. Steve records himself reproducing a bug in an analytics dashboard's "Add panel" dialog while narrating what is wrong.

While you record, Clips captures everything on screen along with network requests, browser logs, and errors thrown on the client, with their full details. Sensitive information is redacted. When you stop, you get a shareable link at clips.agent-native.com.

Handing the Clip to an Agent

The demo then pastes the clip URL into Claude Code with a two-word instruction: "fix this." Because the link carries metadata and APIs, the agent fetches an agent-context JSON endpoint from the URL and starts working with the recording directly.

From there the agent reads console errors captured in the clip, notices three errors around specific timestamps, and pulls video frames at those exact moments using the clip's frame API. It then correlates what it saw in the frames with the codebase and identifies the problem: the "Add panel" dialog uses a plain textarea where it should use the app's standard chat composer stack.

So the agent can effectively see and hear anything in the video: transcript, snapshots at any timestamp, and all the logs and network requests that were shared with it. Steve positions this against expensive apps like Loom for the same demo-and-share workflow, whether you are sending context to an agent or collecting bug reports from teammates.

Free Canonical Apps Over Bloated SaaS

Clips is 100% free and open source. You can fork and customize it. It is built on the agent-native framework, which powers several other free apps you can sign up for and use, or fork. The repo shown is github.com/BuilderIO/agent-native, described as "a framework for building agent-native applications," and its templates page shows Clips alongside other apps described as "100% free and open source."

Steve closes with his thesis, illustrated with a sketch contrasting one-size-fits-all SaaS that costs money against a free canonical open source app you fork and customize. In his view this is the future of software: rather than bloated SaaS that charges a lot and still lacks what you need, free open source canonical apps you can adapt in any way you want.

Key Takeaways

• Clips is a free, open source screen recorder with a Chrome extension that captures video plus network requests, browser logs, and client errors, with sensitive data redacted.
• Every clip link is agent-readable: from the URL alone, an agent can pull the transcript, grab video frames at any timestamp, and read all captured logs and requests.
• The demo workflow is paste the clip URL into Claude Code with "fix this," and the agent fetches context, inspects frames at error timestamps, and locates the root cause in code.
• It is positioned as an alternative to paid tools like Loom for demoing issues and collecting bug reports from teammates.
• Clips is built on the agent-native framework (github.com/BuilderIO/agent-native), and Steve argues forkable canonical open source apps are the future over bloated paid SaaS.

Resources

• BuilderIO/agent-native on GitHub: the open source framework that powers Clips and other agent-native apps, shown in the video.
• Clips itself, hosted at clips.agent-native.com and installable as the "Agent-Native Clips" Chrome extension, shown in the Chrome Web Store during the demo.