Aginx Browser

net.aginxPublished by aginx.netOfficial publisherv0.5.26Updated Oct 30, 2026

Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

Remote stealth browser for AI agents: search, fetch, click, download and type in persistent sessions over a streamable HTTP endpoint.

What you can do
  • Search and fetch web pages through a stealth browser session
  • Click, type and otherwise act on live pages
  • Download files encountered during browsing
  • Keep state across steps in persistent sessions
  • Connect over a single streamable HTTP endpoint with no local install
When to use it
Use it when an assistant needs to interact with live websites rather than just read static pages — searching, filling in forms, clicking through flows or downloading files — and you prefer a hosted endpoint over running a browser locally.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. The README notes the project has been renamed to diting, with the old v0.6.4 release frozen and no longer updated.
Before you install
The README states this project has moved and is frozen at v0.6.4, so fixes and updates land elsewhere. The server acts on live pages (clicking, typing, downloading) and keeps persistent sessions, so actions can change remote state or pull files onto your side. No authentication is declared for the endpoint.

Installation

In SourceWeft

  1. Open Aginx Browser in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.aginx%2Faginxbrowser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "aginx-browser": {
      "type": "http",
      "url": "https://browser.aginx.net/mcp"
    }
  }
}

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.

bash
# install the current release (from the new repo)curl -fsSL https://browser.aginx.net/install.sh | sh
# or Homebrewbrew tap yinnho/diting && brew install yinnho/diting/diting

Migration notes

here (aginxbrowser)new (diting)
Last releasev0.6.4 (frozen)v0.8.x
Binary nameaginxbrowserditing
Config dir~/.aginxbrowser~/.diting (env bridge in place)
Env prefixAGINXBROWSER_*DITING_* (old names still accepted)
HTTP APIsame 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.

Source: README.md at commit 8c1b237

Tools

0
SourceWeft has not read this server's tools yet.

Version history

24
  1. v0.5.26LatestOct 1, 2026
  2. v0.5.25Oct 1, 2026
  3. v0.5.24Sep 30, 2026
  4. v0.5.23Sep 30, 2026
  5. v0.5.22Sep 30, 2026
  6. v0.5.21Sep 29, 2026
  7. v0.5.20Sep 29, 2026
  8. v0.5.18Sep 28, 2026
  9. v0.5.16Sep 27, 2026
  10. v0.5.15Sep 27, 2026
  11. v0.5.14Sep 27, 2026
  12. v0.5.12Sep 27, 2026
  13. v0.5.11Sep 26, 2026
  14. v0.5.9Sep 26, 2026
  15. v0.5.8Sep 25, 2026
  16. v0.5.7Sep 25, 2026
  17. v0.5.5Sep 23, 2026
  18. v0.5.3Sep 21, 2026
  19. v0.5.2Sep 20, 2026
  20. v0.5.1Sep 20, 2026
  21. v0.5.0Sep 19, 2026
  22. v0.4.5Sep 18, 2026
  23. v0.4.4Sep 17, 2026
  24. v0.4.3Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts