Agent skill

BrowserWing Executor API

by MemTensor in MemTensor/MemOS

Controls a browser through BrowserWing's local HTTP API: navigation, clicks, typing, data extraction, accessibility snapshots, screenshots and batch operations.

Apache-2.0Auto-check passedProductivity & Automation

Install BrowserWing Executor API

skills CLI
$ npx skills add MemTensor/MemOS --skill browserwing-executor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MemTensor/MemOS browserwing-executor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MemTensor/MemOS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/memos-local-openclaw/skill/browserwing-executor .claude/skills/browserwing-executor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
browserwing-executor
GitHub stars
12k
Used in
2 other repos
Token cost
~3.9k tokens
SKILL.md length
1,313 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Controls a browser through BrowserWing's local HTTP API: navigation, clicks, typing, data extraction, accessibility snapshots, screenshots and batch operations.

  • Works in 3 steps: Discover Available Commands → Get Accessibility Snapshot → Common Operations
  • Automating a multi-step task in a web page through HTTP calls
  • SKILL.md covers Overview, Core Capabilities, API Endpoints and Instructions, plus 12 more sections
  • Calls curl

What it does

The agent talks to a BrowserWing Executor server on localhost, authenticating with an API key header or a bearer token. It is told to call the help endpoint first to see every command and its parameters, and to take an accessibility snapshot after each navigation. The snapshot lists clickable and input elements with stable reference IDs such as @e1, which later calls use as identifiers, and it is described as cleaner for language models than raw DOM.

Core operations are page navigation including back, forward and reload, element interaction such as click, type, select and hover, extracting text, attributes and values, screenshots, JavaScript execution, keyboard input and running several operations in sequence as a batch. The examples are curl calls to endpoints such as navigate and click, each with a small JSON body.

When your agent uses it

  • Automating a multi-step task in a web page through HTTP calls
  • Extracting text or attributes from specific page elements
  • Understanding a page's interactive elements through an accessibility snapshot
  • Taking screenshots or running JavaScript in a controlled browser session

Example prompts

  • “Open the login page, take a snapshot and fill in the email field.”
  • “Extract the table of prices from the current page and show me the values.”
  • “Go to the pricing page, click the annual toggle and take a screenshot.”

Requirements

  • A running BrowserWing Executor server
  • An API key or bearer token for its HTTP API

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Discover Available Commands
  2. Get Accessibility Snapshot
  3. Common Operations

What it can do on your machine

Read from SKILL.md and the folder at commit a7367d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

BrowserWing Executor API loads about 3.9k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 1,313 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MemTensor/MemOS at commit a7367d0, republished under its Apache-2.0 licence (© MemTensor). 1,313 words, ~3,907 tokens.

