Unstuck Docs GitHub

Requirements

What Unstuck needs on the machine your agent runs on, from the browser it drives, and from the person who takes over.

Your agent's machine

Needs
TypeScript SDK (@velmlabs/unstuck) Node.js 20 or later
TypeScript SDK in-process (needs a relay) Cloudflare Workers: see Cloudflare Workers. On Node.js 20 or later, Deno and Bun, opt in with mode: 'in-process'
Python SDK (unstuck) Python 3.10 or later
MCP server (npx -y @velmlabs/unstuck-engine --mcp) Node.js 18 or later, for npx
Unstuck Browser over MCP (--mcp --browser) Node.js 18 or later, and Chrome or Chromium on the machine (npx playwright install chromium is enough; CHROME_PATH picks one)
Unstuck Browser in Python (unstuck.wrap) Python 3.10 or later with async Playwright (playwright.async_api); sync Playwright isn't supported yet. The browser-use integration (pip install 'unstuck[browser-use]') needs Python 3.11 or later

The engine comes inside the package for these systems; there is nothing else to install:

The browser your agent drives

A Chromium-based browser: Chrome, Chromium or Edge. Unstuck attaches to the page over the Chrome DevTools Protocol, so it works with Playwright's chromium, Puppeteer, Selenium with Chrome, hosted browsers and anything else with a debugging port. Playwright's Firefox and WebKit browsers aren't supported.

The person who takes over

Any current browser: Safari or Chrome on a phone, or any desktop browser. By default the link opens only on the machine your agent runs on. With an UNSTUCK_API_KEY, it opens on any device, from anywhere (Send the link anywhere). The page loads from view.unstuck.sh and connects to relay.unstuck.sh.

Network

Without an API key, nothing leaves your machine. With one, the engine makes an outgoing secure WebSocket connection to relay.unstuck.sh on port 443; nothing needs to reach your machine from outside. Everything sent through the relay is end-to-end encrypted.