matbot plugin API: the singleton contract every matbot plugin builds against — MatbotPlugin, the service registry, hooks, principal carrier, and shared types.

Anthropic Messages API provider adapter with streaming, tool use, and extended thinking; also handles DeepSeek's Anthropic-compatible API.

matbot core runtime: agentic loop, hook dispatch, plugin loader, config, security, and knowledge. Exposes ./providers-base and ./storage-base for plugin authors.

OpenAI-compatible chat completions provider adapter (OpenAI and any compatible endpoint) with streaming and tool calls.

matbot CLI: interactive REPL and single-turn runner for the matbot AI harness, with hot-loadable plugins.

Built-in `plugin` and `provider` tools for managing plugins and LLM providers at runtime — install, remove, reload, and discover.

Cross-platform MCP client: connect to remote MCP servers over HTTP/SSE and register their tools. Runs in the browser and Node (fetch only, no child processes).

Telegram bot frontend

Node skills plugin: embeds @matatbread/matbot-skills CRUD and adds a local filesystem (.md) import + watch.

Replaces the bash tool with a persistent Docker container (exec-based). Project root is read-only at /app; .data is read-write.

Self-contained, browser-only matbot: assembles the platform-neutral core and browser plugins into a single matbot.html that runs entirely client-side (file:// or any static host).

Data-driven hooks: stored conditions that, when an LLM classifier judges them matched, invoke a tool. Cross-runtime (node + browser).

Browser-native backends for the web frontend: an IndexedDB Store, an OPFS file store, and a WebCrypto-backed vault.

Persistent KnowledgeIndex backed by a Store, with entity/heading search and optional BGE reranker.

Session-management tools: list, get, rename, and hide conversation sessions.

Define named stores and expose generated CRUD tools over them via store_action. Cross-runtime (node + browser).

Run bash scripts in the session workspace.

Filesystem-backed StorageBackend for Node — content-addressed and CAS-safe; the CLI's default store.

Make HTTP requests (method, headers, body) to web APIs and remote resources; requires the network capability.

ChatJimmy provider adapter — a very fast hosted llama endpoint, handy for odd-ball / latency tests.