Aginx Browser

What Aginx Browser does

Aginx Browser gives MCP-based agents a browser interface for interacting with the live web. Its documented operations include searching, fetching pages, clicking elements, and entering text. Persistent sessions let browser state continue between interactions rather than requiring every action to begin from scratch.

The browser is implemented as a Rust binary with built-in V8 and does not depend on Chromium. The historical project description positions it for agents that need to see, read, and act on web content. It belongs in browser-automation workflows where an agent must combine navigation with page interaction.

How it works

Agents communicate with the browser through MCP. The engine exposes HTTP as its protocol face, and the HTTP API keeps the same general shape across the project rename. Browser activity is organized around sessions, allowing later actions to use state retained from earlier requests.

The repository has been superseded by diting. The successor uses the same engine and continues development under a new name. The newer engine is described as including its own V8 integration and CSS, layout, and paint stack, with no Chromium dependency. Those capabilities belong to the continuing project line rather than to new releases from this frozen repository.

Setup and configuration

AginxBrowser’s repository is frozen at v0.6.4. Existing v0.6.x release assets and the homebrew-aginxbrowser tap remain available for installations that already depend on the old project, but they are not updated.

For active development and new installations, the project directs users to diting. Its documented installation paths are:

• Run curl -fsSL https://browser.aginx.net/install.sh | sh.
• Install through Homebrew with brew tap yinnho/diting && brew install yinnho/diting/diting.

The successor changes the binary name from aginxbrowser to diting and moves the configuration directory from ~/.aginxbrowser to ~/.diting. The environment-variable prefix changes from AGINXBROWSER_* to DITING_*, while the old names remain accepted through an environment bridge.

Tools and capabilities

• Search the web from an agent workflow.
• Fetch web pages for reading.
• Click page elements.
• Type into browser-controlled pages.
• Preserve state with persistent sessions.
• Run without Chromium using a Rust binary with built-in V8.

Limitations and notes

The original repository is historical rather than an active release line. Its last release is v0.6.4, and active releases, issues, and development have moved to diting. Teams adopting the successor should account for the renamed binary and configuration directory, although the HTTP API retains the same shape and the old environment-variable names are bridged.

The project description identifies HTTP as the only protocol face. Client configuration should therefore use an MCP client’s compatible HTTP connection method rather than assume a Chromium automation setup. The repository materials do not describe browser extensions, a Chromium fallback, or client-specific integrations.