OpenAI 2026 hackathon

Cutscene

Most screen recorders save pixels. Cutscene saves the page structure too, so zooms land on the real element and a stale demo fails like a failing test.

Solo project by Ayush Kumar · 1 likes · 0 comments

Archive position — measured, not model output

1 like on Devpost

506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #918 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

Cutscene is a developer tool that records browser interactions (screen + DOM events) into structured data, enabling precise zooms, interactive demos, quality reports, and regeneration of UI artifacts like README GIFs. It is built as a Chrome extension with a React-based editor and a Node.js runner.

What changed

The author describes an evolution from traditional screen recorders that only save pixels to one that also captures page structure (DOM events), allowing for better fidelity in demos, improved automation, and more accurate quality checks.

Single most important open question

Does the tool have any real-world adoption or usage beyond the author’s own development environment? The description contains no evidence of customers, revenue, or product-market fit beyond self-reported claims.

Back to contents

What The Product Actually Is

The description states that Cutscene:

  • Records a Chrome tab and DOM events into one bundle: a WebM file, a versioned JSONL trace, and a metadata file.
  • Captures clicks, inputs, navigation, scrolling, viewport changes, ranked locators, element bounds, and clock sync markers.
  • Outputs:
    • Zooms that frame the recorded element instead of cursor position.
    • Multiple formats: MP4, GIFs, screenshots, Playwright flow skeletons.
    • An interactive demo (static ZIP with no backend).
    • A recording quality report.
    • Regeneration capability via a demo.yml file.

The tool is built using:

  • Chrome extension (Manifest V3)
  • MediaRecorder API for video
  • Content script for trace capture
  • React, TypeScript, Vite, Zustand for the editor
  • ffmpeg.wasm for rendering
  • Playwright for replaying and validation

Inference This is a developer-focused tool aimed at improving documentation and testing workflows in UI-heavy applications.

Back to contents

Positioning & Claim Evolution

The author positions Cutscene as:

  • A replacement for traditional screen recorders.
  • A solution to stale demos caused by pixel-only recording.
  • A way to make UI interactions more precise, automated, and testable.

Claims include:

  • Zooms land on the real element instead of a guess.
  • Quality reports flag accessibility issues.
  • Regeneration ensures artifacts stay up-to-date with code changes.
  • Privacy is handled at capture time.

Inference The tool evolved from solving a personal pain point (re-recording README GIFs) into a structured solution for UI demo and testing workflows. The positioning implies it targets developers working on web apps, especially those using frameworks or tools that benefit from precise interaction capture.

Back to contents

Target Customer & ICP

The description does not name specific customers or personas.

Inference

Based on the tool’s functionality, likely targets:

  • Developers building UI-heavy applications.
  • Teams maintaining documentation (e.g., READMEs, step-by-step guides).
  • QA engineers or CI/CD teams looking to automate demo generation and detect drift.

Not evidenced No explicit customer segments, personas, or use cases beyond the author's own workflow.

Back to contents

Business Model & Pricing Evidence

The description does not state a business model or pricing strategy.

Inference Given that it is a self-contained tool built as an open-source project (with no mention of monetization), it likely operates without a direct revenue stream. It may be intended for internal use or as a developer utility.

Back to contents

Technical & Delivery Signals

The description states:

  • Built with Manifest V3 Chrome extension.
  • Uses chrome.tabCapture, MediaRecorder, and content scripts.
  • Trace data is stored in JSONL format with ranked locators.
  • Editor uses React, TypeScript, Vite, Zustand.
  • Runner validates demo.yml, replays in Chromium, and generates outputs.
  • Uses WebAssembly (ffmpeg.wasm) for rendering.
  • Privacy masking happens at capture time.

Inference

The tool is technically mature enough to support:

  • Multi-format output generation.
  • Clock synchronization across multiple timelines.
  • Drift detection and reporting.
  • Regeneration of artifacts based on current builds.

Back to contents

Traction & Maturity Signals

The description does not provide evidence of traction, revenue, or adoption beyond the author’s own use case.

Inference

The tool is described as a hackathon project (submitted to OpenAI 2026 hackathon), suggesting it may be early-stage. The author mentions:

  • 315 tests pass.
  • Typecheck is clean.
  • 6 of 6 Chromium end-to-end tests pass.
  • 10 of 10 sampled zooms landed correctly.

However, these are self-reported performance metrics and do not indicate external usage or product-market fit.

Back to contents

Competitive Context

The description does not mention competitors or market positioning.

Inference

Cutscene appears to be in a niche space related to UI recording, demo generation, and automated testing. It overlaps with tools like:

  • Loom (for screen recording)
  • Playwright (for test automation)
  • Storybook (for component documentation)

But it is not clear how it differentiates itself from these or whether it competes directly.

Back to contents

Key Risks & Red Flags

Red flags

  • No evidence of customers, revenue, or product-market fit.
  • Tool is limited to Chrome and DOM-based apps only.
  • No mention of scalability or enterprise features.
  • The tool is described as a personal project (1-person team).
  • No mention of open-source licensing or community adoption.

Inference Cutscene may be a proof-of-concept or early-stage prototype. Its narrow scope and lack of traction raise questions about its viability as a commercial product.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the intended market for Cutscene beyond personal use?
  2. Has there been any external feedback or testing from other developers?
  3. Are there plans to expand support beyond Chrome or DOM-based apps?
  4. How does Cutscene handle cross-origin iframes or shadow DOMs?
  5. Is there a plan to monetize or commercialize the tool?
  6. What are the long-term goals for the project, and how do they align with developer needs?

Back to contents

Investment/Partnership Verdict

Not evidenced No financial data, traction, or commercial strategy is provided.

Inference Cutscene appears to be a technical prototype built by one person, likely as part of a hackathon. It shows strong engineering execution and solves a real problem for developers, but lacks evidence of market demand, adoption, or scalability. It may be an early-stage idea with potential, but not yet a product ready for investment or partnership.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.