Add browser role split decision for mac-5 and mac-7
This commit is contained in:
@@ -72,3 +72,18 @@
|
||||
- 若只是一次性、临时性、上下文强绑定的反思,则不必强行提升为长期记忆
|
||||
- 结论:self-improving 负责发现与总结,durable memory 负责沉淀长期有效规则
|
||||
- 已新增长期 lesson 文档:`shared/long-term/lessons/self-improving-memory-sync.md`
|
||||
|
||||
## 浏览器控制职责分流决策
|
||||
|
||||
- hotwa 明确确认新的稳定浏览器策略:
|
||||
- `mac-5` 主要用于接管本机真实 Chrome 会话(human-in-the-loop / signed-in session / existing-session 优先)
|
||||
- `mac-7` 主要用于自动化浏览器任务(service-like / unattended automation / browser worker)
|
||||
- 该分流的原因:
|
||||
- `mac-5 = brain` 适合本机控制与交互式接管
|
||||
- `mac-7 = eyes` 适合作为浏览器执行与验收节点
|
||||
- 不应把 `user/existing-session` 与远程 raw CDP 混成同一条默认路径
|
||||
- 实施建议:
|
||||
- `mac-5` 侧优先配置本机 `user` / `existing-session` profile,用于接管当前登录浏览器
|
||||
- `mac-7` 侧优先作为独立自动化浏览器承载机,可采用 OpenClaw managed browser 或明确的 remote CDP 启动方式
|
||||
- 若 `mac-5` 要控制 `mac-7` 的浏览器,应视为远程自动化路径,而不是 `mac-5` 本机会话接管路径
|
||||
- 已新增长期决策文档:`shared/long-term/decisions/browser-role-split-mac5-mac7.md`
|
||||
|
||||
47
shared/long-term/decisions/browser-role-split-mac5-mac7.md
Normal file
47
shared/long-term/decisions/browser-role-split-mac5-mac7.md
Normal file
@@ -0,0 +1,47 @@
|
||||
# Browser Role Split: mac-5 local session control, mac-7 automation worker
|
||||
|
||||
Date: 2026-03-18
|
||||
Status: accepted
|
||||
|
||||
## Decision
|
||||
|
||||
Use a split browser strategy in the OpenClaw cluster:
|
||||
|
||||
- **mac-5** handles attachment to the local real Chrome session for interactive, signed-in, human-in-the-loop browsing.
|
||||
- **mac-7** handles browser automation as the dedicated browser/verification worker for unattended or service-like tasks.
|
||||
|
||||
## Rationale
|
||||
|
||||
- This matches the stable machine role semantics:
|
||||
- `mac-5 = brain`
|
||||
- `mac-7 = eyes`
|
||||
- `existing-session` / `user` is best treated as a local-session attach path, not the default remote-browser path.
|
||||
- Remote browser control for automation should be modeled separately from local human session takeover.
|
||||
- This separation reduces confusion between:
|
||||
- local `existing-session` / chrome-mcp attach
|
||||
- remote raw CDP (`cdpUrl`) automation
|
||||
- OpenClaw-managed isolated browser profiles
|
||||
|
||||
## Operational guidance
|
||||
|
||||
### mac-5
|
||||
|
||||
Prefer local `user` / `existing-session` profile when the goal is to control the real browser session on mac-5 itself.
|
||||
|
||||
### mac-7
|
||||
|
||||
Prefer mac-7 as the browser automation host for:
|
||||
|
||||
- automated browsing
|
||||
- acceptance checks
|
||||
- repeatable service-like browser tasks
|
||||
- isolated or explicit remote CDP setups when needed
|
||||
|
||||
### Cross-machine rule
|
||||
|
||||
If mac-5 controls a browser running on mac-7, treat it as a **remote automation** path, not as a local-session attach path.
|
||||
|
||||
## Notes
|
||||
|
||||
- Do not conflate `existing-session` with raw CDP.
|
||||
- For unattended automation, OpenClaw-managed browser or explicit remote CDP is preferred over local-session attach semantics.
|
||||
Reference in New Issue
Block a user