memory: record repository workspace layout

This commit is contained in:
hotwa
2026-03-19 11:40:06 +08:00
parent 5c5fc23fe9
commit 940c9aead1
2 changed files with 22 additions and 0 deletions

View File

@@ -10,3 +10,4 @@
- 后续应记住:`gitea.jmsu.top` 是 hotwa`lingyuzeng`)的自建 Gitea`work2ai` 是提供给 Claw 使用的专属账号
- hotwa 后续计划再为 Claw 创建可用于访问该 Gitea 仓库的 GPG 密钥
- hotwa 补充:自建 Gitea 首选访问地址为 `https://gitea.jmsu.top`;若 HTTPS 外网访问失败,可回退使用 `http://100.64.0.27:8418` 访问 Gitea 服务
- hotwa 确认新的仓库目录规范:今后 Gitea / GitHub 账号克隆下来的代码仓库统一放到 `~/project/workspace/...`(如 `~/project/workspace/gitea/...``~/project/workspace/github/...`),不要放在 `~/openclawd/vaults`,以避免污染 OpenClaw 的记忆/运行区

View File

@@ -0,0 +1,21 @@
# Repository workspace layout
## Decision
Code repositories cloned from Gitea or GitHub should live under `~/project`, not under `~/openclawd/vaults`.
Recommended base path:
- `~/project/workspace/gitea/...`
- `~/project/workspace/github/...`
## Rationale
- Keep `~/openclawd/vaults` clean for OpenClaw runtime, memory, skills, and configuration
- Avoid mixing assistant-memory files with business/source repositories
- Reduce context pollution and accidental edits in the memory/runtime workspace
- Give ACP/opencode jobs a predictable code workspace
## Rule of thumb
- `~/openclawd/vaults` → OpenClaw runtime/config/memory only
- `~/project/workspace/...` → cloned code repositories and active development work