github langbot-app/LangBot v4.11.9
LangBot v4.11.9

one hour ago

LangBot 是一个开源的 AI 聊天机器人与智能体平台,支持多种即时通讯平台、大语言模型、知识库和插件,帮助你构建、部署和管理 AI 助手。
LangBot is an open-source AI chatbot and agent platform that connects messaging platforms, large language models, knowledge bases, and plugins to help you build, deploy, and manage AI assistants.

LangBot v4.11.9

The Box sandbox now runs on Windows hosts, Agents can read uploaded files on demand and publish files they produce, and new installs keep Skills and uploads in the database.

本版本让 Box 沙箱可以在 Windows 主机上运行;Agent 可以按需读取上传的文件,并发布自己生成的文件;新安装默认把 Skill 和上传内容保存在数据库中。

Upgrade note / 升级提示:本版本包含新的数据库迁移(0049–0053),升级前请备份 data/ 目录(使用 PostgreSQL 时同时备份数据库);降级需要用这份备份恢复。已有部署在 config.yaml 中的存储、Skill 和 Box 设置保持不变。This release adds database migrations 0049–0053. Back up data/ (and PostgreSQL, if used) before upgrading; rolling back needs that backup. Existing deployments keep the storage, Skill and Box settings in their config.yaml.

Highlights

  • Windows host Box / Windows 主机沙箱:插件 SDK 0.7.26 让 host 后端支持 Windows:命令优先用 Git Bash 执行,没有时退回 PowerShell,结束时清理整个进程树。注意:host 不做任何隔离(UNSAFE),命令以运行 LangBot 的用户身份直接执行,群聊里不可信的用户可能通过提示词注入执行命令。它不会被自动选中,需要在 config.yaml 里显式设置 box.backend: host,或由 lbctl 原生安装写入(lbctl v0.5.14 起)。在 box.file_transfer_mode: network 下 Skill 无法在 Windows host Box 上执行;LangBot 与 Box 在同一台机器时请使用 legacy(lbctl 会自动写入)。The host backend now works on Windows (Git Bash, falling back to PowerShell; the whole process tree is cleaned up). host has no isolation and runs commands as the LangBot user, so untrusted group-chat users could run commands through prompt injection. It is never auto-selected: set box.backend: host explicitly or let lbctl (v0.5.14+) write it for native installs. Skills cannot run on a Windows host Box in network transfer mode; when LangBot and Box share one machine, use box.file_transfer_mode: legacy (lbctl sets this for you).
  • Files for Agents / Agent 文件:上传的文件保存为带权限的文件资产。Agent 先拿到文件引用,需要时再通过工具按段读取文本、图片或 PDF;Runner 可以把生成的文件发布给指定接收人,运行结束或 Core 重启后仍可下载。知识库文件、插件 SDK 也接入了同一套文件资产。Uploads become authorized file assets: Agents get references and read text, images or PDF pages on demand through tools, and Runners can publish output files that stay downloadable after the run ends or Core restarts. Knowledge-base files and the plugin SDK use the same assets.
  • Database-backed Skills and uploads by default / 新安装默认数据库存储:新安装默认把 Skill(含历史版本)和上传内容存进数据库,Box 默认通过网络传输文件,Core 与 Box 不再需要共享目录。已有部署切换到这种模式时,Core 会在启动、开放 HTTP 之前导入旧的 Skill 和本地文件,可中断恢复,导入完成后不再依赖旧目录。Docker 网络模式的 Box 可以挂载只读的本地数据集。New installs store Skills (with their version history) and uploads in the database, and Box moves files over the network instead of a shared directory. When an existing deployment switches over, Core imports old Skills and local files before serving HTTP, resumably. Docker network-mode Boxes can mount read-only local datasets.
  • Operations API / 操作 API:新增 /api/v1/operations 接口(目录、说明、执行、SSE 流),API Key 也可以确认插件权限,lbctl 等客户端可以用 API Key 确认插件权限。New /api/v1/operations routes (catalog, describe, execute, SSE) and plugin permission confirmation with an API key, so API clients such as lbctl can confirm plugin permissions.
  • WebUI:更新对话框直接显示 langbot.app 上的更新日志;插件详情页显示已安装版本并可直接升级;安装插件后按组件类型提示下一步。The update dialog shows release notes from langbot.app; plugin detail pages show the installed version and offer upgrades; installing a plugin suggests the next step.
  • Startup / 启动:启动时不再自动 pip install 缺失的依赖,而是列出缺少的包并提示重新安装后退出。LangBot no longer pip-installs missing packages at startup; it lists them and exits with reinstall instructions.
  • Fixes / 修复:反复启动失败的插件进程会退避重试,不再刷屏;Telegram 流式编辑忽略 "message is not modified";MulticaAgent 遇到临时错误会重试,重启期间丢失的回复会补发;企业微信客服给裸 external_userid 发消息时自动解析 open_kfid;LangBot Cloud 上的告警保持需手动开启;E2B 工作区限额生效;插件打包排除虚拟环境目录。Failing plugin workers back off; Telegram streaming ignores "message is not modified"; MulticaAgent retries transient errors and recovers replies lost to restarts; WeCom customer service resolves open_kfid for bare external_userid targets; alerts stay opt-in on LangBot Cloud; E2B workspace limits are enforced; plugin packages exclude virtualenvs.
  • SDK:langbot-plugin 由 0.7.25 固定到 0.7.26。Core pins langbot-plugin==0.7.26.

