Ironbee Browser Devtools Cli

IronBee Browser DevTools CLI

Command-line interface for browser automation, debugging, and testing using Playwright. Part of IronBee DevTools. This CLI targets the browser platform; for Node.js backend debugging see ironbee-node-devtools-cli, and for HTTP/gRPC/GraphQL/WS + log + database verification see ironbee-backend-devtools-cli.

ironbee-browser-devtools-cli and ironbee-devtools-cli are aliases — both ship with the same package and target the browser platform by default. Examples in this doc use ironbee-browser-devtools-cli; substitute ironbee-devtools-cli if you prefer the shorter name.

Installation

# Install this skill (skills.sh)
npx skills add ironbee-ai/ironbee-devtools-skills

# Install the CLI binary
npm install -g @ironbee-ai/devtools

Quick Start

# Navigate to a URL
ironbee-browser-devtools-cli navigation go-to --url "https://example.com"

# Take a screenshot
ironbee-browser-devtools-cli content take-screenshot --name "homepage"

# Get page content as text
ironbee-browser-devtools-cli content get-as-text

Ref-based workflow (recommended for AI agents): Call a11y take-aria-snapshot first to get refs (e1, e2, ...), then use refs in interaction click --selector "e1" or content take-screenshot --annotate for numbered element labels.

Global Options

| Option | Description | Default | |--------|-------------|---------| | --port | Daemon server port | 2020 | | --session-id | Session ID for browser state persistence | auto | | --json | Output results as JSON (recommended for AI) | false | | --quiet | Suppress log messages | false | | --verbose | Enable debug output | false | | --timeout | Operation timeout | 30000 | | --headless | Run browser in headless mode | true | | --no-headless | Run browser with visible window | - | | --persistent | Preserve cookies/localStorage | false | | --no-persistent | Clear state on session end | - | | --user-data-dir | Browser user data directory | OS temp | | --use-system-browser | Use system Chrome | false | | --browser-path | Custom browser path | auto |

AI Agent Recommended Options:

# JSON output for parsing, quiet mode for clean output, session for state persistence
ironbee-browser-devtools-cli --json --quiet --session-id "my-session" 

Tool Domains

The CLI provides tools organized by domain:

| Domain | Description | Reference | |--------|-------------|-----------| | navigation | Page navigation (go-to, back, forward, reload) | [navigation](./references/navigation.md) | | content | Content extraction (screenshot, PDF, HTML, text, video recording) | [content](./references/content.md) | | interaction | User interactions (click, fill, hover, scroll) | [interaction](./references/interaction.md) | | a11y | Accessibility snapshots (ARIA, AX tree) | [a11y](./references/a11y.md) | | o11y | Observability (Web Vitals, console, HTTP, traces) | [o11y](./references/o11y.md) | | debug | Non-blocking debugging (tracepoints, logpoints, exceptions) | [debug](./references/debug.md) | | stub | HTTP mocking (intercept, mock, clear) | [stub](./references/stub.md) | | sync | Synchronization (wait for network idle) | [sync](./references/sync.md) | | react | React DevTools integration | [react](./references/react.md) | | figma | Figma design comparison | [figma](./references/figma.md) | | scenario | Reusable JS scripts (add, update, delete, list, search, run) | [scenario](./references/scenario.md) | | execute | Batch JavaScript execution (run execute; CLI and MCP) | [execute](./references/execute.md) |

Execute is available in both CLI and MCP. Use it to run JavaScript and batch tool calls: CLI run execute --code "" (or --file , optionally --timeout-ms); MCP tool execute with the same params. Inside the VM: page (browser only) — Playwright Page; use await page.title(), await page.evaluate(...), etc. callTool(name, input, returnOutput?) — invoke any tool; always await; name is underscore form (e.g. 'navigation_go-to'); input is an object (camelCase keys); returnOutput: true adds the result to the response toolOutputs. See [execute reference](./references/execute.md) for full bindings and args.

