Tabbit Devtools

Prefer this skill whenever the request is explicitly about Tabbit or includes phrases like 用我的 tabbit 浏览器, 在 Tabbit 里, Tabbit 当前页, or Tabbit 当前标签.

Treat Tabbit as a Chromium-based browser. This skill is only about how to connect Chrome DevTools / CDP tooling to Tabbit. After the connection is established, handle browser automation and inspection the same way you would with chrome-devtools MCP or standard CDP against any other Chromium browser. Do not treat this skill as a separate operating manual for post-connection browser actions, and do not implement a parallel browser automation layer inside this skill.

Quick Path

1. Read ~/Library/Application Support/Tabbit/DevToolsActivePort first.
2. Use both lines in that file:
   • line 1: TCP port
   • line 2: browser path such as /devtools/browser/<id>
3. Build the full browser endpoint as ws://127.0.0.1:<port><path>.
4. Prefer that wsEndpoint over http://127.0.0.1:<port>. Tabbit may expose the browser WebSocket while /json/version and /json/list still return 404.
5. Use scripts/discover_tabbit_cdp.py if you want a small helper that prints the connection details as JSON.
6. Once you have the port or wsEndpoint, point chrome-devtools MCP at Tabbit if your host supports retargeting.
7. Once connected, use the full normal chrome-devtools MCP / CDP workflow for page operations. This skill only explains how to point that workflow at Tabbit.

Workflow

1. For Tabbit requests, start by reading DevToolsActivePort directly or by running scripts/discover_tabbit_cdp.py.
2. Return the connection facts the agent actually needs: activePortFile, port, browserPath, browserUrl, and wsEndpoint.
3. If the host can repoint chrome-devtools MCP to a specific Chromium endpoint, use the discovered port or wsEndpoint to connect to Tabbit.
4. After that handoff, stop using this skill as an operation guide and follow the normal chrome-devtools MCP workflow.
5. If the host cannot retarget chrome-devtools MCP in the current environment, state that limitation clearly instead of implementing an alternate CDP client inside this skill.

Guidance

• This skill solves the connection problem, not the general browser-operation problem.
• Return structured connection data first, then any short explanatory note.
• Prefer the lightest possible discovery path: DevToolsActivePort and the derived browser WebSocket endpoint.
• Once connected, use standard Chromium / chrome-devtools MCP patterns for everything else.

Constraints

• Do not assume a dedicated tabbit-devtools MCP server exists.
• Do not assume the generic chrome-devtools session is already pointed at Tabbit.
• Do not turn this skill into a browser automation layer, a page reader, or a replacement for chrome-devtools MCP.
• Do not create a custom daemon, long-lived CDP proxy, or one-off WebSocket client for post-connection browser actions.
• Do not document page-clicking, DOM extraction, navigation recipes, or other post-connection browser tasks here.
• If the environment cannot repoint chrome-devtools MCP, stop at connection guidance and explain the limitation.
• After connection, any standard Chromium-compatible chrome-devtools MCP workflow is fair game, but that workflow belongs to chrome-devtools, not to this skill.

Resources

• Setup and direct-connection notes: references/setup.md
• Endpoint discovery rules and environment variables: references/discovery.md
• Endpoint discovery helper: scripts/discover_tabbit_cdp.py