Hyperbolic Gateway Hyperbolic Gateway
Local-first agent tooling

A real browser.
A real API surface.

Hyperbolic Gateway gives an AI agent a visible Chromium browser and a typed REST bridge, running on your machine. No cloud browser, no account, no separate Node install.

Start here Read the docs

Start in three steps

Use the app like a browser. Connect an agent when you want it to operate the same session.

Open a page

Type a URL in the address bar. Tabs, cookies, downloads and history work normally.

Connect an agent

Open Settings → MCP Clients. Choose Hyperbolic Browser, Hyperbolic Rest, or a legacy alias.

Let it work

The agent reads the page, acts with human-like input, and can call saved REST wrappers.

Two surfaces, one local app

Pick the surface that fits the job. Both use the same desktop process and local data store.

hb-browser

Hyperbolic Browser

A visible, stateful Chromium browser that agents can inspect and drive. Humanized input, page marks, tabs, downloads, Cortex memory and Shadow Walk controls.

MCP browser tools human in the loop local memory
hb-rest

Hyperbolic Rest

Turn a REST endpoint into a saved, typed tool. Define the request and response once; agents call flat arguments. Credentials stay host-bound and encrypted.

saved wrappers typed arguments credential vault

For people using it

You stay in control of the machine and the accounts.

  • No hosted browser or remote dashboard.
  • Your sessions, downloads and memory stay local.
  • Human approval for sensitive actions and account claims.
  • Settings, logs and audit history are visible in the app.
  • Use the normal browser UI; an agent shares the session.
  • Close a tab or disable the bridge at any time.
  • Wrapper credentials are write-only in the UI.
  • Legacy Kuang configs continue to work while you migrate.

For developers

Hyperbolic Gateway speaks MCP over stdio and exposes a localhost bridge. New configurations should use hb-browser and hb-rest.

Browser server

Connect with the bundled runtime or Node, then point it at the running app:

hb-browser
HB_BRIDGE_URL=http://127.0.0.1:4111

Legacy label: kuang · legacy env: KUANG_BRIDGE_URL

REST server

Add a wrapper and bind a credential in Settings → Wrappers:

hb-rest
HB_BRIDGE_URL=http://127.0.0.1:4111
HB_WRAP_TOKEN_FILE=<userData>/wrap/token

Legacy label: kuang-wrap · legacy env: KUANG_WRAP_TOKEN_FILE

The MCP Clients tab generates the exact paths and environment for this installation. Full architecture, recipes, security notes and the wrapper format live in the documentation.

Legacy & inspiration

Hyperbolic Gateway was previously named Kuang Grade Mark Eleven. The current product is the same local browser and REST workspace under a new identity. Existing MCP labels, environment variables and wrapper files are kept as compatibility aliases.

"A Kuang Grade Mark Eleven penetration program. Icebreaker. The military stuff, the heavy artillery."
— William Gibson, Neuromancer (1984)

The original name and quote are preserved as inspiration. Hyperbolic Gateway is an independent project and is not affiliated with William Gibson, Neuromancer, or the fictional device.