tabbit-devtools

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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 about how to connect

agent-browser

to Tabbit. After the connection is established, handle browser automation and inspection through the normal

agent-browser

workflow. Do not implement a parallel browser automation layer, bridge daemon, or custom CDP client inside this skill.

当请求明确涉及Tabbit，或包含类似

用我的 tabbit 浏览器

、

在 Tabbit 里

、

Tabbit 当前页

、

Tabbit 当前标签

这类表述时，请优先使用此技能。

将Tabbit视作基于Chromium的浏览器。此技能用于说明如何将

agent-browser

连接到Tabbit。连接建立后，通过常规的

agent-browser

工作流处理浏览器自动化和检查操作。请勿在此技能中实现并行浏览器自动化层、桥接守护进程或自定义CDP客户端。

agent-browser Quick Reference

Treat

agent-browser

as the browser-operation layer after Tabbit endpoint discovery.

The most relevant commands for this skill are:

```
open <url>
```
```
snapshot -i
```
```
click @e3
```
```
fill @e5 <text>
```
```
press Enter
```

Do not restate a full

agent-browser

manual here. Use these commands as the default vocabulary for Tabbit tasks, and prefer the official README for any broader command surface.

将

agent-browser

视作Tabbit端点发现后的浏览器操作层。

此技能最相关的命令如下：

```
open <url>
```
```
snapshot -i
```
```
click @e3
```
```
fill @e5 <text>
```
```
press Enter
```

请勿在此处重述完整的

agent-browser

手册。将这些命令作为Tabbit任务的默认指令集，如需更广泛的命令范围请参考官方README。

Quick Path

Read

~/Library/Application Support/Tabbit/DevToolsActivePort

first.

Use both lines in that file:
- line 1: TCP port
- line 2: browser path such as
```
/devtools/browser/<id>
```
Build the full browser endpoint as
```
ws://127.0.0.1:<port><path>
```
.
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
```
.
Prefer scripts/run_agent_browser_on_tabbit.py for actual browser actions. It injects the live
```
wsEndpoint
```
into
```
agent-browser --cdp ...
```
.
Use scripts/discover_tabbit_cdp.py when you only need structured connection facts.
Once connected, use the full normal
```
agent-browser
```
workflow for page operations.

首先读取

~/Library/Application Support/Tabbit/DevToolsActivePort

文件。

使用文件中的两行内容：
- 第1行：TCP端口
- 第2行：浏览器路径，例如
```
/devtools/browser/<id>
```
构建完整的浏览器端点：
```
ws://127.0.0.1:<port><path>
```
。
优先使用该
```
wsEndpoint
```
，而非
```
http://127.0.0.1:<port>
```
。Tabbit可能会暴露浏览器WebSocket，但
```
/json/version
```
和
```
/json/list
```
仍返回404。
实际执行浏览器操作时优先使用scripts/run_agent_browser_on_tabbit.py，它会将实时
```
wsEndpoint
```
注入到
```
agent-browser --cdp ...
```
命令中。
若仅需要结构化连接信息，请使用scripts/discover_tabbit_cdp.py。
连接成功后，使用完整的常规
```
agent-browser
```
工作流执行页面操作。

Workflow

For Tabbit requests, start by reading
```
DevToolsActivePort
```
directly or by running scripts/discover_tabbit_cdp.py.
Return the connection facts the agent actually needs:
```
activePortFile
```
,
```
port
```
,
```
browserPath
```
,
```
browserUrl
```
, and
```
wsEndpoint
```
.
Unless the user explicitly asks only for endpoint details, prefer scripts/run_agent_browser_on_tabbit.py immediately so the command becomes
```
agent-browser --cdp <wsEndpoint> ...
```
.
After that handoff, follow the normal
```
agent-browser
```
workflow for open, snapshot, click, fill, and other browser commands.
If
```
agent-browser
```
is unavailable, say so plainly and surface the connection facts instead of inventing a custom CDP bridge.

收到Tabbit相关请求时，首先直接读取
```
DevToolsActivePort
```
文件，或运行scripts/discover_tabbit_cdp.py。
返回Agent实际需要的连接信息：
```
activePortFile
```
、
```
port
```
、
```
browserPath
```
、
```
browserUrl
```
和
```
wsEndpoint
```
。
除非用户明确仅要求端点详情，否则优先立即运行scripts/run_agent_browser_on_tabbit.py，这样命令就变为
```
agent-browser --cdp <wsEndpoint> ...
```
。
交接完成后，遵循常规
```
agent-browser
```
工作流执行打开、快照、点击、填充和其他浏览器命令。
若
```
agent-browser
```
不可用，直接说明该情况并输出连接信息，不要自行开发自定义CDP桥接方案。

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.
Prefer the full
```
wsEndpoint
```
over a raw port because Tabbit may not expose HTTP discovery routes.
Once a Tabbit task has started through
```
run_agent_browser_on_tabbit.py
```
, keep using that same wrapper path for the rest of the task unless the user explicitly asks otherwise.
Once connected, use standard
```
agent-browser
```
patterns for everything else.

此技能仅解决连接问题，不解决通用浏览器操作问题。
优先返回结构化连接数据，再附上简短的说明注释。
优先使用最轻量的发现路径：
```
DevToolsActivePort
```
文件和推导得出的浏览器WebSocket端点。
优先使用完整的
```
wsEndpoint
```
而非原始端口，因为Tabbit可能不会暴露HTTP发现路由。
一旦Tabbit任务通过
```
run_agent_browser_on_tabbit.py
```
启动，后续任务都优先使用相同的封装路径，除非用户明确要求其他方式。
连接成功后，所有其他操作都使用标准
```
agent-browser
```
模式。

Constraints

Do not assume a dedicated
```
tabbit-devtools
```
MCP server exists.
Do not assume the generic
```
chrome-devtools
```
session can be retargeted to Tabbit.
Do not turn this skill into a replacement for
```
agent-browser
```
.
Do not create a custom daemon, long-lived CDP proxy, or one-off WebSocket client for post-connection browser actions.
Do not promise that
```
chrome-devtools
```
MCP will automatically take over Tabbit.
If
```
agent-browser
```
cannot be launched in the current environment, stop at connection guidance and explain the limitation.
After connection, the browser workflow belongs to
```
agent-browser
```
, not to this skill.

不要假设存在专用的
```
tabbit-devtools
```
MCP服务器。
不要假设通用
```
chrome-devtools
```
会话可以重定向到Tabbit。
不要将此技能变成
```
agent-browser
```
的替代品。
不要为连接后的浏览器操作创建自定义守护进程、长生命周期CDP代理或一次性WebSocket客户端。
不要承诺
```
chrome-devtools
```
MCP会自动接管Tabbit。
如果当前环境无法启动
```
agent-browser
```
，仅提供连接指导并说明限制即可。
连接成功后，浏览器工作流归
```
agent-browser
```
处理，不属于此技能的范畴。

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
agent-browser wrapper: scripts/run_agent_browser_on_tabbit.py
agent-browser upstream docs: https://github.com/vercel-labs/agent-browser

安装和直连说明：references/setup.md
端点发现规则和环境变量：references/discovery.md
端点发现辅助工具：scripts/discover_tabbit_cdp.py
agent-browser封装脚本：scripts/run_agent_browser_on_tabbit.py
agent-browser上游文档：https://github.com/vercel-labs/agent-browser