browser-control
SkillWeb & browsingControl web pages in an existing Chromium remote-debugging session with deterministic sagui commands or the browser-only AI Agent. Use when Claude Code needs to inspect tabs, observe semantic elements, navigate, click, type, send keys, scroll, or complete a browser goal through CDP without controlling native macOS UI, Accessibility, or CGEvent input.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the browser-control skill
What this skill tells your AI
The instructions your AI receives, as published by nakaokarei/swiftautogui in plugins/swift-auto-gui/skills/browser-control/SKILL.md and read by ahel’s review.
Use sagui browser to inspect and automate Chromium pages through the Chrome DevTools Protocol
(CDP). Treat this as a browser-only environment: it never falls back to native macOS automation.
Preflight
Run these checks before browser automation:
uname -s
command -v sagui
sagui browser --help
Stop if the platform is not macOS. If sagui is missing, or the installed version has no
browser command, ask before installing or upgrading it:
brew update
brew install NakaokaRei/tap/sagui
# Use this instead when sagui is already installed:
brew upgrade NakaokaRei/tap/sagui
Do not claim that Accessibility or Screen Recording permission is required for browser-only CDP
actions. Those permissions apply to native sagui commands, not sagui browser.
Connect to Chromium
List tabs on the default loopback endpoint:
sagui browser tabs
If no debugging endpoint is available, ask the user to start a dedicated Chromium profile, or obtain approval before launching it:
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \
--remote-debugging-address=127.0.0.1 \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/swift-auto-gui-browser-profile
Keep the endpoint on loopback. Do not expose or connect CDP to a LAN or public address. The browser session does not launch Chromium, manage profiles, bypass login, solve CAPTCHA, or handle 2FA.
Use the target ID printed by sagui browser tabs when a specific tab matters. Re-list tabs after a
tab closes, opens, or navigates unexpectedly because target IDs and page observations may become
stale.
Choose the domain allowlist
Build the narrowest allowlist that satisfies the user's stated goal:
github.compermits exactlygithub.com.'*.github.com'permits subdomains but not the parent domain; quote wildcards in the shell.- Repeat
--domainfor multiple hosts. - Never use a global wildcard, a public suffix such as
com, or unrelated domains. - Ask before adding a domain that is not clearly implied by the goal.
An allowlist entry only makes a destination eligible. Cross-origin navigation is still denied
unless --allow-cross-origin is present. Use that flag only when the goal requires navigation from
another origin, such as from chrome://newtab/ to an allowed website. It never permits navigation
outside the allowlist. Downloads remain denied.
Use deterministic commands
Prefer direct commands when the requested action is known. They do not call the OpenAI API and do
not require OPENAI_API_KEY.
First list tabs and observe the intended tab:
sagui browser tabs
sagui browser observe --tab-id TARGET_ID
sagui browser observe --tab-id TARGET_ID --screenshot /tmp/page.jpg
The observation prints actionable elements as [#N] role "name". Select elements by exact
--role and --name. When multiple current elements share both values, also pass the observed
--element-id; the command verifies all three values against a fresh observation before acting.
sagui browser click \
--tab-id TARGET_ID \
--role link \
--name "Issues" \
--domain github.com \
--allow-cross-origin
sagui browser set-value "SwiftAutoGUI" \
--tab-id TARGET_ID \
--role searchbox \
--name "Search"
Other deterministic commands:
sagui browser activate-tab TARGET_ID
sagui browser open "https://github.com/NakaokaRei/SwiftAutoGUI/issues" \
--tab-id TARGET_ID \
--domain github.com \
--allow-cross-origin
sagui browser type "additional text" --tab-id TARGET_ID
sagui browser key command a --tab-id TARGET_ID
sagui browser key return --tab-id TARGET_ID
sagui browser scroll --vertical -5 --tab-id TARGET_ID
sagui browser scroll --horizontal 3 --tab-id TARGET_ID
| Command | Purpose | Required selection |
|---|---|---|
tabs | List page targets | None |
observe | Print tabs and semantic elements | --tab-id |
activate-tab | Activate a page target | positional target ID |
open | Navigate to an allowed HTTP(S) URL | URL, --tab-id, --domain |
click | Click a freshly verified semantic element | --tab-id, --role, --name |
set-value | Replace an editable element value | value, --tab-id, --role, --name |
type | Insert text into the focused element | text, --tab-id |
key | Send a key or shortcut | keys, --tab-id |
scroll | Scroll the page | non-zero axis, --tab-id |
After navigation, click, typing, keys, or scrolling, use the updated semantic map printed by the
command. Do not reuse an old element ID after the page changes. Prefer set-value over type when
the target textbox is known because set-value focuses and verifies the semantic element first.
Handle the OpenAI API key
The Agent uses the OpenAI API. Prefer OPENAI_API_KEY; never print the value, request it in chat, or
put it in a command with --api-key, where it may enter shell history or process listings.
Check only whether the variable exists:
if [ -n "${OPENAI_API_KEY:-}" ]; then
echo "OPENAI_API_KEY is configured"
else
echo "OPENAI_API_KEY is not configured"
fi
If it is absent, ask the user to configure it securely in their shell and stop until they confirm.
Run a browser-only Agent
First list tabs, then run a narrowly scoped goal:
sagui browser tabs
sagui browser agent \
"Open issue 118 in the NakaokaRei/SwiftAutoGUI repository" \
--domain github.com \
--domain '*.github.com' \
--allow-cross-origin \
--tab-id TARGET_ID
Omit --tab-id when the current active page is the intended starting point. Useful optional
controls include:
--endpoint http://127.0.0.1:9222
--model gpt-5.6-sol
--reasoning-effort low
--max-iterations 20
--delay 1.0
--vision-mode automatic
Use automatic as the normal vision mode. The Agent primarily observes semantic DOM and
Accessibility data and re-observes after navigation, DOM changes, stale elements, or action
failures.
Before goals that submit forms, publish content, purchase items, change permissions, delete data, or otherwise have meaningful external effects, confirm the final consequential action with the user unless their request already authorized it explicitly.
Interpret results
unsupportedAction: The model requested a native-only action. Do not retry it through mouse or keyboard fallback.staleElement: The DOM node, frame, loader, or tab changed. List tabs or run a fresh Agent step; never click an old coordinate.navigationNotAllowed: Add the exact destination host only if it belongs to the user's goal.authorizationDenied: Cross-origin navigation needs explicit--allow-cross-originapproval.disconnected: Chromium exited or its debugging endpoint closed.
Treat Completed: true as the Agent's completion report, then verify any important result from its
printed actions or by listing/observing the relevant tab again.
Native macOS boundary
This Skill controls page content only. It cannot operate Chromium window chrome, permission
dialogs, file pickers implemented as native macOS UI, Finder, System Settings, or other apps. For
those tasks, use the separate macos-control Skill in a distinct phase. Do not represent the two
backends as one Agent run and do not silently fall back from CDP to Accessibility or CGEvent.
Signals
- GitHub stars
- 93
- Forks
- 10
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
browser-control- Source
- github.com/nakaokarei/swiftautogui