This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
OpenCap.dev
Screen-recording for agents
Loom, but for agents Your coding agent runs `opencap record start`, drives the demo (Playwright, the app, whatever), runs `opencap record stop`, and gets a share URL paired with a structured event log of every action it took. Then it drops the link wherever proof-of-work belongs: nPR description, Linear ticket, Slack channel. CLI + MCP first. Built for Claude Code, Codex, Cursor. Free forever for CLI + MCP.
OpenCap exists because a few weeks ago I asked Claude Code to record a Loom of a feature it just shipped for a client, post the replay link to Linear and the PR, and DM the client in Slack. To my surprise, no Loom CLI exists. The whole stack assumed a human was clicking record.
So Claude Code did the next best thing: Playwright screenshots, dumped to markdown, converted to a 20-page PDF the client probably never opened.
That afternoon I started building OpenCap.
Three things surprised me through the build:
1. The event log matters more than the video. The structured JSONL stream alongside the recording lets you trim by natural language ("cut to where the bug was reproduced") instead of scrubbing the timeline.
2. The share-link distribution is the real product. The recording is the artifact, but the agent dropping the link into Linear, Slack, and the PR without a human relay is what saves time on every ship.
3. MCP is a forcing function. Designing the surface as MCP tools first made every UX decision easier, because the user is an LLM, not a human.
Free forever for CLI and MCP. Paid tiers gate longer recordings and password-protected shares. Open to all feedback
About OpenCap.dev on Product Hunt
“Screen-recording for agents”
OpenCap.dev was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #159 on the daily leaderboard. Loom, but for agents Your coding agent runs `opencap record start`, drives the demo (Playwright, the app, whatever), runs `opencap record stop`, and gets a share URL paired with a structured event log of every action it took. Then it drops the link wherever proof-of-work belongs: nPR description, Linear ticket, Slack channel. CLI + MCP first. Built for Claude Code, Codex, Cursor. Free forever for CLI + MCP.
On the analytics side, OpenCap.dev competes within SaaS, Developer Tools and Artificial Intelligence — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how OpenCap.dev performed against the three products that launched closest to it on the same day.
Who hunted OpenCap.dev?
OpenCap.dev was hunted by Timothy Uzoegbu. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of OpenCap.dev including community comment highlights and product details, visit the product overview.
Timothy Uzoegbu