io.github.uindow/uindow

Uindow - AI browser immune to prompt injections

Uindow drives a real, signed Chromium/Electron browser with genuine OS-level input - actual cursor movement, real keystrokes, and native file dialogs rather than synthetic page events. It runs entirely on your own machine and your own network, and every line of code it executes sits in plain sight in this repository.

Automate it three ways:

• No code - build automations in the integrated editor and record complex workflows without writing code.
• From any AI agent - Uindow ships a local MCP server, so Claude, Cursor, VS Code, or any MCP-compatible assistant can list, create, and run automation agents directly. See Control Uindow from AI agents.
• Write automations in pure JavaScript - Use the integrated development environment to write, test, and debug automations with ease. Auto-completion, code healing, JavaScript parsing, and linting are all built in.

Running Uindow

Option 1 - npx (recommended)

One command to fetch the CLI and launch the app:

npx -y @uindow/cli app:start

Other lifecycle commands:

npx @uindow/cli app:status  # check whether the app is running
npx @uindow/cli app:stop    # stop the app

Option 2 - Run locally from source

Clone the repository and launch the app directly from source.

git clone https://github.com/uindow/uindow.git uindow
cd ./uindow/
npm install
npm start

What actually runs on your machine

Both options do the same minimal thing: they fetch the official, signed Electron binary (only if it isn't already on your machine) and tell Electron to load dist/run.js. That's the whole story - a genuine, trusted, signed Electron runtime executing code that is clearly visible to you in this repository. Nothing is hidden, obfuscated, or pulled in behind your back.

Option 3 - Install prebuilt binaries

Prefer a packaged installer?

We build signed binaries for macOS, Windows, and Linux directly from the dist source, and host them on the Releases page (current and older versions).

The build tooling lives in this repository and does exactly one job: it archives the dist folder into app.asar. You can audit it and reproduce the build yourself.

In order to use the app, create a free account at Uindow and follow the on-screen instructions.

Control Uindow from AI agents (MCP)

Uindow exposes a local Model Context Protocol server so any MCP-compatible assistant can drive web-automation agents directly - no glue code required. The server runs locally over stdio and is launched on demand with npx:

npx -y @uindow/cli mcp

Tools exposed: app_docs, app_start, app_stop, app_status, list, create, update, delete, start, stop, status, execute, logs.

Call list first to discover agent indexes.

All clients use the same launch command - npx -y @uindow/cli mcp - only the file location and the wrapping key differ.

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

{
    "mcpServers": {
        "uindow": {
            "command": "npx",
            "args": ["-y", "@uindow/cli", "mcp"]
        }
    }
}

Restart Claude Desktop. The Uindow tools appear under the tools (🔌) menu.

Claude Code

claude mcp add uindow -- npx -y @uindow/cli mcp

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project) - same shape as Claude Desktop:

{
    "mcpServers": {
   

... [View full README on GitHub](https://github.com/uindow/uindow#readme)