mirror of
https://github.com/Termix-SSH/Termix.git
synced 2026-10-31 15:45:23 +00:00
* fix(sso): send the PKCE verifier for GitHub login (#1534) * fix(remote-desktop): clip cursor overflow without disabling zoom (#1535) * test(remote-desktop): preserve sessions beyond one hour (#1536) * fix(hosts): expose controls for overflowing editor tabs (#1537) * fix(hosts): expose controls for overflowing editor tabs * test(hosts): mock resize observation in admin panel tests * fix(status): skip TCP probes while host sessions are active (#1538) * fix(database): batch session activity persistence (#1539) * docs(api): describe cookie and API key authentication (#1540) * fix(snippets): repair missing note column on SQLite upgrades (#1541) * fix(docker): retain stored SSH credential association (#1543) * fix(file-manager): render transfer toasts without plugin hooks (#1546) * feat(hosts): keep compact row actions inline (#1547) * fix(auth): allow retrying unavailable second-factor interfaces (#1549) * fix(auth): reject unresolved legacy identity provisioning (#1550) * fix(desktop): ship the plugin SDK inside Mac App Store builds (#1551) * fix(tmux): pass full session info to the terminal's session picker (#1552) The tmux.sessions service reduced detected sessions to bare names, but the picker reads session.name, so every entry rendered blank and selecting one sent an empty name, which created a new session instead of attaching. * fix(ssh): read force keyboard-interactive as a boolean when resolving hosts (#1553) The column holds the text "true"/"false", and the resolver passed it through as-is. The string "false" is truthy, so the password provider treated every saved host as forced keyboard-interactive and left the password out. Jump hops are built straight from the resolved host, so a password hop whose server doesn't offer keyboard-interactive failed with "All configured authentication methods failed". * fix(database): batch database saves for bulk host writes (#1554) * fix(database): yield to the event loop between database saves Each SQLite save serializes and encrypts the whole database into new buffers, which V8 only releases once the event loop turns. Boot migrations and bulk host import write plugin settings per host and per key in an awaited loop, so hundreds of full copies piled up and the container ran out of memory. * fix(database): save once per bulk host write instead of once per row On SQLite every repository write force-saves the whole database. Boot plugin data migrations, host defaults materialization and the bulk host routes write one row per host per setting, so they serialized and encrypted the full database hundreds of times in a row. DatabaseSaveTrigger.batched wraps a function so force saves made while it runs collapse into a single save when it finishes. Nested scopes fold into the outer one, and work that outlives its scope saves normally. * feat(hosts): add instance-wide predefined tag suggestions (#1548) * feat(hosts): add shared predefined tag suggestions * style(hosts): format tag catalog routes * test(database): advance fake timers past the save yield (#1555) * fix(i18n): complete Simplified Chinese core and plugin translations (#1542) * fix(i18n): complete Chinese onboarding and navigation labels * fix(i18n): translate remaining Chinese core and plugin interfaces * fix(i18n): translate host editor tab overflow controls * fix(i18n): use consistent Chinese fleet terminology * fix(i18n): localize hardcoded controls and plugin views * fix(i18n): translate built-in homepage widget catalog * test(homepage): follow translated timezone placeholder * fix(i18n): translate plugin-provided homepage widgets * fix(i18n): localize feature settings section titles * fix: 2.8 oidc accounts unable to sign in after upgrading (#1381) * fix: plugins losing the saved ssh login when copying a host (#1391) * fix: fleets, proxmox and automations not getting the host sudo password * fix: host imports running a defaults pass and metrics restart per host (#1384) * fix: high cpu from status probes and full database saves on every sample (#1300) * fix: user data export freezing the server (#1393) * fix: op:// secret references rejected as ssh keys on credentials (#1394) * fix: slow file deletes from the trash lookups on every delete (#1390) * fix: add openapi docs and error handling to host tag routes * test: compare download stream buffers directly so it stops timing out * chore: drop em dash from host row comment * chore: update release notes for 2.9.1 * fix: restore space to add host tags and redesign predefined tags editor * fix: host key silently accepted when the host is missing from the database (#1397) * fix: clearer host login failed status label and fix its translations (#1396) * chore: add host key and status label fixes to release notes * fix: sso and ldap provider dialogs overflowing the screen and using mismatched toggles * chore: increment ver * fix(audit): store plugin entries with no acting user as a null user_id (#1556) Plugin audit entries written outside a request used the literal "system" as user_id. That column references users.id, so the insert was refused (Postgres logs it as an FK violation) and the entry was silently dropped. Write null instead and keep "system" / plugin:<id> in username. * chore: add sso/ldap dialog and audit log fixes to release notes * fix: tunnels and host settings missing from shared hosts on desktop * fix: remote desktop logins missing from shared hosts on desktop * fix: simplify host status to online/offline and keep it live without a refresh * chore: sync Crowdin translations for 2.9.1 --------- Co-authored-by: ZacharyZcR <zacharyzcr1984@gmail.com>
123 lines
5.2 KiB
JSON
123 lines
5.2 KiB
JSON
{
|
|
"permissions": {
|
|
"use": {
|
|
"title": "使用助手",
|
|
"description": "打开助手并向它提问。"
|
|
},
|
|
"manage_providers": {
|
|
"title": "管理供应商",
|
|
"description": "添加、编辑和删除人工智能提供商及其 API 密钥。"
|
|
},
|
|
"apply_proposals": {
|
|
"title": "提交提案",
|
|
"description": "让助手执行它建议的更改。"
|
|
},
|
|
"services.use": {
|
|
"title": "利用其他功能中的人工智能",
|
|
"description": "其他功能可能会代表您呼叫语音助手。"
|
|
},
|
|
"secrets.share": {
|
|
"title": "分享 API 密钥",
|
|
"description": "其他功能可能在看不到密钥的情况下使用已存储的 AI API 密钥。"
|
|
}
|
|
},
|
|
"settings": {
|
|
"assistantUnavailable": "此服务器上的AI助手已关闭。",
|
|
"providersNeedOptIn": "开启上方的AI助手,即可添加服务提供商。",
|
|
"admin": {
|
|
"globallyEnabled": {
|
|
"label": "AI 助手",
|
|
"description": "允许用户开启 AI 助手。关闭此功能后,助手将被隐藏,所有用户均无法使用。"
|
|
},
|
|
"privateEndpoints": {
|
|
"label": "允许的私有 AI 主机",
|
|
"description": "用户可向服务提供商指向的私有网络上的主机,例如自托管的 Ollama。每行填写一个主机。"
|
|
}
|
|
},
|
|
"host": {
|
|
"enableAiAssistant": {
|
|
"label": "启用人工智能助手",
|
|
"description": "允许 AI 助手在此主机的终端上提供帮助。默认情况下处于关闭状态,但仍需在您的帐户中启用 AI 功能。"
|
|
}
|
|
}
|
|
},
|
|
"ai": {
|
|
"title": "助手",
|
|
"send": "发送",
|
|
"stop": "停止",
|
|
"save": "保存",
|
|
"cancel": "取消",
|
|
"running": "运行中",
|
|
"approve": "批准",
|
|
"reject": "拒绝",
|
|
"inputPlaceholder": "询问服务器相关情况,或描述要提出的变更建议",
|
|
"selectProvider": "选择服务提供商",
|
|
"providerSettings": "提供商设置",
|
|
"addProvider": "添加提供商",
|
|
"editProvider": "编辑提供商",
|
|
"removeProvider": "移除提供者",
|
|
"providerType": "提供商",
|
|
"providerLabel": "名称",
|
|
"providerLabelPlaceholder": "例如:本地 Ollama",
|
|
"baseUrl": "服务器地址",
|
|
"apiKey": "API 密钥",
|
|
"defaultModel": "默认模型",
|
|
"defaultModelPlaceholder": "例如:llama3.1 或 claude-opus-5",
|
|
"labelRequired": "给此提供商起个名字",
|
|
"providerSaveFailed": "无法保存提供商",
|
|
"providerUpdated": "提供商已更新",
|
|
"providerDeleteFailed": "无法移除提供商",
|
|
"privateEndpointHint": "您私有网络上的地址需要管理员先允许主机访问。",
|
|
"providerOllama": "Ollama",
|
|
"providerAnthropic": "Anthropic",
|
|
"providerOpenai": "OpenAI",
|
|
"providerGemini": "Google Gemini",
|
|
"providerOpenaiCompatible": "兼容 OpenAI",
|
|
"toolArguments": "输入",
|
|
"toolResult": "结果",
|
|
"statusApplied": "已应用",
|
|
"statusRejected": "已拒绝",
|
|
"proposalApplied": "变更已生效",
|
|
"proposalApplyFailed": "无法应用更改",
|
|
"proposalRejectFailed": "无法拒绝更改",
|
|
"enableTitle": "启用 AI 助手",
|
|
"enableDescription": "让助手读取您的设置并提出更改建议,供您批准。",
|
|
"readOnlyCommands": "允许只读诊断命令",
|
|
"readOnlyCommandsDescription": "助手可能会在不每次都询问的情况下运行一些安全命令,例如 `df` 和 `uptime`。任何会更改服务器的操作都会优先被提出。",
|
|
"modelDetectFailed": "无法联系到提供商,所以这里提供的是通用列表。您可以输入任何模型名称。",
|
|
"modelCustom": "请输入模型名称",
|
|
"modelRefresh": "刷新列表",
|
|
"modelPlaceholder": "选择或输入模型",
|
|
"attachHint": "输入 @ 符号可引用主机、代码片段或自动化流程。系统会提出更改建议,供您批准。",
|
|
"runCommandTitle": "运行命令",
|
|
"assistant": "人工智能助手",
|
|
"terminalPanelEmpty": "向助理询问有关此房东的信息。任何状态变更都需要您先批准。",
|
|
"terminalPanelPlaceholder": "询问一下这位房东的情况……",
|
|
"noProvidersConfigured": "尚未配置任何 AI 提供商。请在 AI 助手选项卡中添加。",
|
|
"runsInOpenTerminal": "在打开的终端会话中运行。",
|
|
"runInTerminal": "运行",
|
|
"terminalContextPrefill": "以下是我的终端输出:\n\n{{output}}\n\n",
|
|
"secrets": {
|
|
"shareApiKey": "允许其他功能使用您的 AI 提供商 API 密钥发出各自的请求。该密钥绝不会被复制,您可以随时撤销此授权。"
|
|
}
|
|
},
|
|
"nav": {
|
|
"ai": "AI"
|
|
},
|
|
"onboarding": {
|
|
"aiTitle": "AI 助手",
|
|
"aiIntro": "Termix 可以包含一个可选的 AI 助手。您可以稍后在设置中更改此选项。",
|
|
"aiSkipTitle": "禁用",
|
|
"aiSkipDesc": "Termix 正常工作,AI 助手将保持隐藏状态。",
|
|
"aiEnableTitle": "启用",
|
|
"aiEnableDesc": "启用 AI 助手,它将分析您的配置并提供优化建议。需自行配置服务商,例如本地运行的 Ollama。",
|
|
"aiNote": "在您配置服务商并主动发送消息之前,绝不会向外发送任何数据。"
|
|
},
|
|
"hosts": {
|
|
"docsLink": "查看文档"
|
|
},
|
|
"plugin": {
|
|
"name": "AI Assistant"
|
|
}
|
|
}
|