Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@dokobot/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@dokobot/cli
Connect your Chrome browser to Dokobot as a doko — letting AI agents browse, interact with, and extract content from the real web.
Quick Start
npx @dokobot/cli connectThe CLI will guide you through setup automatically — no manual configuration needed.
Prerequisites
- Node.js 18+
- Chrome with remote debugging enabled:
- Open
chrome://inspect/#remote-debugging - Check "Allow remote debugging for this browser instance"
- Open
Install
# Run directly (no install needed)
npx @dokobot/cli connect
# Or install globally
npm i -g @dokobot/cli
dokobot connectCommands
connect
Connect a Chrome browser to Dokobot.
dokobot connect # Interactive setup
dokobot connect --name "Work Chrome" # Name your doko
dokobot connect --browser-url http://127.0.0.1:9222 # Custom Chrome instance
dokobot connect --device-id <id> # Reconnect an existing dokolist
List all registered dokos on this machine.
dokobot listremove
Remove a registered doko.
dokobot remove <device-id>config
Configure API key and server URL interactively.
dokobot configupdate
Check for CLI updates.
dokobot updateOptions
| Option | Description |
|---|---|
--api-key <key> |
API key (or set DOKO_API_KEY env) |
--server <url> |
Server URL (default: https://dokobot.ai) |
--verbose |
Enable verbose logging |
How It Works
- The CLI connects to your local Chrome via Chrome DevTools Protocol
- It registers your browser as a doko on the Dokobot server
- AI agents can then send commands to your browser — navigating pages, clicking elements, extracting content, and more
License
MIT