About Otto

Otto is a secure remote browser automation platform that allows you to control real browser tabs from your CLI or scripts without the need to host a browser farm. It achieves this by sending commands over WebSocket to a relay daemon, which then routes them to a Chrome extension that executes actions on live tabs. This makes it ideal for developers and automation teams who require real browser context for tasks such as testing, monitoring, and agent-driven workflows, all without the overhead of managing headless infrastructure.

Key Features:

• Real browser tabs, not headless farms: Execute commands on live Chrome tabs via a lightweight extension node, eliminating the need for Docker, Puppeteer farms, or cloud browser rentals.
• Remote CLI control: Send commands from your local machine to a browser running anywhere, with the relay handling routing and authentication.
• Code-driven browser interaction: Otto manages clicks, typing, navigation, and DOM manipulation with deterministic code, allowing agents to focus on strategy rather than low-level interactions.
• Secure by default: Features token authentication, replay protection, per-node ACL grants, and pre-ingress log redaction, with secrets stored securely in the OS keychain.
• Live debugging: Stream logs by requestId for real-time correlation of relay, controller, and node events.
• Network interception: Subscribe to HTTP traffic from managed browser tabs for inspection and data extraction.
• Site-scoped command bundles: Author and use custom, reusable commands for any domain, which run within the extension and are versioned and shareable.
• Agent and CI ready: Supports non-interactive setup, --json output, MCP server, streaming test harness, and agent runtime registration for seamless integration into automated environments.

Quick Start

To get started, ensure you have Node.js 20+ and npm 10+ installed. You will also need Chrome.

1. Install the CLI globally: npm install -g @telepat/otto
2. Run guided setup: otto setup
3. Load the unpacked extension into Chrome.
4. Register a controller identity: otto client register --name "my-laptop" --description "Local controller" followed by otto client login.
5. Verify the stack: otto commands list

For a comprehensive guide, refer to the Installation and Quickstart documentation.

How It Works

The system operates with a Controller (otto CLI or script) communicating via WebSocket to a Relay daemon, which then forwards authenticated commands to an Extension node running in Chrome. This extension interacts with managed browser tabs.

Using With AI Agents

Otto is optimized for headless automation and agent-driven workflows, offering non-interactive setup, machine-readable output, a programmatic API, and live log streaming for effective integration with AI agents.

Security And Trust

Security is paramount, with features like token authentication, ACL grants, replay protection, and log redaction. Otto does not automate credential submission, requiring manual user authentication.

Documentation And Support

Extensive documentation is available on the documentation site, covering installation, quickstart, architecture, protocol, CLI reference, security, and guides for agents. The repository and npm package are also available.

License

This project is licensed under the MIT License.