browser-use/workflow-use

⚙️ Create and run workflows (RPA 2.0)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on May 6th, 2025
Open Issues & Pull Requests: 60 (+0)
GitHub issues: Enabled
Number of forks: 349
Total Stargazers: 4,179 (+1)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.9 hours
Mean response time: 5.7 days
90th percentile: 12.1 days
Tracked items: 51

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 70% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 37
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 410 days
Stale 30+ days: 37
Stale 90+ days: 36

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Workflow-use is a Python framework for creating and running robotic process automation workflows that interact with web browsers.

The tool addresses the need to automate repetitive web-based tasks by providing a structured way to define and execute workflows that can control browsers, interact with web pages, and perform actions like form filling, data extraction, and navigation. It builds on browser automation capabilities and frames itself as a modern approach to RPA, enabling users to create sequences of automated actions without writing traditional scripts for each task.

The project suits teams and individuals who need to automate web interactions at scale, particularly those already working within the browser-use ecosystem. It works well for scenarios involving Telegram automation, data collection workflows, and other browser-based processes that would otherwise require manual repetition. Organizations evaluating adoption should consider whether their workflow patterns fit the framework's abstraction model and whether they prefer this structured approach over writing custom automation scripts.

The project shows active development with regular commits addressing core functionality and bug fixes. Work spans multiple areas including workflow execution logic, browser interaction handling, and integration features. The codebase receives consistent refinement with attention to both new capabilities and stability improvements.