Release notes, part 2: 0.7 and the plugins from outside
MakeKeeper has always been built out of plugins: projects, inventory, storage, logistics, chat and the rest are each a self-contained module, and turning one off removes exactly its functionality. Until 0.7.0, on 31 July 2026, that door only opened inward. This release opened it outward — a plugin can now be a separate program, in its own container, written by someone who has never seen the core’s source.
It was the largest release of the summer by a wide margin, so here is what it actually gives a plugin author.
Screens without shipping frontend code
A plugin describes its interface declaratively and the app draws it. That means no bundle to compile into the frontend, no version of the framework to match, and a screen that keeps the user’s theme and language for free. It also means the core can put a budget on what a plugin renders and stop calling one that misbehaves.
Tools the assistant may call
A plugin can offer tools to the AI assistant. They are always opt-in per plugin, and anything destructive is gated behind a confirmation rather than trusted.
Events, instead of polling
Plugins can subscribe to things that happen — an order arriving, a record being deleted — delivered as signed webhooks with a delivery queue behind them, so a plugin that was asleep does not miss what happened while it was.
Pairing, not config files
A plugin container announces itself on the network. The administrator switches the app into pairing mode and types a four-digit code shown by the container. There is nothing to edit and no token to copy by hand. Each plugin’s settings then live in the plugin’s own card, next to the switch that turns it off.
Five plugins to read
They ship as examples, and each one exists because it demonstrates something different: a workshop climate monitor with a public page of its own, live currency rates pulled from the ECB, a notes plugin and a Telegram bot that both have to tell users apart, and a bridge to a Bambu Lab printer through Home Assistant. There is an SDK and an author’s guide to go with them.
Next: part 3 — the phone joins the workshop. Previously: part 1 — 0.1 to 0.6. All of it is free to self-host, under a source-available licence.