## 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 |
|---|---|
| 118+ third-party integrations - Gmail, Notion, GitHub, Slack, Stripe, Calendar and more - with one-click OAuth and zero API keys. | plug |
Third-party Integrations (118+)
OpenHuman ships with backend-proxied access to 118+ third-party services. Connecting any of them through the managed path is a one-click OAuth flow inside the app, there are no API keys to wire by hand, and no plugin marketplace to navigate.
Under the hood, the connector layer is powered by Composio. In the default managed mode, OpenHuman's backend owns the Composio API key, OAuth token brokering, rate limits, and trigger webhook fan-out. If you switch to direct mode, the core talks to Composio with your own Composio API key; synchronous tool calls work, but real-time trigger webhooks must be configured on your own webhook infrastructure.
Once a service is connected, it shows up in four places at once:
- As an agent tool, the model can call it directly.
- As a memory source, auto-fetch syncs it into the Memory Tree every twenty minutes.
- As a profile signal, your activity across services feeds your personalization.
- As a trigger source, live events (a new email, a new charge, an inbound DM) flow into the Triggers pipeline and can fire off agent actions automatically.
Some of what's in the catalog
The catalog spans productivity, business, social, messaging and Google. A non-exhaustive sample:
| Category | Examples |
|---|---|
| Email & calendar | Gmail, Outlook, Google Calendar, Apple Calendar |
| Docs & storage | Google Docs, Google Drive, Notion, Dropbox, Airtable |
| Code & dev | GitHub, Linear, Jira, Figma |
| Comms | Slack, Discord, Microsoft Teams, Telegram, WhatsApp |
| CRM & sales | Salesforce, HubSpot |
| Commerce & payments | Stripe, Shopify |
| Project management | Asana, Trello |
| Social | Twitter / X, Spotify, YouTube |
Native vs proxied
Some services have native providers. Rust modules that know how to ingest the service into the Memory Tree directly (e.g. Gmail's native ingest path). Others are exposed as proxied tools only: the agent can call them, but there's no automatic ingest yet. New native providers are added as features land.
How connections work
Click Connect on any integration. A browser window opens for OAuth. Once you sign in, the connection becomes active and OpenHuman starts syncing it through auto-fetch on the next 20-minute tick.
Each integration shows its current status:
- Not connected. integration has not been set up.
- Connected. integration is active and being synced.
- Manage. active integration with options to reconfigure or disconnect.
You can revoke any connection at any time from the Skills tab.
Messaging channels
Three integrations are special. OpenHuman uses them to talk back to you, not just read from them:
- Telegram. the primary messaging channel. Two-way: send and receive messages, manage chats, search history, create groups, 80+ actions on your behalf. All actions run through your own encrypted credentials.
- Discord. send and receive messages via Discord. Connect your account to receive OpenHuman messages there.
- Web. a browser-based chat interface within the desktop app. Messages stay entirely local.
Set your default under Settings → Automation & Channels → Messaging Channels. The active route status shows which channel is currently in use. Telegram offers two credential modes: connect via OpenHuman (one-click, encrypted) or provide your own credentials for maximum control.
Skills
Beyond third-party services, OpenHuman has skills, small sandboxed modules that run inside the app, fetch external data, run on a schedule, transform information, and respond to events. Each runs with enforced resource limits. Skills install from the Skills tab and integrate with the same Memory Tree as everything else.
Native voice and tools
Two capabilities ship native rather than as integrations because they're load-bearing for the desktop experience:
- Voice. STT in, TTS out, plus a live Google Meet agent that joins meetings, transcribes them into your Memory Tree, and can speak back into the call.
- Native tools. built-in web search, web-fetch scraper, and a full filesystem/git/lint/test/grep coder toolset that the agent uses out of the box.
Privacy boundary
OpenHuman's core never calls any third-party API directly. All requests go through the OpenHuman backend, which handles OAuth tokens and rate limiting. Your tokens never sit on disk in plaintext on your machine, and the agent only sees the results of tool calls, not the credentials.
If you opt into direct Composio mode, that boundary changes: your local core uses your own Composio API key and you are responsible for the Composio account, rate limits, billing relationship, and any webhook endpoint needed for trigger delivery.
See Privacy & Security for the full boundary.
See also
- Triggers, live events from connected integrations and how they fire agent actions.
- Auto-fetch from Integrations
- Memory Tree