Interface plugin catalog¶
Call Baxter's core is protocol-neutral. Plugins connect that core to outside systems as signal sources, action sinks, pollers, or ingress adapters.
Built-in runtime plugins¶
| Module | Role | Representative contracts |
|---|---|---|
call_baxter.plugins.system |
local signal source / utility actions | system.heartbeat, log.write |
call_baxter.plugins.telegram |
Telegram ingress/poller + actions | telegram.message.new, telegram.send_message, callback/progress actions |
call_baxter.plugins.http_poll |
HTTP poller + request action | http.check.ok, http.check.failed, http.request |
call_baxter.plugins.docker_watch |
Docker state poller + restart action | container up/down signals, docker.restart |
call_baxter.plugins.mqtt |
MQTT signal source + publisher | mqtt.message.received, mqtt.publish |
call_baxter.plugins.caldav |
calendar/todo poller + mutations | upcoming/start signals, add/complete actions |
call_baxter.plugins.sonic_byte |
local command-backed audio interface | inspect/render/play actions |
call_baxter.plugins.file_out |
bounded local file sink | file.out |
call_baxter.plugins.zrok |
constrained external command interface | zrok.run |
See Plugin system for registration and context contracts and Arbitrary actions and replay safety before composing side-effecting actions.
Separate interface packages¶
Some adapters are packaged independently so their dependencies and release surfaces stay isolated:
- tg-agent-cli is the Telegram projection/index and operator CLI used by the Telegram runtime integration.
- cb-wordpress-plugin is an action sink and Telegram mirror layer for WordPress.
- cb-social-plugin provides independent Bluesky, Mastodon and X action sinks plus a shared Telegram mirror layer.
These packages still register ordinary Call Baxter contracts; they are not alternate runtimes.