About Aginx Browser
Aginx Browser is a frozen browser project for AI agents; active development has moved to diting, and this repository remains available for historical reference. Its last release was v0.6.4, and existing HTTP API calls can be ported with the process name changed.
Key features
- 01Repository frozen at v0.6.4
- 02Active development moved to diting
- 03Historical repository remains readable
- 04HTTP API shape remains compatible
Use cases
- 01Locate the current project and releases
- 02Maintain an existing v0.6.4 installation
- 03Port HTTP API calls to diting
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://browser.aginx.net/mcpclaude mcp add --transport http net-aginx-aginxbrowser https://browser.aginx.net/mcp{"mcpServers":{"net-aginx-aginxbrowser":{"type":"http","url":"https://browser.aginx.net/mcp"}}}Open in Cursor{"servers":{"net-aginx-aginxbrowser":{"type":"http","url":"https://browser.aginx.net/mcp"}}}Open in VS Code{"mcpServers":{"net-aginx-aginxbrowser":{"type":"http","url":"https://browser.aginx.net/mcp"}}}{"mcpServers":{"net-aginx-aginxbrowser":{"serverUrl":"https://browser.aginx.net/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project README⚠️ This project has moved
AginxBrowser is now diting.
Same engine, same team, new name. All active development, releases, and issues live at the new address — this repository is frozen at v0.6.4 and kept readable for history.
→ github.com/yinnho/diting
The engine-first browser for AI agents. One Rust binary, built-in V8, no Chromium — HTTP is the only protocol face. Everything this repo was, plus a year of engine work since: ~25 MB cold start, own CSS/layout/paint stack, receipts on every response, flow replay, and a v0.8.x release line.
If you starred this repo, star diting — that's where the next release lands.
# install the current release (from the new repo)
curl -fsSL https://browser.aginx.net/install.sh | sh
# or Homebrew
brew tap yinnho/diting && brew install yinnho/diting/diting
Migration notes
| here (aginxbrowser) | new (diting) | |
|---|---|---|
| Last release | v0.6.4 (frozen) | v0.8.x |
| Binary name | aginxbrowser | diting |
| Config dir | ~/.aginxbrowser | ~/.diting (env bridge in place) |
| Env prefix | AGINXBROWSER_* | DITING_* (old names still accepted) |
| HTTP API | same shape — port your calls, only the process name changes |
Old v0.6.x release assets and the homebrew-aginxbrowser tap stay up so
existing installs keep working; they will not receive updates.
Why the rename
The engine grew its own identity: own V8 integration, own runtime
(diting_runtime), own CSS/layout/paint stack — no Chromium anywhere.
The new name owns that story. Full continuity notes in the
new repo's docs.
The Chinese README carries the same migration notice: 中文迁移说明.
Historical description, superseded by diting:
AginxBrowser
The Browser for AI Agents. See the live web. Read it. Act on it. Remember it. One Rust binary with built-in V8, no Chromium required.
Humans have Chrome. Agents have diting.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.