## Summary - 添加第二批核心功能模块的中文翻译（8 个文件）：隐私与安全、第三方集成、吉祥物、模型路由、编码器、语音、定时任务、系统与工具 - 修复批次 A 遗留的 12 处未本地化内部链接（因第二批新增目标 `.zh-CN` 文件，之前保留的英文链接现在可指向中文版） - 修复第二批翻译中的 12 处质量问题：错别字、过直译、中英混杂、指向不存在的 `.zh-CN` 链接 - 修复隐私与安全文档中指向 `local-ai.zh-CN.md` 和 `triggers.zh-CN.md` 等尚未翻译文件的错误链接 - 统一 mascot、integrations 等跨模块链接指向，确保中文读者在 zh-CN 文档间流转 - 所有修改仅涉及 `.md` 文档，无代码变更 ## Problem - OpenHuman 中文用户阅读英文文档存在语言障碍 - 第一批汉化（overview + lightweight features）完成后，核心功能模块（integrations、model-routing、native-tools 等）仍无中文版 - 批次 A 的部分链接因目标文件当时未翻译而保留英文版，随着第二批新增 zh-CN 文件，这些链接已过时 ## Solution - 基于英文原文逐文件翻译，遵循术语统一表（vault→存储库、Agent→智能体、LLM/Token 保留英文等） - 翻译完成后运行审计脚本扫描，修复所有未本地化链接、MD040 代码块标识、术语一致性问题 - 对于目标 `.zh-CN.md` 不存在的链接（如 triggers、subconscious、local-ai、agent-coordination），保持指向英文原文，在 Related 中标记后续批次覆盖计划 ## Submission Checklist - [x] I have read the Codex PR Checklist - [x] I have confirmed Type Check passes (`pnpm typecheck`) (N/A: Markdown docs only) - [x] I have confirmed the app builds locally (`pnpm build`) (N/A: Markdown docs only) - [x] I have added tests for this change (N/A: i18n docs do not affect testable logic) - [x] I have updated documentation (N/A: this PR is documentation-only) - [x] I have confirmed no feature flags are required (N/A: no code changes) - [x] I have confirmed Prettier passes (`pnpm format:check`) (N/A: Markdown docs only) ## Impact - Runtime/platform impact: None - Performance/security/migration/compatibility: None ## Related - Follow-up PR(s)/TODOs: - Batch C: subconscious.zh-CN.md, triggers.zh-CN.md, local-ai.zh-CN.md, agent-coordination.zh-CN.md - Batch C: memory-tools.zh-CN.md, meeting-agents.zh-CN.md, developing/cef.zh-CN.md --- ## AI Authored PR Metadata ### Linear Issue - Key: N/A - URL: N/A ### Commit & Branch - Branch: `docs/i18n-batch-b-core-features` - Commit SHA: see PR commits ### Validation Run - [x] `pnpm --filter openhuman-app format:check` — N/A: no code changed - [x] `pnpm typecheck` — N/A: no code changed - [x] Focused tests: N/A - [x] Rust fmt/check: N/A - [x] Tauri fmt/check: N/A ### Validation Blocked - N/A ### Behavior Changes - Intended behavior change: None - User-visible effect: Chinese users can now read core feature docs in zh-CN ### Parity Contract - Legacy behavior preserved: N/A - Guard/fallback/dispatch parity checks: N/A ### Duplicate / Superseded PR Handling - N/A <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Localization** * Updated Simplified Chinese UI strings for vault operations and MCP server/settings. * **Documentation** * Added extensive Chinese documentation covering integrations, mascot/meeting agents, model routing, native tools (voice, web search/scraper, coder, cron, system/tools), memory tree, obsidian wiki, token compression, platform, privacy/security, and subconscious/agent coordination. * **Chores** * Updated ignore rules to exclude AI assistant progress tracking. * Added documentation maintenance and validation scripts. <!-- review_stack_entry_start --> [](https://app.coderabbit.ai/change-stack/tinyhumansai/openhuman/pull/2450?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack) <!-- review_stack_entry_end --> <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: agent:skill-master <skill-master@openclaw> Co-authored-by: Steven Enamakel <enamakel@tinyhumans.ai>
description, icon
| description | icon |
|---|---|
| Every memory chunk also lives as a Markdown file in an Obsidian-compatible vault you can open and edit. Inspired by Karpathy's obsidian-wiki workflow. | book-open |
Obsidian-Style Memory
A preview of the OpenHuman memory in Obsidian. Data from various sources (GMail, Slack, Whatsapp etc..) is organized as a memory tree.
OpenHuman's memory is not a black box. The same chunks the agent reasons over are written as plain .md files into a vault inside your workspace. You can open it in Obsidian, browse it, edit it, and link notes by hand, and the agent will see your edits.
The design is directly inspired by Andrej Karpathy's obsidian-wiki workflow: a personal wiki where every interesting thing in your life ends up as a linkable note.
Where the vault lives
<workspace>/
└── wiki/
├── summaries/ # auto-generated source / topic / global summaries
├── notes/ # your hand-written notes (free-form)
└── … # one folder per connected toolkit you've connected
The summaries/ folder is laid out hierarchically, by date for the global tree, by source for source trees, by entity for topic trees. Each file's frontmatter carries provenance (source ids, time range, scope) so the agent can trace any claim back to the chunks that produced it.
Open the vault
In the desktop app, the Memory tab has a "View vault in Obsidian" button. It uses an obsidian://open?path=... deep link, so you need Obsidian installed.
You can also open the folder in any editor, it's just Markdown. Links between files use standard [[wiki-link]] syntax, so Obsidian's graph view, backlinks, and tag explorer all work out of the box.
Editing notes by hand
Anything you put in wiki/notes/ is fair game for ingest. The same pipeline that processes Gmail and Slack picks up your hand-written notes, chunks them, scores them, and folds them into the topic and global trees alongside everything else.
This means you can:
- Drop a meeting note in
wiki/notes/2026-05-08-board-call.mdand the agent will know the context tomorrow. - Maintain a file per project, per person, per ticker, the topic tree treats your manual notes as just another source.
- Bulk-import an existing Obsidian vault: drop the
.mdfiles in and trigger ingest.
Why this matters
You can't trust a memory you can't read. Most "AI memory" systems hide the state in opaque embeddings; OpenHuman's vault is the inverse, the agent's memory is literally a folder of Markdown you own. If the agent gets something wrong, you can find the file, fix it, and the next retrieval is correct.
It's also the cleanest possible export: stop using OpenHuman tomorrow and you keep a fully-formed personal wiki.
See also
- Memory Tree. the pipeline that produces the vault.
- Auto-fetch from Integrations. how the vault grows on its own.