Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for creators and technical teams who want AI agents to produce rough-cut videos from real footage instead of only generating scripts, thumbnails, or one-off editing prompts.
Who should use it
Who should skip it
Skip browser-use/video-use if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
browser-use/video-use is tracked by RepoRadar as a creative tool in the Creative Tools section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for browser-use/video-use are workflow potential (9.5) and momentum (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned browser-use/video-use a composite score of 8.4 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The recommended workflow gives an agent shell access over local media files and can call ElevenLabs for voice tasks, so first runs should stay on non-sensitive footage with a dedicated API key; Always-on VPS or Telegram usage extends the exposure window beyond a one-off local editing session, so remote runs should use a separate workspace and storage policy.