Scenarios are reusable JS scripts stored in ${WORKING_DIR}/.ironbee-devtools/scenarios.json (project) or ~/.ironbee-devtools/scenarios.json (global). They run inside the same VM as execute (with the same callTool and page bindings). See [scenario reference](./references/scenario.md).

CLI Management Commands

Daemon Management

ironbee-browser-devtools-cli daemon status      # Check daemon status
ironbee-browser-devtools-cli daemon info        # Show daemon info (version, uptime, sessions)
ironbee-browser-devtools-cli daemon start       # Start daemon
ironbee-browser-devtools-cli daemon stop        # Stop daemon
ironbee-browser-devtools-cli daemon restart     # Restart daemon

Session Management

ironbee-browser-devtools-cli session list                  # List active sessions
ironbee-browser-devtools-cli session info      # Show session details
ironbee-browser-devtools-cli session delete    # Delete a session

Tool Discovery

ironbee-browser-devtools-cli tools list              # List all available tools
ironbee-browser-devtools-cli tools search     # Search tools by name or description
ironbee-browser-devtools-cli tools info   # Show tool details and parameters

Configuration

ironbee-browser-devtools-cli config    # Show current configuration

Updates

ironbee-browser-devtools-cli update --check   # Check for updates
ironbee-browser-devtools-cli update           # Check and install updates

Examples

Basic Navigation and Screenshot

# Navigate to URL
ironbee-browser-devtools-cli navigation go-to --url "https://example.com"

# Take screenshot
ironbee-browser-devtools-cli content take-screenshot --name "homepage"

# Get page text
ironbee-browser-devtools-cli content get-as-text

Form Automation

# Use same session for state persistence
SESSION="--session-id login-test"

# Navigate to login page
ironbee-browser-devtools-cli $SESSION navigation go-to --url "https://app.example.com/login"

# Fill form fields
ironbee-browser-devtools-cli $SESSION interaction fill --selector "#email" --value "user@example.com"
ironbee-browser-devtools-cli $SESSION interaction fill --selector "#password" --value "password123"

# Submit form
ironbee-browser-devtools-cli $SESSION interaction click --selector "button[type=submit]"

# Wait for navigation
ironbee-browser-devtools-cli $SESSION sync wait-for-network-idle

# Capture result
ironbee-browser-devtools-cli $SESSION content take-screenshot --name "dashboard"

Performance Analysis

# Navigate
ironbee-browser-devtools-cli navigation go-to --url "https://example.com"

# Get Web Vitals metrics
ironbee-browser-devtools-cli --json o11y get-web-vitals

# Check console for errors
ironbee-browser-devtools-cli --json o11y get-console-messages --type warning

# Analyze HTTP requests
ironbee-browser-devtools-cli --json o11y get-http-requests

Accessibility Audit

# Navigate
ironbee-browser-devtools-cli navigation go-to --url "https://example.com"

# Get ARIA snapshot
ironbee-browser-devtools-cli a11y take-aria-snapshot

# Get detailed AX tree
ironbee-browser-devtools-cli --json a11y take-ax-tree-snapshot --roles button,link,textbox

Batch Execution (execute)

# Run JavaScript in session VM (page + callTool available)
ironbee-browser-devtools-cli run execute --code "return await page.title();"

# Batch multiple tools in one call (fewer round-trips)
ironbee-browser-devtools-cli run execute --code "await callTool('a11y_take-aria-snapshot', {}, true); await callTool('content_take-screenshot', {}, true);"

# Run script body from a file (mutually exclusive with --code)
ironbee-browser-devtools-cli run execute --file ./scripts/login-flow.js

Scenarios (reusable JS)

