Skip to content

Add LICENSE file (Apache 2.0 or MIT) so commercial integrations can adopt video-use #20

@withaxiom

Description

@withaxiom

Hi browser-use team — first off, this tool is excellent. The transcript-driven cutting approach (12KB text vs 45M tokens of frames) is the right design, and the OpenClaw/Hermes/Codex first-class support in the README setup prompt is a delight to see.

One thing keeping me from integrating video-use into a paid product I'm building: the repo currently has no LICENSE file. Without a license, default copyright applies and "all rights reserved" — which means downstream commercial use is technically a copyright issue for SaaS authors, even though the README clearly invites broad use.

Would you consider adding an explicit LICENSE file? Apache 2.0 would be ideal (it matches HeyGen's hyperframes, which I'm pairing video-use with) and grants commercial use clearly. MIT also works.

Happy to file a PR with the LICENSE text if that helps; just want to confirm intent first so I'm not stepping on whatever decision you've already made internally.

Thanks for the work — looking forward to using this in production once the license picture is settled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions