NTXM Logo
NTXM BROWSER MINI · v0.1.3 · 127.0.0.1:9090

NTXM Browser.The browser an agent attaches to.

NTXM Browser Mini is a desktop Chromium (CEF) that stays open on your machine — cookies, logins, and tabs included. An agent does not eat HTML or screenshots by default. It gets a small action map, acts by a short id, and gets the next map back in one call.

Version 0.1.3 · Windows x64POST /v1/observe · /v1/act · /v1/extractMCP /mcp · experimental
API contract /v1

Unsigned Binary NoticeAs a solo developer, my installers are currently unsigned. Windows Defender, SmartScreen, or your browser may show a "Windows protected your PC" warning or falsely flag the file as harmful. To proceed, click "More info" → "Run anyway". Use at your own risk.

NTXM Browser Mini desktop window

NTXM Browser is not another Chrome and not a cloud browser farm. It is the local agent browser: one warm profile, HTTP on port 9090, three tools.

What it does

Attach over HTTP /v1

An agent — script, NTXM Agent later, anything that can POST JSON — calls /v1. Sessions are s_19, not window=1&tab=4. One session is one tab. Delete closes that tab only.

01

You run NTXM Browser Mini

Normal desktop window. Your Google / airline / site logins live in that profile.

02

Observe

Ranked controls, short ids (a3f), a few facts, hard cap 800 tokens.

03

Act

fill / click / select / … in one request, optional wait — always returns a fresh observe.

04

Extract

You send a JSON schema; the browser fills it from the page. No LLM inside NTXM Browser.

Why this exists

One job. That's the product.

Playwright, Playwright MCP, Stagehand, and Browser Use already drive browsers. NTXM Browser does not try to beat them at fleets, stealth, or “click the blue button” on a server.

Attach any model to the Chrome that is already open, using a tiny map and your existing cookies.

That is the whole product.

0.1.3 — what shipped

Production door is /v1

Legacy /windows, /tabs, /page_map, /click still answer for old scripts. They are internal. Manifest and docs lead with /v1.

POST /v1/session*
Create / go / read / delete a tab; host allowlist
POST /v1/observe
Token-capped map + facts + rev; optional diff via since
POST /v1/act
Verb chain + wait; returns observe; typed errors
POST /v1/extract
Schema → JSON (tables/forms only; else extract_failed)
GET /v1/manifest
Machine description of the three tools
GET|POST /mcp
Experimental JSON-RPC: initialize / tools/list / tools/call
Async act wait (tab keeps painting)Short stable ids + reborn_id on remountblocked off-allowlistact navigate via CEF LoadURL after allowlistInstaller NTXM_Browser_Mini_Setup_0.1.3.exe
Measured · honest

Kitchen-sink fixture only.

Measured 2026-09-25 on the shipped 06-kitchen-sink.html only, base http://127.0.0.1:9090. Google Flights and live login traces are not part of this release pack.

7 ms
Warm observe

Target < 300 ms

9 ms
Act (click/fill) → observe

Target < 1.5 s

142
Observe tokens

Target ≤ 800

Deliberately not built

So you stop asking for the wrong product

No server-side natural language (act("click the blue button")) — the caller’s model picks the id

No cloud browsers, proxies, or CAPTCHA farm

No screenshot/HTML as the default agent path

No Playwright / CDP requirement

No tab groups

MCP is not a full SDK and not required to use the product

How an agent talks to it

Production is /v1

MCP (experimental): same three tools, JSON-RPC envelope at /mcp. Use it only if the host cannot call /v1. Cursor-style attach is not the 0.1.3 guarantee.

Allowlist: first successful origin locks the session. Navigate outside → blocked. A tunnel does not widen that.

Production endpointsLocal

POST http://127.0.0.1:9090/v1/session

POST http://127.0.0.1:9090/v1/session/s_19/go

POST http://127.0.0.1:9090/v1/observe

POST http://127.0.0.1:9090/v1/act

POST http://127.0.0.1:9090/v1/extract

GET http://127.0.0.1:9090/v1/manifest

Compare

Short. Accurate.

NTXM Browser is the hands. It is not the planner. A future NTXM Agent can call /v1; that is a different product.

NTXM Browser MiniPlaywright / MCPStagehandCloud agent browsers
What it isLocal desktop Chromium + /v1Library / MCP toolsNL act/extract on PlaywrightRented Chrome + agent
SessionYour profile, already logged inUsually a fresh contextYour script’s browserTheir machine
Default see~hundreds of tokens, short idsAccessibility snapshotModel + observeVaries; often heavier
Default extractSchema, no NTXM LLMYou parseTheir model + schemaTheir agent
You installOne Windows exe, port 9090Node + browsersSDK + keysAccount + hours

Who it is for

  • You want an agent to use your logged-in desktop browser
  • You want HTTP, not a driver stack
  • You care about tokens per step more than pixel computer-use

Not for

  • Replacing Playwright tests
  • 1,000 stealth sessions
  • “Just do the task” with no API

Requirements

  • Windows x64
  • Local port 9090
  • Installer may be unsigned (SmartScreen)

Privacy: local-first, no NTXM telemetry. The page the agent opens is between you and that site.

Questions Answered

Official: NTXM Browser Mini. In prose: NTXM Browser. Same app.
Start NTXM Browser Mini. Call /v1. Do not start with /tabs or raw HTML — that is leftover internal REST.
No. /content exists internally. Agents should observe → act → extract.
Playwright is the standard driver. NTXM Browser is a running desktop session with a small agent contract. Different job.
/mcp implements initialize / list / call as a subset. Treat it as experimental. Production integration is /v1.
The engine can open real sites. This release only publishes kitchen-sink benches and traces. Flights/login are not claimed in 0.1.3 notes.
Out of date. 0.1.3 is CEF + /v1 agent contract. Optional bearer auth may exist in settings; the public story is allowlist + local bind.

Local agent browser. /v1 is the door.

NTXM Browser Mini 0.1.3 — TechXcelerate · NTXM