+
-
+
- NanoClaw —— 您的专属 Claude 助手，在容器中安全运行。它轻巧易懂，并能根据您的个人需求灵活定制。 + Clawdie —— 您的专属 Claude 助手，在容器中安全运行。它轻巧易懂，并能根据您的个人需求灵活定制。
- nanoclaw.dev •
+ clawdie.si •
English •
@@ -19,13 +19,13 @@
[OpenClaw](https://github.com/openclaw/openclaw) 是一个令人印象深刻的项目，愿景宏大。但我无法安心使用一个我不了解却能访问我个人隐私的软件。OpenClaw 有 52+ 个模块、8 个配置管理文件、45+ 个依赖项，以及为 15 个渠道提供商设计的抽象层。其安全性是应用级别的（通过白名单、配对码实现），而非操作系统级别的隔离。所有东西都在一个共享内存的 Node 进程中运行。
-NanoClaw 用一个您能在 8 分钟内理解的代码库，为您提供了同样的核心功能。只有一个进程，少数几个文件。智能体（Agent）运行在具有文件系统隔离的真实 Linux 容器中，而不是依赖于权限检查。
+Clawdie 用一个您能在 8 分钟内理解的代码库，为您提供了同样的核心功能。只有一个进程，少数几个文件。智能体（Agent）运行在具有文件系统隔离的真实 Linux 容器中，而不是依赖于权限检查。
## 快速开始
```bash
-git clone https://github.com/qwibitai/nanoclaw.git
-cd nanoclaw
+git clone https://codeberg.org/Clawdie/Clawdie-AI.git /home/clawdie/clawdie-ai
+cd /home/clawdie/clawdie-ai
claude
```
@@ -92,7 +92,7 @@ claude
**不要添加功能，而是添加技能。**
-如果您想添加 Telegram 支持，不要创建一个 PR 同时添加 Telegram 和 WhatsApp。而是贡献一个技能文件 (`.agent/skills/add-telegram/SKILL.md`)，教 Claude Code 如何改造一个 NanoClaw 安装以使用 Telegram。
+如果您想添加 Telegram 支持，不要创建一个 PR 同时添加 Telegram 和 WhatsApp。而是贡献一个技能文件 (`.agent/skills/add-telegram/SKILL.md`)，教 Claude Code 如何改造一个 Clawdie 安装以使用 Telegram。
然后用户在自己的 fork 上运行 `/add-telegram`，就能得到只做他们需要事情的整洁代码，而不是一个试图支持所有用例的臃肿系统。
diff --git a/docs/SECURITY.md b/docs/SECURITY.md
index e726511..78a78e3 100644
--- a/docs/SECURITY.md
+++ b/docs/SECURITY.md
@@ -1,4 +1,4 @@
-# NanoClaw Security Model
+# Clawdie Security Model
## Trust Model
diff --git a/docs/nanoclaw-architecture-final.md b/docs/nanoclaw-architecture-final.md
index 103b38b..bdcb480 100644
--- a/docs/nanoclaw-architecture-final.md
+++ b/docs/nanoclaw-architecture-final.md
@@ -1,4 +1,4 @@
-# NanoClaw Skills Architecture
+# Clawdie Skills Architecture
## Core Principle
@@ -123,7 +123,7 @@ skills/
- Git's three-way merge uses context matching, so it works even if the user has moved code around — unlike line-number-based diffs that break immediately
- Auditable: `diff .nanoclaw/base/src/server.ts skills/add-whatsapp/modify/src/server.ts` shows exactly what the skill changes
- Deterministic: same three inputs always produce the same merge result
-- Size is negligible since NanoClaw's core files are small
+- Size is negligible since Clawdie's core files are small
### Intent Files
@@ -190,7 +190,7 @@ depends: [] # Skills that must be applied first
test: "npx vitest run src/channels/whatsapp.test.ts"
# --- Future fields (not yet implemented in v0.1) ---
-# author: nanoclaw-team
+# author: clawdie-team
# license: MIT
# min_skills_system_version: "0.1.0"
# tested_with: [telegram@1.0.0]
@@ -382,11 +382,11 @@ If tests fail and Level 2 can't resolve, restore from `.nanoclaw/backup/` and re
### The Problem
-`git rerere` is local by default. But NanoClaw has thousands of users applying the same skill combinations. Every user hitting the same conflict and waiting for Claude Code to resolve it is wasteful.
+`git rerere` is local by default. But Clawdie has thousands of users applying the same skill combinations. Every user hitting the same conflict and waiting for Claude Code to resolve it is wasteful.
### The Solution
-NanoClaw maintains a verified resolution cache in `.nanoclaw/resolutions/` that ships with the project. This is the shared artifact — **not** `.git/rr-cache/`, which stays local.
+Clawdie maintains a verified resolution cache in `.nanoclaw/resolutions/` that ships with the project. This is the shared artifact — **not** `.git/rr-cache/`, which stays local.
```
.nanoclaw/
@@ -588,7 +588,7 @@ There is no unrecoverable state.
## 10. Core Updates
-Core updates must be as programmatic as possible. The NanoClaw team is responsible for ensuring updates apply cleanly to common skill combinations.
+Core updates must be as programmatic as possible. The Clawdie team is responsible for ensuring updates apply cleanly to common skill combinations.
### Patches and Migrations
@@ -977,7 +977,7 @@ Each passing combination generates a verified resolution entry for the shared ca
### `.gitattributes`
-Ship with NanoClaw to reduce noisy merge conflicts:
+Ship with Clawdie to reduce noisy merge conflicts:
```
* text=auto
@@ -1060,4 +1060,4 @@ project/
16. **Skills are tested.** Integration tests per skill. CI tests pairwise by overlap. Tests run always.
17. **Deterministic serialization.** Sorted keys, consistent formatting. No noisy diffs.
18. **Rebase when needed.** Flatten layers for a clean starting point.
-19. **Progressive core slimming.** Breaking changes move functionality from core to migration skills. Existing users keep what they have automatically. New users start minimal and add what they need.
\ No newline at end of file
+19. **Progressive core slimming.** Breaking changes move functionality from core to migration skills. Existing users keep what they have automatically. New users start minimal and add what they need.
diff --git a/docs/nanorepo-architecture.md b/docs/nanorepo-architecture.md
index 1365e9e..77476b9 100644
--- a/docs/nanorepo-architecture.md
+++ b/docs/nanorepo-architecture.md
@@ -1,8 +1,8 @@
-# NanoClaw Skills Architecture
+# Clawdie Skills Architecture
## What Skills Are For
-NanoClaw's core is intentionally minimal. Skills are how users extend it: adding channels, integrations, cross-platform support, or replacing internals entirely. Examples: add Telegram alongside WhatsApp, switch from Apple Container to Docker, add Gmail integration, add voice message transcription. Each skill modifies the actual codebase, adding channel handlers, updating the message router, changing container configuration, and adding dependencies, rather than working through a plugin API or runtime hooks.
+Clawdie's core is intentionally minimal. Skills are how users extend it: adding channels, integrations, cross-platform support, or replacing internals entirely. Examples: add Telegram alongside WhatsApp, switch from Apple Container to Docker, add Gmail integration, add voice message transcription. Each skill modifies the actual codebase, adding channel handlers, updating the message router, changing container configuration, and adding dependencies, rather than working through a plugin API or runtime hooks.
## Why This Architecture
@@ -165,4 +165,4 @@ Each skill includes integration tests. Tests run **always** — after apply, aft
16. **Skills are tested.** CI tests pairwise by overlap.
17. **Deterministic serialization.** No noisy diffs.
18. **Rebase when needed.**
-19. **Progressive core slimming** via migration skills.
\ No newline at end of file
+19. **Progressive core slimming** via migration skills.