Unverified50% confidenceFactExact time
LangBot 4.11 changes Runner from built-in code to a plugin installable from the plugin marketplace; the core no longer presets the running logic of service APIs, and all external integrations must be loaded as plugins.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedLangBot version 4.11 makes external CLI agents (such as Claude Code and Codex) installable, configurable, and bindable to different chat platform pipelines like ordinary plugins through Runner pluginization.77% similarUnverifiedLangBot 4.11's Runner plugins report Runners among installed plugins via the LIST_RUNNERS protocol, and the host program caches them in RunnerRegistry and generates IDs of the form plugin:author/plugin_name/runner_name.72% similarUnverifiedLangBot Runner plugins execute in a separate plugin runtime container, so deployment requires two containers: the core container and the runtime container.71% similarUnverifiedLangBot version 4.10 hard-coded nine built-in Runners in the src/langbot/pkg/provider/runners/ directory.71% similarUnverifiedThe LangBot official document OFFICIAL_RUNNER_PLUGINS.md maps the old dify-service-api runner to the DifyAgent plugin and states that the old built-in runner code no longer provides a runtime fallback.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1066145API
curl https://kongchang.com/api/v1/knowledge/claims/1066145MCP
get_claim(id=1066145)