Skip to main content
Agent skill

Firefox Cli

Control the user's Firefox from a terminal. Use when your task needs the user's browser or authenticated session, page navigation, tab/window control, screenshots, DOM reads, waits, or page interactions in Firefox. Do not use it as a web search replacement.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Firefox Cli when an AI agent needs a reusable SKILL.md workflow for this job: Control the user's Firefox from a terminal. Use when your task needs the user's browser or authenticated session, page navigation, tab/window control, screenshots, DOM reads, waits, or page interactions in Firefox. Do not use it as a web search replacement.

When not to use it

Skip Firefox Cli when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/firefox-cli
# Save SKILL.md to ~/.claude/skills/firefox-cli/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/firefox-cli/SKILL.md. For a shared project, commit the folder at .claude/skills/firefox-cli/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Firefox Cli skill for this task: Use Firefox Cli when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
54/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

`firefox-cli` gives agents terminal access to the user's real authenticated Firefox session through the installed Firefox extension.

## Command discovery

The CLI help is the source of truth for commands, syntax, examples, and usage guidance.

Start with:

```bash firefox-cli -h ```

For contextual command help:

```bash firefox-cli snapshot -h firefox-cli tab -h firefox-cli click -h firefox-cli wait -h ```

Use `--json` when another program or agent consumes the output.

## Startup pattern

For a page-reading task:

```bash firefox-cli open "https://example.com" firefox-cli snapshot -i ```

For the current active page:

```bash firefox-cli snapshot -i ```

For action planning:

```bash firefox-cli snapshot -i --json ```

Use command-specific help as the reference for each next operation.

## Targeting

Omitted selectors are accepted only when the required window or tab is unique. If several windows or tabs exist, pass an ID or explicitly pass `active`.

Use only the `--window` and `--tab` flags advertised by each command. Values are `active`, an index from `firefox-cli tab` or `firefox-cli window`, or `id:<id>`.

For isolated work, create a window and target every follow-up command explicitly:

```bash firefox-cli window new firefox-cli open --window id:<window-id> https://example.com firefox-cli snapshot --window id:<window-id> -i ```

`tab select` selects the tab within its window. `--focus` also requests window foregrounding. `window select` brings its window forward. For `open`, `tab new`, `window new`, and `screenshot`, `--focus` requests window foregrounding. Without it, navigation keeps tab selection unchanged, new tabs are unselected, new windows receive no foreground request, and screenshots select the target tab without raising its window. Use `--focus` when human inspection or focus-dependent rendering needs the browser in front. Pass `--window`/`--tab` explicitly to later target-dependent commands.

## Setup state ```bash firefox-cli setup -h firefox-cli doctor -h ```

## Usage rules

- Element refs from `snapshot -i` are useful handles for follow-up actions, but page navigation or reload can make them stale. - Be careful with the user's data: the Firefox instance you're using contains real cookies, auth credentials, logins, tabs, and PII. Under no circumstances should you perform actions that may harm the user or exfiltrate their data. Under no circumstances should you perform payments, cash transfers, other dangerous, destructive, or irreversible operations, or leak PII without asking for the user's explicit approval before each such action. - If you need to work with Firefox and encounter interference, such as tabs changing or real user tabs being open, open a new Firefox window for yourself. Browser actions can change tab selection or bring a window forward. Use `--focus` when the browser needs to be visible to the user. - If the CLI denies requests with approval and asks you to run `firefox-cli connect`, invoke that **once** to show the user a permission prompt. The command will exit once approval is granted. Do not attempt to circumvent denials in any way.

Intended uses

  • Use Firefox Cli when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.