The scenario tools are platform-agnostic shared tools — their CLI commands live under the auto-generated default group (they have no domain prefix in their tool id). The full set (CRUD + scenario-run) is registered on all six platform CLIs (browser, node, python, backend, android, terminal). A scenario can declare an optional typed params contract (defaults + shallow validation applied by scenario-run) — see the [scenario reference](./references/scenario.md#declared-params).

# Register a scenario at the project scope
ironbee-browser-devtools-cli default scenario-add \
  --name "login-flow" \
  --description "Logs in and verifies dashboard" \
  --script "await callTool('navigation_go-to', { url: 'https://app.example.com/login' });"

# Discover available scenarios
ironbee-browser-devtools-cli default scenario-list
ironbee-browser-devtools-cli default scenario-search --query "login"

# Run a scenario directly (scenario-run is a CLI subcommand on every platform)
ironbee-browser-devtools-cli default scenario-run --name login-flow

# Parameterize: --args JSON, or repeatable --param key=value (coerced to declared param types)
ironbee-browser-devtools-cli default scenario-run --name login-flow --param email=user@example.com

Equivalent MCP tool names (all six are MCP-registered): scenario-add, scenario-update, scenario-delete, scenario-list, scenario-search, scenario-run (flat, no domain prefix).

API Mocking

# Mock API response
ironbee-browser-devtools-cli stub mock-http-response \
  --pattern "**/api/users" \
  --body '[{"id": 1, "name": "Test User"}]'

# Navigate and test
ironbee-browser-devtools-cli navigation go-to --url "https://app.example.com"

# Clear mocks
ironbee-browser-devtools-cli stub clear

Non-Blocking Debugging

SESSION="--session-id debug-session"

# Navigate to app
ironbee-browser-devtools-cli $SESSION navigation go-to --url "http://localhost:3000"

# Set tracepoint on a function
ironbee-browser-devtools-cli $SESSION debug put-tracepoint \
  --url-pattern "app.js" \
  --line-number 42

# Add watch expression
ironbee-browser-devtools-cli $SESSION debug add-watch --expression "this"

# Enable exception catching
ironbee-browser-devtools-cli $SESSION debug put-exceptionpoint --state uncaught

# Interact with app (triggers probes)
ironbee-browser-devtools-cli $SESSION interaction click --selector "#submit-btn"

# Get captured snapshots
ironbee-browser-devtools-cli $SESSION --json debug get-probe-snapshots
ironbee-browser-devtools-cli $SESSION --json debug get-probe-snapshots --types tracepoint,exceptionpoint

Shell Script for CI/CD

#!/bin/bash
set -e

CLI="ironbee-browser-devtools-cli --json --quiet --session-id ci-test-$$"

# Navigate
$CLI navigation go-to --url "https://example.com"

# Wait for load
$CLI sync wait-for-network-idle

# Take screenshot
$CLI content take-screenshot --name "ci-test"

# Get Web Vitals
VITALS=$($CLI o11y get-web-vitals)
echo "Web Vitals: $VITALS"

# Check for console errors
ERRORS=$($CLI o11y get-console-messages --type error)
if [ "$ERRORS" != "[]" ]; then
  echo "Console errors found: $ERRORS"
  exit 1
fi

# Cleanup
$CLI session delete "ci-test-$$"

Interactive Mode (Human Users)

For manual exploration, an interactive REPL mode is available:

ironbee-browser-devtools-cli interactive
ironbee-browser-devtools-cli --no-headless interactive   # With visible browser

| Command | Description | |---------|-------------| | help | Show available commands | | exit, quit | Exit interactive mode | | | Execute a tool |

Shell Completions

# Bash
ironbee-browser-devtools-cli completion bash
echo 'eval "$(ironbee-browser-devtools-cli completion bash)"' >> ~/.bashrc

# Zsh
ironbee-browser-devtools-cli completion zsh
echo 'eval "$(ironbee-browser-devtools-cli completion zsh)"' >> ~/.zshrc

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: ironbee-ai
• Source: ironbee-ai/ironbee-devtools-skills
• License: MIT
• Homepage: https://ironbee.ai/products/ironbee-devtools

Install and usage instructions live in the source repository linked above.