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

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

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).

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

Override the web frontend's request principal with the host OS user ($USER).

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

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

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

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

Mock LLM provider for customer services scenarios. Always helpful, never useful.

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

Diagnostic plugin: registers a hook on every channel (screen/contribute/toolcall/toolresult/followup) and console.logs when each fires. For exercising and debugging the hook pipeline.

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

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

Node filesystem-backed FileStore for MIME-typed blobs, served by the frontend.

Cross-runtime skill documents: CRUD over named markdown playbooks via skill_action, persisted and knowledge-indexed. Runs in Node and the browser.

Run prompts in detached background processes. Schedule recurring prompts with every/every_list/every_cancel/every_suspend/every_resume/everything_suspend/everything_resume.

In-process browser chat frontend: renders to the DOM and drives the session runner directly (no HTTP/SSE server).

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).