lingyun14
48ba71ad74
* fix(i18n): add missing dashboard translation keys
Several call sites reference keys that exist in no locale bundle, so the
i18n helper returns its truthy "[MISSING: key]" placeholder and the UI
leaks that instead of a translation.
- TemplateListEditor.vue used core.common.collapse/expand for the
expand/collapse tooltip; neither key existed. Add both to zh-CN,
en-US, ja-JP and ru-RU.
- BackupDialog.vue alerts core.common.unauthorized, which was absent
from every bundle. Add it to all four.
- PersonaSelector.vue reads core.shared.personaSelector.editPersona;
it existed in ru-RU only. Add it to zh-CN, en-US and ja-JP, matching
the wording of the existing createPersona entries.
- KBList.vue uses create.embeddingModelRequired as the validation rule
when creating a knowledge base. Sibling keys exist in all four
bundles but this one was missed.
The unauthorized values mirror the wording already used by the
equivalent messages.errors.auth.unauthorized entries.
* feat(i18n): add a dashboard i18n key check and fix key drift
The i18n helper returns "[MISSING: <key>]" (a truthy string) when a key is
absent, so `t(key) || 'fallback'` never falls back and the placeholder
leaks into the UI. A key missing from *every* locale is invisible to
locale-vs-locale comparison (src/i18n/validator.ts), because all bundles
agree on it, so those defects can only be caught by checking source usage
against the bundles.
Add dashboard/scripts/check-i18n-keys.mjs, run via `pnpm run i18n:check`
and wired into the Dashboard CI workflow. It assembles locale trees by
parsing each locale index.ts (bundle filenames are not runtime
namespaces: features/tool-use.json -> features.tooluse), strips comments
before scanning, respects the module-relative t()/tm() bindings from
useModuleI18n(), and skips plugin-provided strings. It has no dependency
on installed packages, so it runs without node_modules.
It reported two classes of problem, both fixed here:
- Used in source but absent from all four locales:
features.knowledge-base.detail.retrieval.debugMode and
.tsneVisualization (RetrievalTab.vue debug switch and t-SNE image alt).
- Locale drift against the zh-CN baseline:
features.subagent.form.personaPreview missing from en-US and ru-RU, and
the config-metadata use_markdown description/hint missing from ja-JP.
ru-RU additionally carries ~42 keys with no zh-CN counterpart (notably
agent_runner_type and the per-provider agent runner ids, which the backend
does use). Those are pre-existing and left alone; this check only fails on
keys that source code actually references.
* chore(i18n): remove orphaned ru-RU translation keys
Two groups of ru-RU keys reference paths the dashboard no longer reads,
left behind when zh-CN was migrated and ru-RU was not:
- features.tooluse.dialogs.syncProvider.* (22 leaves)
The syncProvider subtree now lives at the namespace root, which is what
McpServersSection.vue reads via useModuleI18n('features/tooluse'). PR #9932
relocated it for zh-CN but left ru-RU's copy under `dialogs`, so ru-RU
carried both.
- 20 features.config-metadata entries under provider_settings
Those paths were restructured into agent_runner.config.* by PR #9821 for
zh-CN. Only the entries with no zh-CN counterpart are removed here; most
provider_settings children are still live under their new paths and are
kept. platform_group.platform.kook_bot_nickname has no backend field at
all (no reference anywhere in astrbot/).
All four locales now expose an identical key set (4130 leaves each, no
missing and no extra keys), so this also removes the last locale drift the
i18n check could see.
* fix(i18n): make the key check enforce drift and scan injected translators
Addresses both blocking findings from the review.
1. Locale drift did not fail the check. The drift branch only printed its
results and never set the failure flag, and it compared in one direction
only (baseline keys absent elsewhere), so a locale could gain keys the
baseline lacks without any complaint. It now compares both directions and
fails on either, which is safe to enforce because the key sets are already
identical across all four locales (4130 leaves each).
2. Keys read through an injected translator were never scanned. The call
pattern only matched bare `t(` / `tm(`, so `props.tm('models.metadata.image')`
in ProviderModelsPanel.vue (8 call sites, reached via :tm="tm" from
ProviderPage / ProviderChatCompletionPanel) escaped validation entirely. A
key that resolves nowhere previously passed; it is now reported.
Injected usage carries no local module binding, so the parent's namespace is
unknown at the call site. Rather than guess it, such a key is only reported
when it resolves nowhere in any locale under any namespace, which keeps the
new pass free of false positives. The tradeoff is documented in the script:
a key that exists in some other namespace but not the injected one is not
caught.
Verified: deleting a baseline-only key from en-US now fails (was PASS), adding
an extra key to en-US now fails (was ignored), and the injected-translator probe
in ProviderModelsPanel.vue now fails with the call site (was PASS). The clean
tree still passes all three sections.
简体中文 ｜ 繁體中文 ｜ 日本語 ｜ Français ｜ Español ｜ Русский
Documentation ｜ Blog ｜ Roadmap ｜ Issue Tracker ｜ Email Support
AstrBot is an open-source all-in-one Agent chatbot platform that integrates with mainstream instant messaging apps. It provides reliable and scalable conversational AI infrastructure for individuals, developers, and teams. Whether you're building a personal AI companion, intelligent customer service, automation assistant, or enterprise knowledge base, AstrBot enables you to quickly build production-ready AI applications within your IM platform workflows.
Key Features
- 💯 Free & Open Source.
- ✨ AI LLM Conversations, Multimodal, Agent, MCP, Skills, Knowledge Base, Persona Settings, Auto Context Compression.
- 🤖 Supports integration with Dify, Alibaba Cloud Bailian, Coze, and other agent platforms.
- 🌐 Multi-Platform: QQ, WeChat Work, Feishu, DingTalk, WeChat Official Accounts, Telegram, Slack, and more.
- 📦 Plugin Extensions with 1000+ plugins available for one-click installation.
- 🛡️ Agent Sandbox for isolated, safe execution of code, shell calls, and session-level resource reuse.
- 💻 WebUI Support.
- 🌈 Web ChatUI Support with built-in agent sandbox and web search.
- 🌐 Internationalization (i18n) Support.
Quick Start
One-Click Cloud Deployment (RainYun)
For users who want one-click 24-hour-online deployment and do not want to manage servers themselves, we recommend RainYun's one-click cloud deployment service ☁️:
One-Click Deployment
Note
Requires uv to be installed. For macOS users: due to macOS security checks, the first run of the
astrbotcommand may take longer (about 10-20s).
For users who want to quickly experience AstrBot, are familiar with command-line usage, and can install a uv environment on their own, we recommend the uv one-click deployment method ⚡️:
uv tool install astrbot --python 3.12
astrbot init # Only execute this command for the first time to initialize the environment
astrbot run
Update astrbot:
uv tool upgrade astrbot --python 3.12
Docker Deployment
For users familiar with containers and looking for a more stable, production-ready deployment method, we recommend deploying AstrBot with Docker / Docker Compose.
Please refer to the official documentation: Deploy AstrBot with Docker.
Desktop Application Deployment
For users who want to use AstrBot on desktop and mainly use ChatUI, we recommend AstrBot App.
Visit AstrBot-desktop to download and install; this method is designed for desktop usage and is not recommended for server scenarios.
Launcher Deployment
For desktop users who also want fast deployment and isolated multi-instance usage, we recommend AstrBot Launcher.
Visit AstrBot Launcher to download and install.
More deployment methods
If you need panel-based management or deeper customization, see BT-Panel Deployment for BT Panel app-store setup, 1Panel Deployment for 1Panel app-market deployment, CasaOS Deployment for NAS/home-server visual deployment, and Manual Deployment for fully custom source-based installation with uv.
❤️ Sponsors
Welcome to sponsor us via Afdian or contact us.
Supported Messaging Platforms
Connect AstrBot to your favorite chat platform.
| Platform | Maintainer |
|---|---|
| Official | |
| OneBot v11 protocol implementation | Official |
| Telegram | Official |
| Wecom & Wecom AI Bot | Official |
| WeChat Official Accounts | Official |
| Feishu (Lark) | Official |
| DingTalk | Official |
| Slack | Official |
| Discord | Official |
| LINE | Official |
| Satori | Official |
| KOOK | Official |
| Misskey | Official |
| Mattermost | Official |
| WhatsApp (Coming Soon) | Official |
| Matrix | Community |
| Rocket.Chat | Community |
| VoceChat | Community |
Supported Model Services
| Service | Type |
|---|---|
| OpenAI and Compatible Services | LLM Services |
| Anthropic | LLM Services |
| Google Gemini | LLM Services |
| Moonshot AI | LLM Services |
| Zhipu AI | LLM Services |
| DeepSeek | LLM Services |
| Ollama (Self-hosted) | LLM Services |
| LM Studio (Self-hosted) | LLM Services |
| MiraRouter | LLM Services (API Gateway, supports all models) |
| AIHubMix | LLM Services (API Gateway, supports all models) |
| CompShare | LLM Services |
| 302.AI | LLM Services |
| TokenPony | LLM Services |
| SiliconFlow | LLM Services |
| PPIO Cloud | LLM Services |
| ModelScope | LLM Services |
| OneAPI | LLM Services |
| Dify | LLMOps Platforms |
| Alibaba Cloud Bailian Applications | LLMOps Platforms |
| Coze | LLMOps Platforms |
| OpenAI Whisper | Speech-to-Text Services |
| SenseVoice | Speech-to-Text Services |
| Xiaomi MiMo Omni | Speech-to-Text Services |
| OpenAI TTS | Text-to-Speech Services |
| Gemini TTS | Text-to-Speech Services |
| GPT-Sovits-Inference | Text-to-Speech Services |
| GPT-Sovits | Text-to-Speech Services |
| FishAudio | Text-to-Speech Services |
| Edge TTS | Text-to-Speech Services |
| Alibaba Cloud Bailian TTS | Text-to-Speech Services |
| Azure TTS | Text-to-Speech Services |
| Minimax TTS | Text-to-Speech Services |
| Xiaomi MiMo TTS | Text-to-Speech Services |
| Volcano Engine TTS | Text-to-Speech Services |
❤️ Contributing
Issues and Pull Requests are always welcome! Feel free to submit your changes to this project :)
How to Contribute
You can contribute by reviewing issues or helping with pull request reviews. Any issues or PRs are welcome to encourage community participation. Of course, these are just suggestions—you can contribute in any way you like. For adding new features, please discuss through an Issue first.
Development Environment
AstrBot uses ruff for code formatting and linting.
git clone https://github.com/AstrBotDevs/AstrBot
pip install pre-commit
pre-commit install
🌍 Community
QQ Groups
We have 15+ chat groups, please see: Community for details.
Discord Server
❤️ Special Thanks
Special thanks to all Contributors and plugin developers for their contributions to AstrBot ❤️
Open Source Friends ❤️
- NapNeko/NapCatQQ - The amazing cat framework
- Mai-with-u/MaiBot - The powerful "digital life" in your QQ!
⭐ Star History
Tip
If this project has helped you in your life or work, or if you're interested in its future development, please give the project a Star. It's the driving force behind maintaining this open-source project <3
Companionship and capability should never be at odds. What we aim to create is a robot that can understand emotions, provide genuine companionship, and reliably accomplish tasks.
私は、高性能ですから!