Download SKILL.mdSave it as .claude/skills/browserwing-executor/SKILL.md (or your agent's skills folder).
name
browserwing-executor
description
Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.

BrowserWing Executor API

Overview

BrowserWing Executor provides comprehensive browser automation capabilities through HTTP APIs. You can control browser navigation, interact with page elements, extract data, and analyze page structure.

API Base URL: http://localhost:8080/api/v1/executor

Authentication: Use X-BrowserWing-Key: <api-key> header or Authorization: Bearer <token>

Core Capabilities

  • Page Navigation: Navigate to URLs, go back/forward, reload
  • Element Interaction: Click, type, select, hover on page elements
  • Data Extraction: Extract text, attributes, values from elements
  • Accessibility Analysis: Get accessibility snapshot to understand page structure
  • Advanced Operations: Screenshot, JavaScript execution, keyboard input
  • Batch Processing: Execute multiple operations in sequence

API Endpoints

1. Discover Available Commands

IMPORTANT: Always call this endpoint first to see all available commands and their parameters.

bash
curl -X GET 'http://localhost:8080/api/v1/executor/help'

Response: Returns complete list of all commands with parameters, examples, and usage guidelines.

Query specific command:

bash
curl -X GET 'http://localhost:8080/api/v1/executor/help?command=extract'
2. Get Accessibility Snapshot

CRITICAL: Always call this after navigation to understand page structure and get element RefIDs.

bash
curl -X GET 'http://localhost:8080/api/v1/executor/snapshot'

Response Example:

json
{
  "success": true,
  "snapshot_text": "Clickable Elements:\n  @e1 Login (role: button)\n  @e2 Sign Up (role: link)\n\nInput Elements:\n  @e3 Email (role: textbox) [placeholder: your@email.com]\n  @e4 Password (role: textbox)"
}

Use Cases:

  • Understand what interactive elements are on the page
  • Get element RefIDs (@e1, @e2, etc.) for precise identification
  • See element labels, roles, and attributes
  • The accessibility tree is cleaner than raw DOM and better for LLMs
  • RefIDs are stable references that work reliably across page changes
3. Common Operations
Navigate to URL
bash
curl -X POST 'http://localhost:8080/api/v1/executor/navigate' \
  -H 'Content-Type: application/json' \
  -d '{"url": "https://example.com"}'
Click Element
bash
curl -X POST 'http://localhost:8080/api/v1/executor/click' \
  -H 'Content-Type: application/json' \
  -d '{"identifier": "@e1"}'

Identifier formats:

  • RefID (Recommended): @e1, @e2 (from snapshot)
  • CSS Selector: #button-id, .class-name
  • XPath: //button[@type='submit']
  • Text: Login (text content)
Type Text
bash
curl -X POST 'http://localhost:8080/api/v1/executor/type' \
  -H 'Content-Type: application/json' \
  -d '{"identifier": "@e3", "text": "user@example.com"}'
Extract Data
bash
curl -X POST 'http://localhost:8080/api/v1/executor/extract' \
  -H 'Content-Type: application/json' \
  -d '{
    "selector": ".product-item",
    "fields": ["text", "href"],
    "multiple": true
  }'
Wait for Element
bash
curl -X POST 'http://localhost:8080/api/v1/executor/wait' \
  -H 'Content-Type: application/json' \
  -d '{"identifier": ".loading", "state": "hidden", "timeout": 10}'
Batch Operations
bash
curl -X POST 'http://localhost:8080/api/v1/executor/batch' \
  -H 'Content-Type: application/json' \
  -d '{
    "operations": [
      {"type": "navigate", "params": {"url": "https://example.com"}, "stop_on_error": true},
      {"type": "click", "params": {"identifier": "@e1"}, "stop_on_error": true},
      {"type": "type", "params": {"identifier": "@e3", "text": "query"}, "stop_on_error": true}
    ]
  }'

Instructions

Step-by-step workflow:

  1. Discover commands: Call GET /help to see all available operations and their parameters (do this first if unsure).

  2. Navigate: Use POST /navigate to open the target webpage.

  3. Analyze page: Call GET /snapshot to understand page structure and get element RefIDs.

  4. Interact: Use element RefIDs (like @e1, @e2) or CSS selectors to:

    • Click elements: POST /click
    • Input text: POST /type
    • Select options: POST /select
    • Wait for elements: POST /wait
  5. Extract data: Use POST /extract to get information from the page.

  6. Present results: Format and show extracted data to the user.

Complete Example

User Request: "Search for 'laptop' on example.com and get the first 5 results"

Your Actions:

  1. Navigate to search page:
bash
curl -X POST 'http://localhost:8080/api/v1/executor/navigate' \
  -H 'Content-Type: application/json' \
  -d '{"url": "https://example.com/search"}'
  1. Get page structure to find search input:
bash
curl -X GET 'http://localhost:8080/api/v1/executor/snapshot'

Response shows: @e3 Search (role: textbox) [placeholder: Search...]

  1. Type search query:
bash
curl -X POST 'http://localhost:8080/api/v1/executor/type' \
  -H 'Content-Type: application/json' \
  -d '{"identifier": "@e3", "text": "laptop"}'
  1. Press Enter to submit:
bash
curl -X POST 'http://localhost:8080/api/v1/executor/press-key' \
  -H 'Content-Type: application/json' \
  -d '{"key": "Enter"}'
  1. Wait for results to load:
