Unverified50% confidenceFactExact time
LangBot 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedLangBot version 4.10 hard-coded nine built-in Runners in the src/langbot/pkg/provider/runners/ directory.79% similarUnverifiedThe official Runner IDs provided by LangBot include plugin:langbot-team/ClaudeCodeAgent/default and plugin:langbot-team/CodexAgent/default.78% similarUnverifiedWhether a given chat platform is supported in LangBot depends on the adapter and event binding, not the Runner; the Runner itself does not determine the scope of platform support.68% similarUnverifiedLangBot 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.64% similarUnverifiedThe LangBot plugin manifest contains fields such as id, name, label, description, capabilities, permissions, config_schema and metadata, where capabilities is a typed boolean model used for UI and resource projection rather than a permission grant, while permissions is the access permission ceiling and is intersected with the binding policy.54% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1053063API
curl https://kongchang.com/api/v1/knowledge/claims/1053063MCP
get_claim(id=1053063)