Record browser endpoints for mac-5 and mac-7

This commit is contained in:
hotwa
2026-03-18 14:50:23 +08:00
parent be1a2c1d50
commit 0a735c8676
2 changed files with 85 additions and 0 deletions

View File

@@ -87,3 +87,15 @@
- `mac-7` 侧优先作为独立自动化浏览器承载机,可采用 OpenClaw managed browser 或明确的 remote CDP 启动方式
-`mac-5` 要控制 `mac-7` 的浏览器,应视为远程自动化路径,而不是 `mac-5` 本机会话接管路径
- 已新增长期决策文档:`shared/long-term/decisions/browser-role-split-mac5-mac7.md`
- 当日验证结果补充:
- `mac-5` 本机 Chrome 接管(`browser profile=user` / `existing-session` / `chrome-mcp`)已测通
- `openclaw browser --browser-profile user status` 返回 `running: true`
- `openclaw browser --browser-profile user tabs` 可见当前本机标签页,说明 mac-5 本机会话接管可直接使用
- `mac-7` 自动化 Chrome LaunchAgent 已建立:`~/Library/LaunchAgents/com.lingyuzeng.chrome-cdp-mac7.plist`
- `mac-7` 持久化本地 CDP 监听端口为 `127.0.0.1:9333`
- `mac-7` 自动化 Chrome profile 路径为 `~/.openclaw/browser/mac7-automation-profile`
- `mac-7` 当前还存在一个临时 tailnet 转发监听:`100.64.0.23:9223 -> 127.0.0.1:9222`Python 代理,当前存活,但不是已确认持久化的正式入口)
- `tailscale serve` 当前未配置成功,`tailscale serve status` 显示 `No serve config`
- 因此后续引用时应区分:
- 稳定本地自动化入口:`mac-7 localhost:9333`
- 临时 tailnet 入口:`mac-7 100.64.0.23:9223`

View File

@@ -0,0 +1,73 @@
# Browser endpoints registry for mac-5 takeover and mac-7 automation
Date: 2026-03-18
Status: accepted
## Purpose
Record the currently validated browser control endpoints so future automation and browser takeover tasks can reuse the right path without re-discovering ports.
## mac-5 local intelligent browser takeover
Use OpenClaw local browser attach on mac-5 for takeover of the real local Chrome session.
### Validated profile
- OpenClaw browser profile: `user`
- Driver/transport: `existing-session` via `chrome-mcp`
### Validation result
Validated on 2026-03-18:
- `openclaw browser --browser-profile user status` returned `running: true`
- `openclaw browser --browser-profile user tabs` listed live local tabs
### Operational meaning
This is the preferred path for smart takeover of the browser running on mac-5 itself.
## mac-7 browser automation service
mac-7 hosts the dedicated automation Chrome instance.
### Persistent local CDP service
- LaunchAgent plist:
- `~/Library/LaunchAgents/com.lingyuzeng.chrome-cdp-mac7.plist`
- Chrome executable:
- `/Applications/Google Chrome.app/Contents/MacOS/Google Chrome`
- Dedicated profile dir:
- `~/.openclaw/browser/mac7-automation-profile`
- Persistent local CDP listen address:
- `127.0.0.1:9333`
- Validation:
- `http://127.0.0.1:9333/json/version` returns standard CDP metadata and `webSocketDebuggerUrl`
### Current tailnet-facing listener status
Observed on 2026-03-18:
- Tailscale IP on mac-7: `100.64.0.23`
- A temporary Python TCP proxy was listening on:
- `100.64.0.23:9223`
- That proxy was forwarding toward a Chrome debug port for network reachability testing.
### Important caveat
The `100.64.0.23:9223` listener was observed as a temporary proxy, not yet confirmed as a durable/persistent service managed by LaunchAgent or `tailscale serve`.
Also, `tailscale serve status` showed:
- `No serve config`
So future tasks should treat the endpoints as:
- **stable local automation endpoint on mac-7:** `127.0.0.1:9333`
- **temporary observed tailnet endpoint on mac-7:** `100.64.0.23:9223`
## Usage guidance
- For mac-5 intelligent browser takeover: use OpenClaw local `user` profile.
- For mac-7 automation on the same machine: use CDP on `127.0.0.1:9333`.
- For mac-5 controlling mac-7 across the tailnet, do not assume `100.64.0.23:9223` is durable unless a persistent proxy/serve configuration is explicitly installed later.