bash
curl -X POST 'http://localhost:8080/api/v1/executor/wait' \
  -H 'Content-Type: application/json' \
  -d '{"identifier": ".search-results", "state": "visible", "timeout": 10}'
  1. Extract search results:
bash
curl -X POST 'http://localhost:8080/api/v1/executor/extract' \
  -H 'Content-Type: application/json' \
  -d '{
    "selector": ".result-item",
    "fields": ["text", "href"],
    "multiple": true
  }'
  1. Present the extracted data:
Found 15 results for 'laptop':
1. Gaming Laptop - $1299 (https://...)
2. Business Laptop - $899 (https://...)
...

Key Commands Reference

Navigation
  • POST /navigate - Navigate to URL
  • POST /go-back - Go back in history
  • POST /go-forward - Go forward in history
  • POST /reload - Reload current page
Element Interaction
  • POST /click - Click element (supports: RefID @e1, CSS selector, XPath, text content)
  • POST /type - Type text into input (supports: RefID @e3, CSS selector, XPath)
  • POST /select - Select dropdown option
  • POST /hover - Hover over element
  • POST /wait - Wait for element state (visible, hidden, enabled)
  • POST /press-key - Press keyboard key (Enter, Tab, Ctrl+S, etc.)
Data Extraction
  • POST /extract - Extract data from elements (supports multiple elements, custom fields)
  • POST /get-text - Get element text content
  • POST /get-value - Get input element value
  • GET /page-info - Get page URL and title
  • GET /page-text - Get all page text
  • GET /page-content - Get full HTML
Page Analysis
  • GET /snapshot - Get accessibility snapshot (⭐ ALWAYS call after navigation)
  • GET /clickable-elements - Get all clickable elements
  • GET /input-elements - Get all input elements
Advanced
  • POST /screenshot - Take page screenshot (base64 encoded)
  • POST /evaluate - Execute JavaScript code
  • POST /batch - Execute multiple operations in sequence
  • POST /scroll-to-bottom - Scroll to page bottom
  • POST /resize - Resize browser window
  • POST /tabs - Manage browser tabs (list, new, switch, close)
  • POST /fill-form - Intelligently fill multiple form fields at once
Debug & Monitoring
  • GET /console-messages - Get browser console messages (logs, warnings, errors)
  • GET /network-requests - Get network requests made by the page
  • POST /handle-dialog - Configure JavaScript dialog (alert, confirm, prompt) handling
  • POST /file-upload - Upload files to input elements
  • POST /drag - Drag and drop elements
  • POST /close-page - Close the current page/tab

Element Identification

You can identify elements using:

  1. RefID (Recommended): @e1, @e2, @e3

    • Most reliable method - stable across page changes
    • Get RefIDs from /snapshot endpoint
    • Valid for 5 minutes after snapshot
    • Example: "identifier": "@e1"
    • Works with multi-strategy fallback for robustness
  2. CSS Selector: #id, .class, button[type="submit"]

    • Standard CSS selectors
    • Example: "identifier": "#login-button"
  3. XPath: //button[@id='login'], //a[contains(text(), 'Submit')]

    • XPath expressions for complex queries
    • Example: "identifier": "//button[@id='login']"
  4. Text Content: Login, Sign Up, Submit

    • Searches buttons and links with matching text
    • Example: "identifier": "Login"
  5. ARIA Label: Elements with aria-label attribute

    • Automatically searched
Show full SKILL.md (589 more words)Show less

Guidelines

Before starting:

  • Call GET /help if you're unsure about available commands or their parameters
  • Ensure browser is started (if not, it will auto-start on first operation)

During automation:

  • Always call /snapshot after navigation to get page structure and RefIDs
  • Prefer RefIDs (like @e1) over CSS selectors for reliability and stability
  • Re-snapshot after page changes to get updated RefIDs
  • Use /wait for dynamic content that loads asynchronously
  • Check element states before interaction (visible, enabled)
  • Use /batch for multiple sequential operations to improve efficiency

Error handling:

  • If operation fails, check element identifier and try different format
  • For timeout errors, increase timeout value
  • If element not found, call /snapshot again to refresh page structure
  • Explain errors clearly to user with suggested solutions

Data extraction:

  • Use fields parameter to specify what to extract: ["text", "href", "src"]
  • Set multiple: true to extract from multiple elements
  • Format extracted data in a readable way for user

Complete Workflow Example

Scenario: User wants to login to a website

User: "Please log in to example.com with username 'john' and password 'secret123'"

Your Actions:

Step 1: Navigate to login page

bash
POST http://localhost:8080/api/v1/executor/navigate
{"url": "https://example.com/login"}

Step 2: Get page structure

bash
GET http://localhost:8080/api/v1/executor/snapshot

Response:

Clickable Elements:
  @e1 Login (role: button)

Input Elements:
  @e2 Username (role: textbox)
  @e3 Password (role: textbox)

Step 3: Enter username

bash
POST http://localhost:8080/api/v1/executor/type
{"identifier": "@e2", "text": "john"}

Step 4: Enter password

bash
POST http://localhost:8080/api/v1/executor/type
{"identifier": "@e3", "text": "secret123"}

Step 5: Click login button

bash
POST http://localhost:8080/api/v1/executor/click
{"identifier": "@e1"}

Step 6: Wait for login success (optional)

bash
POST http://localhost:8080/api/v1/executor/wait
{"identifier": ".welcome-message", "state": "visible", "timeout": 10}

Step 7: Inform user

"Successfully logged in to example.com!"

Batch Operation Example

Scenario: Fill out a form with multiple fields

Instead of making 5 separate API calls, use one batch operation:

bash
curl -X POST 'http://localhost:8080/api/v1/executor/batch' \
  -H 'Content-Type: application/json' \
  -d '{
    "operations": [
      {
        "type": "navigate",
        "params": {"url": "https://example.com/form"},
        "stop_on_error": true
      },
      {
        "type": "type",
        "params": {"identifier": "#name", "text": "John Doe"},
        "stop_on_error": true
      },
      {
        "type": "type",
        "params": {"identifier": "#email", "text": "john@example.com"},
        "stop_on_error": true
      },
      {
        "type": "select",
        "params": {"identifier": "#country", "value": "United States"},
        "stop_on_error": true
      },
      {
        "type": "click",
        "params": {"identifier": "#submit"},
        "stop_on_error": true
      }
    ]
  }'

Best Practices

  1. Discovery first: If unsure, call /help or /help?command=<name> to learn about commands
  2. Structure first: Always call /snapshot after navigation to understand the page
  3. Use accessibility indices: They're more reliable than CSS selectors (elements might have dynamic classes)
  4. Wait for dynamic content: Use /wait before interacting with elements that load asynchronously
  5. Batch when possible: Use /batch for multiple sequential operations
  6. Handle errors gracefully: Provide clear explanations and suggestions when operations fail
  7. Verify results: After operations, check if desired outcome was achieved

Common Scenarios

Form Filling
  1. Navigate to form page
  2. Get accessibility snapshot to find input elements and their RefIDs
  3. Use /type for each field: @e1, @e2, etc.
  4. Use /select for dropdowns
  5. Click submit button using its RefID
Data Scraping
  1. Navigate to target page
  2. Wait for content to load with /wait
  3. Use /extract with CSS selector and multiple: true
  4. Specify fields to extract: ["text", "href", "src"]
Search Operations
  1. Navigate to search page
  2. Get accessibility snapshot to locate search input
  3. Type search query into input
  4. Press Enter or click search button
  5. Wait for results
  6. Extract results data
Login Automation
  1. Navigate to login page
  2. Get accessibility snapshot to find RefIDs
  3. Type username: @e2
  4. Type password: @e3
  5. Click login button: @e1
  6. Wait for success indicator

Important Notes

  • Browser must be running (it will auto-start on first operation if needed)
  • Operations are executed on the currently active browser tab
  • Accessibility snapshot updates after each navigation and click operation
  • All timeouts are in seconds
  • Use wait_visible: true (default) for reliable element interaction
  • Replace localhost:8080 with actual API host address
  • Authentication required: use X-BrowserWing-Key header or JWT token

Troubleshooting

Element not found:

  • Call /snapshot to see available elements
  • Try different identifier format (accessibility index, CSS selector, text)
  • Check if page has finished loading

Timeout errors:

  • Increase timeout value in request
  • Check if element actually appears on page
  • Use /wait with appropriate state before interaction

Extraction returns empty:

  • Verify CSS selector matches target elements
  • Check if content has loaded (use /wait first)
  • Try different extraction fields or type

Quick Reference

bash
# Discover commands
GET localhost:8080/api/v1/executor/help

# Navigate
POST localhost:8080/api/v1/executor/navigate {"url": "..."}

# Get page structure
GET localhost:8080/api/v1/executor/snapshot

# Click element
POST localhost:8080/api/v1/executor/click {"identifier": "@e1"}

# Type text
POST localhost:8080/api/v1/executor/type {"identifier": "@e3", "text": "..."}

# Extract data
POST localhost:8080/api/v1/executor/extract {"selector": "...", "fields": [...], "multiple": true}

Response Format

All operations return:

json
{
  "success": true,
  "message": "Operation description",
  "timestamp": "2026-01-15T10:30:00Z",
  "data": {
    // Operation-specific data
  }
}

Error response:

json
{
  "error": "error.operationFailed",
  "detail": "Detailed error message"
}

© MemTensor, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in apps/memos-local-openclaw/skill/browserwing-executor of MemTensor/MemOS.

Open the folder on GitHubat commit a7367d0

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in MemTensor/MemOS, which our catalogue first saw on October 7, 2026.

Compare with similar skills

BrowserWing Executor API next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

BrowserWing Executor API compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
BrowserWing Executor API this skillMemTensor/MemOS12k2 repos~3.9kAutomated safety check: PassApache-2.0
Core Guide for agent-browservercel-labs/agent-browser44k4 repos~9.5kAutomated safety check: PassApache-2.0
OpenCLI Browser Controljackwener/OpenCLI30k2 repos~7.3kAutomated safety check: PassApache-2.0
Cloudflare Browser Renderingcloudflare/moltworker9.9k—~742Automated safety check: PassApache-2.0
Browser Control with Omowrightcode-yeongyu/oh-my-openagent70k—~2.2kAutomated safety check: PassCustom licence
Skyvern Browser AutomationSkyvern-AI/skyvern23k—~2.9kAutomated safety check: PassAGPL-3.0

Similar skills

  • Core Guide for agent-browser

    vercel-labs/agent-browser

    Official

    Core usage guide for the agent-browser CLI: the snapshot-and-ref workflow for navigating, clicking, filling forms, extracting data and running parallel sessions.

    44k GitHub starsUsed in 4 repos~9.5k tokens
    Productivity & AutomationAuto-check passed
  • OpenCLI Browser Control

    jackwener/OpenCLI

    Drives a real Chrome window through the opencli CLI to inspect pages, fill forms, click through logged-in flows and extract data from structured command responses.

    30k GitHub starsUsed in 2 repos~7.3k tokens
    Productivity & AutomationAuto-check passed
  • Cloudflare Browser Rendering

    cloudflare/moltworker

    Official

    Drives headless Chrome through Cloudflare Browser Rendering over a CDP WebSocket to take screenshots, navigate and scrape pages, and record multi-page videos.

    9.9k GitHub stars~742 tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check passed
  • Browser Control with Omowright

    code-yeongyu/oh-my-openagent

    Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.

    70k GitHub stars~2.2k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Skyvern Browser Automation

    Skyvern-AI/skyvern

    Picks the right Skyvern CLI command for a web task, from quick yes/no checks to reusable multi-page workflows, instead of falling back to plain page fetching.

    23k GitHub stars~2.9k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Agent Browser

    nanocoai/nanoclaw

    Drives a web browser from the shell with the agent-browser CLI: open pages, read an element snapshot, click and fill by reference, grab text and screenshots.

    31k GitHub starsUsed in 3 repos~1.6k tokens
    Productivity & AutomationAuto-check passed

More from MemTensor/MemOS

  • Dev Browser Automation

    MemTensor/MemOS

    Automates a real browser through short TypeScript scripts that keep page state between runs, for navigating, filling forms, taking screenshots and extracting data.

    12k GitHub starsUsed in 3 repos~1.7k tokens
    Auto-check passed
  • Ask User Question

    MemTensor/MemOS

    Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.

    12k GitHub stars~1k tokensUpdated 8 days ago
    Auto-check passed
  • BrowserWing Admin

    MemTensor/MemOS

    Installs, configures and operates BrowserWing, a browser automation platform, covering Chrome setup, LLM provider configuration, and creating or running automation scripts.

    12k GitHub stars~4.1k tokensUpdated 8 days ago
    Auto-check: notes
  • Safe File Deletion

    MemTensor/MemOS

    Enforces explicit user permission before any file deletion. Activates when you're about to use rm, unlink, fs.rm, or any operation that removes files from…

    12k GitHub stars~291 tokensUpdated 8 days ago
    Auto-check passed
  • Explains when to call MemOS's own memory tools to search past conversations, after the automatic per-turn recall hook comes up empty.

    12k GitHub stars~3.5k tokensUpdated 8 days ago
    Auto-check: warnings

Questions about BrowserWing Executor API

What does BrowserWing Executor API do?

Controls a browser through BrowserWing's local HTTP API: navigation, clicks, typing, data extraction, accessibility snapshots, screenshots and batch operations. The agent talks to a BrowserWing Executor server on localhost, authenticating with an API key header or a bearer token. It is told to call the help endpoint first to see every command and its parameters, and to take an accessibility snapshot after each navigation.

When should I use BrowserWing Executor API?

BrowserWing Executor API fits situations like: automating a multi-step task in a web page through HTTP calls; extracting text or attributes from specific page elements; understanding a page's interactive elements through an accessibility snapshot; taking screenshots or running JavaScript in a controlled browser session.

How do I install BrowserWing Executor API in Claude Code?

Run `npx skills add MemTensor/MemOS --skill browserwing-executor -a claude-code`. Or copy the skill folder (apps/memos-local-openclaw/skill/browserwing-executor in MemTensor/MemOS) into .claude/skills/browserwing-executor in your project. Claude Code loads it when a task matches its description.

How do I install BrowserWing Executor API in Codex?

Run `npx skills add MemTensor/MemOS --skill browserwing-executor -a codex`. Or copy the skill folder (apps/memos-local-openclaw/skill/browserwing-executor in MemTensor/MemOS) into .agents/skills/browserwing-executor in your project. Codex loads it when a task matches its description.

Can I use BrowserWing Executor API in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MemTensor/MemOS --skill browserwing-executor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browserwing-executor, .gemini/skills/browserwing-executor, .github/skills/browserwing-executor and .opencode/skills/browserwing-executor in your project.

What does BrowserWing Executor API need to run?

Going by SKILL.md and its folder, BrowserWing Executor API needs the command-line tools its instructions call (curl). Our summary lists: A running BrowserWing Executor server; An API key or bearer token for its HTTP API.

Does BrowserWing Executor API access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is BrowserWing Executor API safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does BrowserWing Executor API use?

BrowserWing Executor API is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does BrowserWing Executor API use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to BrowserWing Executor API?

Skills that share tags, products or a category with BrowserWing Executor API: Core Guide for agent-browser (vercel-labs/agent-browser, 44k stars), OpenCLI Browser Control (jackwener/OpenCLI, 30k stars), Cloudflare Browser Rendering (cloudflare/moltworker, 9.9k stars) and Browser Control with Omowright (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains BrowserWing Executor API?

MemTensor (a GitHub organization) maintains it in MemTensor/MemOS, which has 11,738 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 29, 2026.

Source: MemTensor/MemOS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.