Document per-node Warp env requirement

This commit is contained in:
hotwa
2026-03-17 19:59:30 +08:00
parent 298a77bd0e
commit 2f2d23592a
3 changed files with 13 additions and 0 deletions

View File

@@ -10,6 +10,12 @@ Primary secret file:
- `~/.openclaw/.env`
Cluster rule:
- `mac-5`, `mac-6`, and `mac-7` must each keep a local `~/.openclaw/.env` if they may locally run Warp-backed ACP harnesses.
- Do not rely on `mac-5` secrets propagating to `mac-6` / `mac-7` at runtime.
- Wrapper scripts should always read the local machine's own `~/.openclaw/.env`.
Current placeholder variables:
- `WARP_INFINI_API_KEY`

View File

@@ -7,6 +7,7 @@
- 已决定长期文档主名采用 `warp-acp-*`
- 第一阶段仅先标准化 `opencode` 的 Warp ACP 接入;后续再扩展到 `gemini cli``claude code`
- 已新增本地 secrets 文件占位:`~/.openclaw/.env`
- 已确认节点级配置规则:`mac-5``mac-6``mac-7` 三台机器都应各自本地配置 `~/.openclaw/.env`;不能假设 `mac-5` 的 secrets 会在 Warp-backed ACP harness 实际落到 `mac-6` / `mac-7` 时自动可用
- 当前预置的 provider 环境变量名:
- `WARP_INFINI_API_KEY`
- `WARP_INFINI_BASE_URL`

View File

@@ -33,6 +33,12 @@ Primary local secret file:
- `~/.openclaw/.env`
Node-local requirement:
- Any machine that may locally execute a Warp-backed ACP harness must have its own local `~/.openclaw/.env`.
- For the current cluster plan, this means `mac-5`, `mac-6`, and `mac-7` should all be configured.
- Do not assume secrets from `mac-5` will automatically be available when a harness actually runs on `mac-6` or `mac-7`.
Recommended format:
```bash