Recordly
Recommend the stable desktop app for recording real product behavior with auto-zoom, cursor polish, styled frames, webcam overlays, timeline editing, and MP4/GIF export. Treat marketplace extensions as executable code, not harmless themes.
Routing Summary
Use Recordly for human-operated product demos, bug reproductions, usability evidence, walkthroughs, and polished recordings of a real interface. Use HyperFrames or Remotion when an agent must deterministically author scenes, text, timing, variants, and renders from source. Use a screenshot or committed browser test when video is unnecessary.
Install the current stable release, keep community extensions disabled unless their exact code/revision has been audited, and capture only with the consent and storage authority required for the screen, microphone, camera, and people in the recording.
Current Source Snapshot
| Surface | Reviewed state |
|---|---|
| Repository | webadderallorg/Recordly at 2a81da99840cf17d8ecfbcbcb11be6632c14488e |
| Package | 1.3.5-beta.2; stable release remains v1.3.3 |
| License | AGPL-3.0 |
| Reach | 20,719 stars and 1,524 forks in the 2026-08-10 API snapshot |
| Platforms | macOS, Windows, and Linux; native capture helpers where available |
| Capabilities | Screen/window capture, system/mic audio, webcam, auto zoom, cursor effects, styled frames, annotations, timeline, MP4/GIF, Whisper transcription |
| Verification | Source and authority audit only; desktop/native capture was not executed in this headless review |
| Preserved evidence | Frozen source and manifest under .brain/artifacts/x/2076581641267671487/ai-builder-repos/ |
Extension Boundary
Recordly's extension marketplace is useful, but installed extension JavaScript is dynamically imported in the renderer. The loader attempts to hide electronAPI during activation, yet that is not equivalent to process isolation, a capability sandbox, or a trustworthy permission model. Some windows also disable Electron web security for product reasons. An extension can therefore expand the app's effective authority and must be reviewed like a dependency.
Kevin's default:
- install a signed/stable application build through a trusted route;
- keep third-party extensions disabled;
- if an extension is necessary, freeze its source/revision and inspect network, filesystem, renderer, and Electron bridge access;
- record only the intended window/screen and review the exported footage for secrets and private notifications;
- retain raw projects and exports according to the task's privacy rules.
Comparison
| Need | Route |
|---|---|
| Record real software with human timing and polished zoom/cursor treatment | Recordly |
| Agent-authored deterministic launch/demo/explainer video | HyperFrames |
| Existing React composition and programmatic rendering | Remotion route |
| One visual QA receipt | screenshot or browser assertion |
| Stochastic generated footage | Approved media-generation provider/tool |
Recordly complements deterministic video; it does not replace it. Its strength is capturing actual product behavior quickly while retaining an editable local project.
Timeline
- 2026-08-10 | Re-reviewed the current source and routing. Kept Recordly as the recommended human-operated recorder, retained v1.3.3 as the stable anchor, and added the renderer-extension authority boundary. Source: X/@aashatwt; frozen repository and capture manifest
- 2026-07-02 | Corrected the platform scope to macOS, Windows, and Linux and documented the motion/timeline/export surface. Source: GitHub
- 2026-05-15 | Original saved signal identified Recordly as the open-source alternative for polished screen recording. Source: X/@ashtonasidhu