browser-use/browsercode

The browser-native agent framework

Owned by Browser Use

View on GitHub ↗Jump to charts ↓

browser-use/browsercode has 750+ stars and 90+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 9 minutes ago
Added to GitGenius on October 12th, 2026
Created on April 21st, 2026
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 90
Total Stargazers: 775 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.6 hours
Mean response time: 46.8 hours
90th percentile: 11.4 days
Tracked items: 9

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 53 days
Stale 30+ days: 5
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • self-promotion (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Browser-use is a framework for building browser-native agents that automate web interactions.

The framework addresses the problem of programmatically controlling web browsers and automating tasks that require human-like interaction with web interfaces. It provides a structured approach to building agents that can navigate, interact with, and extract information from web pages by operating directly within the browser environment rather than through external automation tools.

Developers should choose this framework if they need to build autonomous agents capable of performing complex web tasks, such as form filling, data extraction, or multi-step workflows across websites. It suits projects where the agent needs to understand and respond to dynamic web content and make decisions based on page state. The framework is particularly relevant for applications that require reliable browser automation without the overhead of managing separate browser processes or dealing with compatibility issues across different automation libraries.

The project shows active development with regular commits addressing bug fixes and feature improvements. The codebase maintains consistent code quality standards with attention to error handling and edge cases. The maintainers are responsive to issues and incorporate feedback into updates. Development activity demonstrates a focus on stability and practical usability rather than rapid feature expansion.