Skill Tracer
Skills › Compound Engineering › ce-test-browser › agent-browser-driver.md

agent-browser-driver.md

47 lines · skills/ce-test-browser/references/agent-browser-driver.md at 3449230

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# `agent-browser` Fallback Driver
2
3Read this file only after the main skill selects `agent-browser` because no qualifying host-native integrated browser is available.
4

agent-browser Fallback Driver

Read this file only after the main skill selects agent-browser because no qualifying host-native integrated browser is available.

Raw lines 1 to 4
5## Bootstrap
6
7Verify the direct CLI is installed:
8
9```bash
10command -v agent-browser >/dev/null 2>&1 && echo "Ready" || echo "NOT INSTALLED"
11```
13If it is missing, tell the user: "`agent-browser` is not installed. Use the `ce-setup` skill to print the current install command, then install `agent-browser` and retry." Then stop. An installed discovery skill does not imply that the CLI or its browser runtime is installed.
15Before running browser actions, load the workflow and troubleshooting content that matches the installed CLI:
17```bash
18agent-browser skills get core
19```
21If the CLI exists but cannot launch its browser, follow the current core troubleshooting instructions and report the exact launch failure. Do not misreport a missing browser runtime or launch error as a missing CLI.

Bootstrap

Verify the direct CLI is installed:

command -v agent-browser >/dev/null 2>&1 && echo "Ready" || echo "NOT INSTALLED"

If it is missing, tell the user: "agent-browser is not installed. Use the ce-setup skill to print the current install command, then install agent-browser and retry." Then stop. An installed discovery skill does not imply that the CLI or its browser runtime is installed.

Before running browser actions, load the workflow and troubleshooting content that matches the installed CLI:

agent-browser skills get core

If the CLI exists but cannot launch its browser, follow the current core troubleshooting instructions and report the exact launch failure. Do not misreport a missing browser runtime or launch error as a missing CLI.

Raw lines 5 to 22
Names a skill ce-setup :13
23## Commands Used by This Skill
25Add `--headed` to commands when manual mode selected a visible browser. Pipeline mode defaults this fallback driver to headless.
27```bash
28# Navigate and inspect
29agent-browser open <url>
30agent-browser snapshot -i
32# Interact using refs from the latest snapshot
33agent-browser click @e1
34agent-browser fill @e1 "text"
35agent-browser type @e1 "text"
36agent-browser press Enter
38# Capture evidence
39agent-browser screenshot out.png
40agent-browser screenshot --full out-full.png
42# Navigation and waits
43agent-browser back
44agent-browser wait @e1
45```
47Use the installed core documentation for console-error inspection and any command not shown here. Do not switch to another browser driver after the first route is tested.

Commands Used by This Skill

Add --headed to commands when manual mode selected a visible browser. Pipeline mode defaults this fallback driver to headless.

# Navigate and inspect
agent-browser open <url>
agent-browser snapshot -i

# Interact using refs from the latest snapshot
agent-browser click @e1
agent-browser fill @e1 "text"
agent-browser type @e1 "text"
agent-browser press Enter

# Capture evidence
agent-browser screenshot out.png
agent-browser screenshot --full out-full.png

# Navigation and waits
agent-browser back
agent-browser wait @e1

Use the installed core documentation for console-error inspection and any command not shown here. Do not switch to another browser driver after the first route is tested.

Raw lines 23 to 47