Release verification

  • Release commit 826bf580ff42bbf10dac52203f1171f63b97b52a. It differs from the tested candidate dfa3c743c only in the version number; all pull-request checks passed on the release PR.

  • Before tagging, the candidate was installed twice on fresh data directories and run through routine operations:

    • Docker (docker compose with the plugin runtime and Box, image built from the candidate commit);
    • uvx (uvx --from <wheel> langbot, dependencies from PyPI: SDK 0.7.26, SQLAlchemy 2.1.9).

    Both passed: account setup and WebUI; Marketplace install of LocalAgent, EssentialCommands, WebSearch, LangRAG and HelloPlugin with permission confirmation, enable/disable per pipeline and uninstall; model provider and model test; a LocalAgent pipeline over HTTP Bot, including a web-search tool call; !help !cmd !func !plugin !version; knowledge-base ingestion and retrieval; creating a Skill and having the agent use it; and data, plugins, knowledge base and Skill intact after a restart. Docker ran a command in a Box sandbox container; uvx ran one through the host Box backend.

  • Concurrency: 8 simultaneous conversations on one model completed on Docker. On uvx (SQLite) some conversations exceeded the HTTP Bot 60 s reply window on a heavily loaded test host and a few hit database is locked; v4.11.8 behaved the same way side by side under the same load, so this is not new in this release.

  • Windows: the release wheel was installed with uvx on Windows 11 (build 26300, code page 936, Python 3.11, Git Bash installed; SDK 0.7.26, SQLAlchemy 2.1.9) and passed the same checklist with a local mock model, including 8 simultaneous conversations (8/8, no database is locked). With box.backend: host and file_transfer_mode: legacy, the agent ran a command (exec) and wrote and read back a file through the Windows host Box. A plugin printing Chinese and emoji kept the runtime connected, and with tokenizer downloads blocked the first LocalAgent conversation replied in 2 s (no count_tokens timeout).

  • Database migrations: databases created by v4.11.8 (revision 0048), v4.10.11 (0023) and v4.10.6 (0008, before workspaces) were upgraded to this release on both SQLite and PostgreSQL. Each upgrade reached revision 0053 and started twice cleanly; no rows were lost, SQLite integrity and foreign-key checks passed, and the seeded provider, model, bot and pipeline read back. Copies of three real SQLite databases (revisions 0042, 0040 and 0008, up to 33 MB) also upgraded cleanly. Upgraded schemas match a fresh install, apart from index naming differences on databases that started before 0024, which v4.11.8 has as well.

Contributors

@RockChinQ @huanghuoguoguo @TyperBody

Full Changelog: v4.11.8...v4.11.9

Don't miss a new LangBot release

NewReleases is sending notifications on new releases.