Actionbook

When to Use This Skill

Activate when the user:

• Needs to do anything on a website ("Send a LinkedIn message", "Book an Airbnb", "Search Google for...")
• Asks how to interact with a site ("How do I post a tweet?", "How to apply on LinkedIn?")
• Wants to fill out forms, click buttons, navigate, search, filter, or browse on a specific site
• Wants to take a screenshot of a web page or monitor changes
• Builds browser-based AI agents, web scrapers, or E2E tests for external websites
• Automates repetitive web tasks (data entry, form submission, content posting)
• Needs to operate multiple websites or tabs concurrently

How It Works

Actionbook provides up-to-date action manuals for the modern web. Action manuals tell agents exactly what to do on a page, no parsing, no guessing.

Why this matters:

• 10x faster, action manuals provide selectors and page structure upfront. No snapshot-per-step loop needed.
• Accurate, handles SPAs, streaming components, dropdowns, date pickers, and dynamic content reliably.
• Concurrent, stateless architecture with explicit --session/--tab. Operate dozens of tabs in parallel.

The workflow:

1. Start a browser session
2. Navigate to the target page
3. Snapshot to get the page structure with element refs
4. Automate using refs from the snapshot

Run actionbook <command> --help for full usage and examples of any command.

Browser Automation

Every browser command is stateless, pass --session and --tab explicitly. No "current tab", you can run commands on any session/tab in parallel.

Start a session

actionbook browser start --set-session-id s1

Both --session and --set-session-id are get-or-create: they reuse a Running session with the given ID, or create one if not found. If --profile is passed and does not match the session's bound profile, the command fails with SESSION_PROFILE_MISMATCH.

Core workflow: snapshot, act, wait