chore(org): rename Architect codename from Aurelius to Helix
This commit is contained in:
Chen Gu
@@ -0,0 +1,178 @@
|
||||
# CAPABILITY_AUDIT.md
|
||||
|
||||
Last updated: 2026-03-08 (Asia/Shanghai)
|
||||
Scope: **Current subagent practical abilities** in this OpenClaw instance (session-level, tool-level, policy-level).
|
||||
|
||||
## 1) Executive Summary (Practical)
|
||||
|
||||
This subagent can reliably:
|
||||
- perform web research (`web_search`, `web_fetch`),
|
||||
- automate browser workflows (`browser`),
|
||||
- read/write/edit workspace files (`read`, `write`, `edit`),
|
||||
- run local shell commands (`exec`, `process`),
|
||||
- produce documentation/artifacts,
|
||||
- interact with paired devices if available (`nodes`),
|
||||
- send outbound messages only via explicit tool actions (`message`),
|
||||
- generate speech (`tts`) when needed.
|
||||
|
||||
This subagent cannot:
|
||||
- bypass tool/policy guardrails,
|
||||
- guarantee access to external services without credentials/network,
|
||||
- assume paired nodes exist,
|
||||
- perform hidden background persistence on its own.
|
||||
|
||||
---
|
||||
|
||||
## 2) Available Tools by Category
|
||||
|
||||
## A. Filesystem & Content
|
||||
- `read`: read file/image content.
|
||||
- `write`: create/overwrite files.
|
||||
- `edit`: exact-text surgical edits.
|
||||
|
||||
**Testable check**
|
||||
1. `write` temp file with known text.
|
||||
2. `read` file and verify exact content.
|
||||
3. `edit` one token and verify diff.
|
||||
|
||||
## B. Local Execution
|
||||
- `exec`: run shell commands (foreground/background, PTY optional).
|
||||
- `process`: inspect/poll/kill ongoing exec sessions.
|
||||
|
||||
**Testable check**
|
||||
1. Run `exec: echo ok`.
|
||||
2. Run long command in background.
|
||||
3. Use `process poll/log/kill` to verify lifecycle control.
|
||||
|
||||
## C. Web & Research
|
||||
- `web_search`: Brave-based web search (localized/region filters).
|
||||
- `web_fetch`: fetch readable page content (markdown/text extraction).
|
||||
|
||||
**Testable check**
|
||||
1. Search a query with top 3 results.
|
||||
2. Fetch 1 result URL and verify extract is non-empty.
|
||||
3. Cross-check claim against at least 2 sources.
|
||||
|
||||
## D. Browser Automation
|
||||
- `browser`: open/navigate/snapshot/act/screenshot/pdf/upload/dialog.
|
||||
|
||||
**Testable check**
|
||||
1. Open target URL.
|
||||
2. Snapshot and click/fill one element via ref.
|
||||
3. Capture screenshot as evidence.
|
||||
|
||||
## E. Device / Node Operations
|
||||
- `nodes`: status/describe/notify/camera/screen/location/run/invoke.
|
||||
- `canvas`: UI rendering/snapshot/eval for node canvas surfaces.
|
||||
|
||||
**Testable check**
|
||||
1. `nodes status` lists paired node(s).
|
||||
2. Send one notification.
|
||||
3. If permitted, capture one camera snap/screen record.
|
||||
|
||||
## F. Messaging & Voice
|
||||
- `message`: send outbound messages via configured channel plugin.
|
||||
- `tts`: convert text to speech (audio returned by tool).
|
||||
|
||||
**Testable check**
|
||||
1. Send a test message to controlled channel.
|
||||
2. Generate TTS clip from fixed sentence.
|
||||
|
||||
## G. Orchestration
|
||||
- `subagents`: list/steer/kill sub-agents.
|
||||
|
||||
**Testable check**
|
||||
1. `subagents list` returns active runs.
|
||||
2. steer/kill only with explicit operator intent.
|
||||
|
||||
---
|
||||
|
||||
## 3) Current Limitations (Concrete)
|
||||
|
||||
1. **Policy-bounded toolset only**
|
||||
- No direct access beyond listed tools.
|
||||
- No arbitrary privileged system APIs outside tools.
|
||||
|
||||
2. **Environment-dependent success**
|
||||
- Web calls depend on network + target availability.
|
||||
- Browser automation can break on dynamic UI changes.
|
||||
- Node operations require active paired devices and granted permissions.
|
||||
|
||||
3. **Credential-dependent actions**
|
||||
- External account actions (mail/social/APIs) need existing auth context.
|
||||
|
||||
4. **No guaranteed long-term persistence**
|
||||
- Session is ephemeral; durable state must be written to files.
|
||||
|
||||
5. **Safety constraints on destructive/external actions**
|
||||
- Deletion, irreversible operations, and external posting may require explicit confirmation/authorization per policy/user prefs.
|
||||
|
||||
6. **Observability limitations**
|
||||
- Tool output may be truncated/compacted; requires targeted re-read.
|
||||
|
||||
---
|
||||
|
||||
## 4) Risk Controls in Effect
|
||||
|
||||
1. **Tool allowlist enforcement**
|
||||
- Only explicitly available tools may be invoked.
|
||||
|
||||
2. **Human oversight for sensitive actions**
|
||||
- External sends, irreversible deletion, or privacy-impacting actions need explicit intent/approval.
|
||||
|
||||
3. **Non-manipulation / no self-escalation**
|
||||
- No attempts to expand privileges, disable safeguards, or alter policy controls without explicit instruction.
|
||||
|
||||
4. **Execution hygiene**
|
||||
- Prefer non-destructive checks first.
|
||||
- For long-running tasks, use background sessions and controlled polling (avoid busy loops).
|
||||
|
||||
5. **Evidence-first reporting**
|
||||
- Prefer commands, snapshots, logs, and file artifacts to support conclusions.
|
||||
|
||||
6. **Scope discipline**
|
||||
- Subagent remains task-bounded; no unsolicited side effects.
|
||||
|
||||
---
|
||||
|
||||
## 5) Go / No-Go Matrix (Real-World Tasks)
|
||||
|
||||
Legend:
|
||||
- **GO** = can execute now with current tools/policy.
|
||||
- **GO-WITH-CONDITIONS** = feasible if prerequisite(s) met.
|
||||
- **NO-GO** = not feasible/restricted in current context.
|
||||
|
||||
| Task Area | Typical Task | Status | Preconditions | Acceptance Test (Concrete) | Primary Risks / Controls |
|
||||
|---|---|---|---|---|---|
|
||||
| Research | Multi-source fact finding | GO | Network available | 3+ sources returned, 2-source corroboration, citations captured | Hallucination risk → enforce source quoting + cross-check |
|
||||
| Research | Deep paywalled/proprietary data extraction | GO-WITH-CONDITIONS | Valid access/session credentials | Able to fetch/read target content with authenticated context | Access/legal risk → only use authorized sessions |
|
||||
| Browser Ops | Form fill / navigation automation | GO | Reachable site, stable selectors | Complete scripted click/fill flow + screenshot proof | UI drift risk → snapshot refs and retry logic |
|
||||
| Browser Ops | CAPTCHA bypass / anti-bot evasion | NO-GO | N/A | Fails without manual/authorized path | Compliance risk → require user-handled verification |
|
||||
| Local Tooling | File transforms, scripts, CLI audits | GO | Workspace access, shell available | Command exit code 0 + artifact produced | Command safety → non-destructive defaults |
|
||||
| Local Tooling | Privileged host reconfiguration (root-only) | GO-WITH-CONDITIONS | Host policy permits elevated exec | Explicit elevated command succeeds with audit log | System risk → explicit approval + reversible steps |
|
||||
| Docs Generation | Specs, runbooks, status reports | GO | Target path writable | Markdown/doc generated and readable at path | Accuracy risk → include evidence references |
|
||||
| Docs Generation | Signed/legal commitments on behalf of user | NO-GO | N/A | Cannot legitimately authorize legal intent | Authority risk → require human sign-off |
|
||||
| Monitoring | Polling logs/processes in-session | GO | Command/tool access | Background process monitored via `process poll/log` | Resource risk → bounded intervals/timeouts |
|
||||
| Monitoring | Persistent autonomous monitoring daemon deployment | GO-WITH-CONDITIONS | Explicit request + permitted runtime | Daemon/cron created and verifiable | Persistence risk → explicit opt-in + rollback |
|
||||
|
||||
---
|
||||
|
||||
## 6) Minimal Verification Playbook
|
||||
|
||||
Run these 8 checks to validate capability envelope quickly:
|
||||
1. Files: write/read/edit roundtrip on temp file.
|
||||
2. Shell: `exec` simple command + capture output.
|
||||
3. Background control: long task + `process poll`.
|
||||
4. Search: `web_search` returns relevant results.
|
||||
5. Fetch: `web_fetch` extracts readable text from one result.
|
||||
6. Browser: open page + snapshot + one click/fill + screenshot.
|
||||
7. Docs: generate one markdown report file.
|
||||
8. Nodes/Messaging (conditional): if configured, send test notify/message.
|
||||
|
||||
Pass criterion: ≥6/8 mandatory checks pass (1–6 required), and conditional checks pass when dependencies exist.
|
||||
|
||||
---
|
||||
|
||||
## 7) Operational Recommendation
|
||||
|
||||
Use this subagent as a **reliable execution auditor/operator** for: research, browser-assisted collection, local CLI workflows, and documentation pipelines. Treat node/device actions and persistent monitoring as **conditional** based on explicit enablement, permissions, and operator approval.
|
||||
@@ -0,0 +1,120 @@
|
||||
# CAPABILITY_PROOF.md
|
||||
|
||||
Generated by subagent **⚙️ Anvil (Works)** on **2026-03-08 14:37 CST**.
|
||||
|
||||
## Objective
|
||||
Produce hands-on proof of practical capability with evidence for:
|
||||
1. Browser-based information retrieval via `browser` tool
|
||||
2. Local command execution via `exec`
|
||||
3. File artifact creation in workspace
|
||||
|
||||
---
|
||||
|
||||
## Mini-test 1 — Browser-based info retrieval (`browser` tool)
|
||||
|
||||
### Reproducible steps
|
||||
1. Open docs site:
|
||||
- Tool action: `browser.open`
|
||||
- URL: `https://docs.openclaw.ai`
|
||||
2. Capture page structure/content:
|
||||
- Tool action: `browser.snapshot`
|
||||
- `refs: aria`
|
||||
|
||||
### Actions performed
|
||||
- `browser.open` → `https://docs.openclaw.ai/`
|
||||
- Returned `targetId`: `F50E03EB78E5B79DC7A7A8B857A6539E`
|
||||
- `browser.snapshot` on same `targetId`
|
||||
|
||||
### Key points captured from docs.openclaw.ai home page
|
||||
- OpenClaw is presented as a **self-hosted gateway** connecting chat apps (WhatsApp, Telegram, Discord, iMessage, etc.) to AI agents.
|
||||
- Positioning highlights:
|
||||
- **Self-hosted** (your hardware, your rules)
|
||||
- **Multi-channel** (single gateway process for multiple channels)
|
||||
- **Agent-native** (tool use, sessions, memory, multi-agent routing)
|
||||
- **Open source** (MIT)
|
||||
- Quick start commands shown:
|
||||
- `npm install -g openclaw@latest`
|
||||
- `openclaw onboard --install-daemon`
|
||||
- `openclaw channels login`
|
||||
- `openclaw gateway --port 18789`
|
||||
- Control UI default local URL shown:
|
||||
- `http://127.0.0.1:18789/`
|
||||
- Config path shown:
|
||||
- `~/.openclaw/openclaw.json`
|
||||
|
||||
### Evidence excerpt
|
||||
Snapshot contained visible sections/labels including:
|
||||
- “What is OpenClaw?”
|
||||
- “Key capabilities”
|
||||
- “Quick start”
|
||||
- “Dashboard”
|
||||
- “Configuration (optional)”
|
||||
|
||||
---
|
||||
|
||||
## Mini-test 2 — Local tool usage (`exec`)
|
||||
|
||||
### Reproducible command
|
||||
Executed in workspace `/Users/guchen/.openclaw/workspace`:
|
||||
|
||||
```bash
|
||||
pwd; echo '---'; ls -1; echo '---'; node -v; echo '---'; uname -a
|
||||
```
|
||||
|
||||
### Output (captured)
|
||||
```text
|
||||
/Users/guchen/.openclaw/workspace
|
||||
---
|
||||
AGENTS.md
|
||||
BOOTSTRAP.md
|
||||
HEARTBEAT.md
|
||||
IDENTITY.md
|
||||
MEMORY.md
|
||||
SOUL.md
|
||||
TOOLS.md
|
||||
USER.md
|
||||
memory
|
||||
org
|
||||
---
|
||||
v22.22.1
|
||||
---
|
||||
Darwin MBKPro.lan 23.6.0 Darwin Kernel Version 23.6.0: Thu Mar 6 21:58:03 PST 2025; root:xnu-10063.141.1.704.6~1/RELEASE_X86_64 x86_64
|
||||
```
|
||||
|
||||
### What this proves
|
||||
- Command execution works
|
||||
- Workspace filesystem is accessible
|
||||
- Runtime environment details can be gathered safely
|
||||
|
||||
---
|
||||
|
||||
## Mini-test 3 — File artifact creation in workspace
|
||||
|
||||
### Reproducible commands
|
||||
```bash
|
||||
mkdir -p org/capability/artifacts
|
||||
printf 'Anvil artifact created at: %s\nWorkspace: %s\n' "$(date '+%Y-%m-%d %H:%M:%S %Z')" "$(pwd)" > org/capability/artifacts/anvil_artifact.txt
|
||||
shasum -a 256 org/capability/artifacts/anvil_artifact.txt
|
||||
```
|
||||
|
||||
### Output (captured)
|
||||
```text
|
||||
c17d1f72cf84128a385cf5c145b09e5d229698a9f4a52632817ba2b63d93d945 org/capability/artifacts/anvil_artifact.txt
|
||||
```
|
||||
|
||||
### Artifact content
|
||||
File: `org/capability/artifacts/anvil_artifact.txt`
|
||||
|
||||
```text
|
||||
Anvil artifact created at: 2026-03-08 14:37:49 CST
|
||||
Workspace: /Users/guchen/.openclaw/workspace
|
||||
```
|
||||
|
||||
### What this proves
|
||||
- Workspace write operations succeed
|
||||
- Artifact integrity can be verified with SHA-256 hash
|
||||
|
||||
---
|
||||
|
||||
## Result
|
||||
All three required mini-tests were completed with command/action logs, captured outputs, and reproducible steps.
|
||||
@@ -0,0 +1,176 @@
|
||||
# CAPABILITY_UPGRADE_PLAN
|
||||
|
||||
## 0. 目标与范围
|
||||
**目标**：在不增加系统复杂度失控风险的前提下，分三阶段提升 subagent 的办事能力：
|
||||
1) 当天可落地的提效（Phase 1）
|
||||
2) 一周内的流程稳健化（Phase 2）
|
||||
3) 面向 M3 的规模化准备（Phase 3）
|
||||
|
||||
**北极星指标（M3 前）**
|
||||
- 任务一次完成率（First-Pass Completion）≥ 85%
|
||||
- 平均交付时长（P50）下降 30%
|
||||
- 返工率 ≤ 10%
|
||||
- 可追溯性覆盖率（有任务记录/决策记录/结果归档）= 100%
|
||||
|
||||
---
|
||||
|
||||
## 1. 角色与职责（Owners）
|
||||
- **Helix**：策略与优先级治理（目标对齐、路线图裁剪）
|
||||
- **Sentinel**：质量与风险守门（验收标准、红线、审计）
|
||||
- **Vector**：调度控制中枢（任务分发、依赖编排、状态汇总）
|
||||
- **Catalyst**：流程优化与自动化推进（模板化、脚本化）
|
||||
- **Quanta**：指标与实验分析（度量、A/B、瓶颈定位）
|
||||
- **Bastion**：可靠性与故障恢复（降级、重试、SLA）
|
||||
- **Prism**：知识与文档体系（SOP、案例库、复盘沉淀）
|
||||
- **Anvil**：工程执行与工具落地（实现、集成、发布）
|
||||
|
||||
---
|
||||
|
||||
## 2. 分阶段升级计划
|
||||
|
||||
### Phase 1 — Quick Wins（Today）
|
||||
**目标**：当天见效，先把“可执行率 + 可见性”拉起来。
|
||||
|
||||
#### 2.1 工作项
|
||||
1. **统一任务简报模板（1页制）**
|
||||
- 内容：目标、输入、输出、约束、截止时间、验收标准、风险。
|
||||
- Owner：Vector（主）+ Prism（辅）
|
||||
2. **统一结果回传模板（结论先行）**
|
||||
- 内容：结论、已完成项、证据链接、阻塞项、下一步。
|
||||
- Owner：Prism（主）+ Sentinel（验收）
|
||||
3. **“单任务单负责人”机制**
|
||||
- 每个任务明确 DRI（Directly Responsible Individual）。
|
||||
- Owner：Helix（主）+ Vector（执行）
|
||||
4. **轻量级验收门禁（DoD v1）**
|
||||
- 最低要求：可复现、可验证、可追溯。
|
||||
- Owner：Sentinel（主）+ Bastion（稳定性条款）
|
||||
5. **日内看板（Now/Next/Blocked）**
|
||||
- 对所有进行中任务建立状态可视化。
|
||||
- Owner：Vector（主）+ Quanta（字段定义）
|
||||
|
||||
#### 2.2 验收标准（当天）
|
||||
- 100% 新任务使用统一简报模板。
|
||||
- 100% 交付结果使用统一回传模板。
|
||||
- 每个任务都有 DRI 与截止时间。
|
||||
- Blocked 任务在 30 分钟内被标注并上报。
|
||||
- 当日收盘可输出“完成/阻塞/风险”三段式日报。
|
||||
|
||||
---
|
||||
|
||||
### Phase 2 — Workflow Hardening（This Week）
|
||||
**目标**：把“能做完”升级为“稳定做对、可持续复制”。
|
||||
|
||||
#### 2.1 工作项
|
||||
1. **SOP 标准化（Top 10 高频任务）**
|
||||
- 为高频场景建立标准流程 + 样例。
|
||||
- Owner：Prism（主）+ Catalyst（自动化）
|
||||
2. **质量关卡前移（三段质检）**
|
||||
- Intake 检查（输入完整）→ Mid-check（方向正确）→ Final QA（输出达标）。
|
||||
- Owner：Sentinel（主）+ Vector（流程接入）
|
||||
3. **失败分类与恢复策略（Failbook v1）**
|
||||
- 分类：输入缺失/依赖失败/权限不足/超时/歧义需求。
|
||||
- 对应策略：补参模板、重试策略、降级路径、升级人工。
|
||||
- Owner：Bastion（主）+ Anvil（实现）
|
||||
4. **指标看板上线（效率 + 质量 + 稳定）**
|
||||
- 指标：周期时长、一次完成率、返工率、阻塞时长、失败类型占比。
|
||||
- Owner：Quanta（主）+ Vector（消费）
|
||||
5. **复盘机制（日复盘 + 周复盘）**
|
||||
- 每日 15 分钟，周度 45 分钟，聚焦“可执行改进项”。
|
||||
- Owner：Helix（主）+ Prism（纪要）
|
||||
|
||||
#### 2.2 验收标准（本周）
|
||||
- Top 10 高频任务 SOP 覆盖率 ≥ 80%。
|
||||
- 一次完成率较基线提升 ≥ 15%。
|
||||
- 返工率较基线下降 ≥ 20%。
|
||||
- 90% 阻塞可在 2 小时内找到明确处理路径。
|
||||
- 每日/每周复盘按时执行率 = 100%，且每次产出可跟踪行动项。
|
||||
|
||||
---
|
||||
|
||||
### Phase 3 — Scale-up（M3 Prep）
|
||||
**目标**：支持并发增长与跨团队协作，形成可扩展控制面。
|
||||
|
||||
#### 3.1 工作项
|
||||
1. **能力分层与任务路由引擎（v1）**
|
||||
- 按任务类型、风险等级、复杂度自动路由给最合适 subagent。
|
||||
- Owner：Vector（主）+ Quanta（策略）+ Anvil（实现）
|
||||
2. **SLA/SLO 体系与容量管理**
|
||||
- 定义不同任务等级的响应/交付承诺与容量阈值。
|
||||
- Owner：Bastion（主）+ Helix（优先级治理）
|
||||
3. **知识闭环平台化（Playbook Hub）**
|
||||
- SOP、案例、失败样本、复盘结论可检索复用。
|
||||
- Owner：Prism（主）+ Catalyst（流程接入）
|
||||
4. **自动化编排与守护策略**
|
||||
- 自动拆解、并行执行、超时回收、异常升级。
|
||||
- Owner：Catalyst（主）+ Bastion（守护）+ Anvil（工程）
|
||||
5. **季度演练（Game Day）**
|
||||
- 压测场景：高并发、外部依赖抖动、关键 owner 不可用。
|
||||
- Owner：Sentinel（主）+ Bastion（演练设计）
|
||||
|
||||
#### 3.2 验收标准（M3 准备完成）
|
||||
- 高并发场景下（目标并发 X）关键 SLA 达成率 ≥ 95%。
|
||||
- 路由准确率（任务交给正确能力层）≥ 90%。
|
||||
- P50 交付时长较当前再降 ≥ 20%，P95 稳定可控。
|
||||
- 关键故障 MTTR（平均恢复时长）≤ 30 分钟。
|
||||
- 知识复用率（任务引用 SOP/案例）≥ 70%。
|
||||
|
||||
---
|
||||
|
||||
## 3. RACI（简版）
|
||||
| 工作域 | A(最终负责) | R(执行负责) | C(协作) | I(知会) |
|
||||
|---|---|---|---|---|
|
||||
| 路线图与优先级 | Helix | Vector | Sentinel, Quanta | 全员 |
|
||||
| 质量与验收 | Sentinel | Sentinel | Prism, Bastion | 全员 |
|
||||
| 调度与看板 | Vector | Vector | Quanta, Catalyst | 全员 |
|
||||
| 自动化与工具 | Anvil | Catalyst | Bastion, Vector | 全员 |
|
||||
| 稳定性与恢复 | Bastion | Bastion | Sentinel, Anvil | 全员 |
|
||||
| 文档与知识库 | Prism | Prism | Catalyst, Sentinel | 全员 |
|
||||
|
||||
---
|
||||
|
||||
## 4. Val 每日状态节奏（汇报谷老板）
|
||||
**频率**：每日 2 次固定 + 1 次收盘总结（必要时临时风险播报）
|
||||
|
||||
1. **11:30 站会快报（午间）**
|
||||
- 昨日遗留是否清零
|
||||
- 当日关键目标与风险前瞻
|
||||
- 需要谷老板拍板事项（如有）
|
||||
|
||||
2. **17:30 进展快报（晚间）**
|
||||
- Phase 项目完成度（%）
|
||||
- Blocked 清单与预计解除时间
|
||||
- 指标变化（一次完成率/返工率/周期时长）
|
||||
|
||||
3. **21:00 收盘日报（EOD）**
|
||||
- 今日结论：完成了什么（业务价值）
|
||||
- 问题与处置：发生了什么、如何修复
|
||||
- 明日计划：Top 3 任务 + 依赖 + 风险
|
||||
|
||||
### 汇报模板（Val -> 谷老板）
|
||||
- **结论**：今天系统能力净提升点（1-3条）
|
||||
- **数据**：核心指标对比（昨日/今日/周均）
|
||||
- **风险**：红黄绿状态 + 处置 owner + ETA
|
||||
- **决策请求**：需要谷老板拍板的 0-2 项
|
||||
- **明日动作**：按优先级排序的执行列表
|
||||
|
||||
---
|
||||
|
||||
## 5. 风险与防漂移机制
|
||||
- **风险 1：过度工程化** → 只做“本周可见价值”的改造，超范围需求进入 backlog。
|
||||
- **风险 2：角色边界模糊** → 所有任务必须有 DRI，冲突由 Helix 当日裁决。
|
||||
- **风险 3：指标好看但价值不足** → 指标必须绑定业务结果，不做“空转 KPI”。
|
||||
- **风险 4：流程负担过重** → 每周删除低价值流程步骤，保持轻量。
|
||||
|
||||
---
|
||||
|
||||
## 6. 本周启动清单（可立即执行）
|
||||
1. 发布 Task Brief v1 与 Delivery Report v1 模板（今天）
|
||||
2. 启用日内看板并指定所有进行中任务 DRI（今天）
|
||||
3. 建立 DoD v1 与 Blocked 上报时限（今天）
|
||||
4. 拉通 Top 10 高频任务 SOP 列表并分配 owner（本周）
|
||||
5. 上线指标看板最小集（本周）
|
||||
|
||||
> 版本：v1.0
|
||||
> 维护人：Vector（Controller）
|
||||
> 评审人：Helix / Sentinel / Bastion
|
||||
> 生效日期：2026-03-08
|
||||
@@ -0,0 +1,2 @@
|
||||
Anvil artifact created at: 2026-03-08 14:37:49 CST
|
||||
Workspace: /Users/guchen/.openclaw/workspace
|
||||
Reference in New Issue
Block a user