THUDM

OpenWebAgent: Build LLM-Powered Web Browsing Agents

OpenWebAgent combines a Chrome extension with a configurable server to let LLM-based agents interpret webpages and take actions. It suits developers prototyping browser agents who can operate and maintain the server stack themselves.

View on GitHub Compare
Stars
29
Forks
2
Stars, last 30 days
-1
Last commit
2.2 years ago
Contributors
1

Our take

Inactiveno commits in over a year

Health score

16/100

How it is scored
Activity
19
Community
4
Issues
21
Pull requests
20

-1 stars in the last 30 days

  • Fewer contributors than 91% of the projects we track

OpenWebAgent provides a concrete extension-and-server starting point for web-agent experiments, but its inactive status and single-contributor history make it a project to adopt only when you can maintain it yourself.

Good fit if

  • You want to study or adapt a Chrome extension and server workflow for LLM-driven webpage interaction.
  • You can configure the model provider, credentials, and MongoDB or local storage yourself.
  • You are prepared to maintain a project with no recent commits or releases and work primarily attributable to one contributor.

Look elsewhere if

  • You need a project with recent releases, active development, or a broader contributor base.
  • You need a ready-to-use agent service without setting up and operating the server.
  • You require a clearly stated license before evaluating or incorporating the code. The repository metadata provided here does not specify one.
All health signals
Last commit2024-08-11 (2.2 years ago)
Commits, last 90 days0
Releases, last 12 months0
Contributors1
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age2 years

Checked on 2026-10-12 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

28

Forks

2

Change since Nov 13, 2026: 0 stars·0 forks

Overview

OpenWebAgent is a toolkit for building web agents that automate interactions with webpages. It pairs a Chrome extension for user interaction with a server that accepts configurable models, aiming to turn user intent and page content into browser actions.

It is aimed at developers who want to experiment with or adapt a web-agent workflow, rather than people looking for a maintained, ready-to-deploy browser automation product. The project is inactive, so adoption also means taking responsibility for maintenance.

Key Features

  • Chrome extension interface for starting and controlling web-agent tasks.
  • HTML parser intended to simplify page content for model processing.
  • Workflow that combines user intent, action history, and parsed HTML.
  • Server designed to connect the workflow to configurable models.
  • OpenAI provider example in the server configuration, with instructions for other models in the server README.
  • MongoDB Atlas configuration, with local data storage also described as an option.
  • Extension source can be built with npm and installed in Chrome as an unpacked extension.

Use Cases

  • Researchers prototyping how LLMs can navigate and operate webpages.
  • Developers evaluating a model-backed browser-agent workflow and adapting its planner or server integration.
  • Teams building a Chrome-based demonstration where users need to observe and control agent tasks.
  • Developers exploring how parsed HTML and action history can inform successive browser actions.

What you need

Detected in the repository

  • JavaScript (main language on GitHub)

Getting Started

For the server, configure config/server_config.yaml, MongoDB settings, and the required environment variables, then run:

cd server
bash setup.sh
python agent/run_server.py

For extension build instructions and the full configuration details, see the repository README and the plugin and server READMEs.

License in Plain Words

No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.

Alternatives

  • opendia: OpenDia exposes an existing logged-in browser through MCP, while OpenWebAgent pairs its extension with a configurable agent server.
  • browserable: Browserable provides a self-hosted automation library and REST API, rather than OpenWebAgent's Chrome extension and configurable server setup.
  • stagehand: Stagehand is an automation SDK that can run with Playwright or Browserbase, while OpenWebAgent centers on a Chrome extension and server.
ProjectLanguageLicenseStarsStatus
OpenWebAgentJavaScript–29Inactive
opendiaJavaScriptMIT1.9kActive
browserableJavaScriptMIT1.2kInactive
stagehandTypeScriptMIT25.5kActive

Considerations

The project has had no commits in over a year and no releases in the past year. The measured contributor history is concentrated in one person, and there have been no recently closed issues or merged pull requests, so users should plan for self-support and maintenance. Running the example setup involves server configuration, API credentials, and database configuration; the README also describes local data storage as an option. No license is specified in the supplied repository metadata, so check the repository for licensing terms before use or redistribution.

Found this useful?

Share it with someone who would like OpenWebAgent.

Comparisons