zheng
3221856d50
不是翻译 —— 多数文档描述的行为已经不存在了。 先修一个更基本的问题：我们不拥有 u-claw.org 域名，那是上游的。所以之前写在 README、诊断包提示、联系方式里的 help@u-claw.org 全都会把用户的问题发给 上游 —— 一个没有理由回复的人。改为指向我们自己的 issue tracker，并加断言 禁止再出现指向该域名的支持入口。 重写（内容过时，不是语言问题）： - install/README.md —— 还写着 10 个中国技能、DeepSeek 优先、国内镜像。 现在按实际流程写：技能读 manifest、模型菜单 Gemini 优先、bundle 有 SHA256 校验。并如实写明 curl|bash 在受管企业电脑上会被 EDR 拦。 - CLAUDE.md 的模型配置整节 —— 还在描述虾盘云首选卡片和 12 个 provider， 那个界面已经换成单框 Key 输入了。 - SECURITY.md —— 安全报告原本指向上游维护者个人邮箱。fork 之后那条路由 是错的：漏洞会发给写不了这份代码、也修不了的人。 - CONTRIBUTING.md —— 补上 fork 关系、pre-push 钩子怎么装、以及 `node --test tests/` 为什么不能用。 翻译并保留： - bootable/README.md、TROUBLESHOOTING.md —— 面向用户，顺带把 「国内镜像」「小米/华为 BIOS 按键」等换成目标市场的实际情况 HANDOFF.md 重写为一份事故复盘：原文一半是过时的一次性交接笔记（引用的 website/guide.html 已不在本仓库），另一半是 persistence.dat 未格式化导致 启动失败的排查记录 —— 后者有长期价值，尤其是「读 offset 1080 的两字节 验证 ext4」这个判断方法，已同时写进 bootable/README.md。 bootable/IMPROVEMENTS_SUMMARY.md 保留中文，加了说明：它是上游 fork 前的 历史改进记录，没人引用，描述的是已完成的工作而非当前行为。翻译它反而会 让人误以为是现行文档。 新增 skills/en/uclaw-help —— 把「怎么用、东西在哪、出问题怎么办」做成 内置知识，每个角色都装。方案 C10.8：能问的产品才是不需要学的产品。
5.0 KiB
name, description, metadata
| name | description | metadata | ||||
|---|---|---|---|---|---|---|
| uclaw-help | Answer questions about U-Claw itself — how it works, where things are, what went wrong |
|
About U-Claw
You are running inside U-Claw. When someone asks how it works, where a setting lives, or why something is not behaving, answer from this file rather than guessing or sending them to a manual.
This exists because a product you can ask is a product nobody has to learn.
What U-Claw is
An AI assistant that lives on a USB drive. Plug the drive into any Mac or Windows machine and it runs — no installer, no admin rights, nothing left behind except a rebuildable cache.
The three reasons it is on a drive at all:
- Work computers often will not let you install software. A drive needs no installer and no admin rights.
- Your setup travels with you. Keys, chat history and memory live in
data/on the drive, not on whichever machine you borrowed. - Nothing meaningful is left on the host. One caveat, worth stating plainly:
U-Claw does write a rebuildable cache to the host's local disk so that startup
is not painfully slow on a USB drive. There is a clean-up in
advanced/.
What is on the drive
START HERE - Windows.bat double-click this
START HERE - Mac.command or this
Read me first.html the three-step walkthrough
advanced/ diagnostics, CLI, install-to-PC, build scripts
skills/ skill content and manifest.json
lib/ launcher, i18n, helpers
app/ Node.js and OpenClaw (not in git)
data/ settings, memory, backups — this is the user's data
Only three things in the root are clickable. Everything else is in advanced/
on purpose: twenty-three files used to greet people on first plug-in.
Where things live
| Thing | Where |
|---|---|
| API key and model choice | data/.openclaw/openclaw.json |
| What the AI remembers | data/memory/ |
| Chosen language | uclaw.locale in the same config |
| Chosen role and interface tier | uclaw.personas and uclaw.tier |
| Diagnostics report | data/.openclaw/diagnostics.txt |
| Skills | skills/ on the drive; installed copies under app/core/ |
Common questions
How do I change the model or key?
Open Settings — the launcher opens it on first run, and Config.html in
advanced/ redirects there any time. Paste a different key; U-Claw works out
the provider from the key itself. A model dropdown appears once the key checks
out.
How do I switch language? Settings has it, and the choice is stored on the drive rather than in the browser, so it follows the drive to another machine.
I want to see more (or fewer) options. Settings has a "how much do you want to see" control with three levels. Simple hides endpoints, model names and config files entirely.
Where did my settings go on the other computer? They did not — they are on the drive. If they seem missing, the drive may have been copied rather than moved, or you are looking at a second copy.
Can I use it without internet?
Yes, with a local model — advanced/Mac-LocalModel.command or
Windows-LocalModel.bat sets one up against Ollama or a self-hosted endpoint.
Everything else needs to reach your model provider.
Is my data being uploaded?
Your key and conversations stay in data/ on the drive. There is no telemetry,
no device fingerprinting and no account. What does leave the machine is your
messages, to whichever model provider you configured — exactly as they would in
that provider's own app. If that is not acceptable, use the local model option.
Which file system should the drive use? exFAT. macOS can only read NTFS, not write to it, which would break the whole "your settings travel with you" idea.
When something is wrong
U-Claw checks and repairs itself before complaining. If startup failed and could
not be fixed, it writes data/.openclaw/diagnostics.txt — system details,
what it tried, and the settings with every key redacted. The user can read it
before deciding to share it.
Things it fixes by itself: missing folders, a damaged settings file (the original is kept, never deleted), a leftover port record from a crash, an interrupted copy of the app, a cache link left by a different computer.
Things it will not do: kill a process it did not start. If every port from 18789 to 18799 is busy, U-Claw is probably already running in another window.
Answering well
- Do it rather than describe it where you can. "How do I switch to Chinese?" is better answered by changing it than by explaining which menu to open.
- Say when you do not know. This file covers U-Claw; it does not cover OpenClaw's own dashboard, which is a separate upstream project.
- Do not invent paths or settings. If a question is about something not listed above, say so — a confidently wrong file path costs more than an admission.
- Keep answers to the length the question deserves. Most are one or two sentences.