Tabbit DevTools — drive the Tabbit browser via CDP through agent-browser
⚠️ AUTHORIZED USE ONLY — connect agent-browser to the Tabbit browser: read the DevToolsActivePort file, derive the browser WebSocket endpoint, and automate tabs with the standard agent-browser workflow
- What
- ⚠️ AUTHORIZED USE ONLY — connect agent-browser to the Tabbit browser: read the DevToolsActivePort file, derive the browser WebSocket endpoint, and automate tabs with the standard agent-browser workflow
- Cost
- Free
- Needs
- the Tabbit browser installed; the agent-browser CLI available in the environment — ⚠️ AUTHORIZED USE ONLY: this skill controls a LIVE browser with your logged-in sessions; use only on your own accounts and systems
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — ⚠️ AUTHORIZED USE ONLY: this skill gives your agent full control of a LIVE browser — open tabs and logged-in sessions are visible and actionable, so use it only for your own accounts and systems, never against third parties or accounts you do not own. @tabbit-browser's tabbit-devtools skill: a connection recipe for driving the Tabbit browser (a Chromium-based browser) from an agent through the agent-browser CLI over the Chrome DevTools Protocol. The agent reads Tabbit's live DevToolsActivePort file (platform-specific paths for macOS and Windows), builds the full browser WebSocket endpoint (ws://127.0.0.1:<port><path> — preferred over the raw port because Tabbit's HTTP discovery routes may 404), hands off to agent-browser --cdp via the bundled wrapper scripts (run_agent_browser_on_tabbit.py for actions, discover_tabbit_cdp.py for structured connection facts), and then works with the normal agent-browser vocabulary (open, snapshot, click, fill, press). It states its constraints clearly: it solves the connection problem only — no parallel automation layer, no custom CDP client, no daemon, no promise that chrome-devtools MCP can take over Tabbit; if agent-browser is unavailable it stops at connection guidance. Honest caveats: this connects the agent to your LIVE browser — open tabs and logged-in sessions are visible, so grant access deliberately (anonymous-profile guidance is referenced); you need the agent-browser CLI in the environment; Tabbit-specific, not a generic Chrome tool. MIT licensed (frontmatter and manifest agree). Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Tabbit DevTools is a free connection recipe for driving the Tabbit browser, a Chromium-based browser, from an agent through the agent-browser CLI over the Chrome DevTools Protocol. The agent reads Tabbit's DevToolsActivePort file, derives the browser WebSocket endpoint, and automates tabs with the agent-browser workflow, for authorized use only, on your own accounts and systems, never against third parties.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 7a7dc81Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the Tabbit browser installed; the agent-browser CLI available in the environment — ⚠️ AUTHORIZED USE ONLY: this skill controls a LIVE browser with your logged-in sessions; use only on your own accounts and systems Install "Tabbit DevTools — drive the Tabbit browser via CDP through agent-browser" for me. It gives my agent @tabbit-browser's Tabbit connection recipe: locate the live DevToolsActivePort file for the platform, derive the browser WebSocket endpoint (ws://127.0.0.1:<port><path>), connect with agent-browser --cdp via the bundled wrapper scripts, and automate tabs with the standard agent-browser workflow (open, snapshot, click, fill, press) — honoring the constraints (connection problem only, no custom CDP client or daemon, stop at connection guidance if agent-browser is missing). MIT licensed. Repository: https://raw.githubusercontent.com/tabbit-browser/tabbit-devtools-skill/7a7dc819ae89eb4e7836f888dcde63666269b80c/skills/tabbit-devtools/SKILL.md Pinned version: install the code at commit 7a7dc819ae89eb4e7836f888dcde63666269b80c exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tabbit-devtools". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm the Tabbit install and agent-browser availability; decide whether to grant access to my live browser session or use an anonymous profile). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 7a7dc81 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.