Skip to content

Plugins

A plugin teaches the app something new; Library items only rearrange and style what the app already does.

Example: a plugin adds an importer for an app Kaizendex does not support yet. It asks to write to your Workouts collection and to call one website. You approve both, and your old runs arrive as entries.

What a plugin is

A plugin is a folder in Settings/Plugins/, for example Settings/Plugins/Pomodoro/. Any editor, or a coding agent such as Claude Code, can open it. It has up to three parts:

Part What it holds In a Pomodoro timer
The manifest (plugin.json, the plugin’s label card) Its name and version, the slots it fills, the permissions it asks for, the websites it may call (none by default), its speed budget, and the contract number: the version of the plugin rules it was written for. “Pomodoro”; slots topbar.end and panel.right; may add entries to Focus; no websites
A screen part (optional) Settings in the house JSON language and skins, drawn by the app’s own parts; or free HTML and JavaScript in a sealed frame. the pill 🍅 24:59 and the panel
Logic (optional) Code in a sealed box (see Fast by design). count down; at the end, log a session

Where a plugin shows up: slots

A slot is a named place where a plugin can add something. The app’s own buttons, panels and commands use the same slots, so a plugin is one more entry in the same list.

Slot What a plugin adds there
topbar.end a small pill or button at the right of the top bar
sidebar.section a section in the left sidebar
panel.right a panel in the right sidebar
page a new tab in a hub, or a new page
view a new view kind next to table, board and calendar
block a new block for dashboards and Block pages
card.button a button on cards
property.editor a new way to show and edit a property
command a command in Ctrl+K
automation.trigger, automation.step a new “when” or a new “do” for Automations
agent.tool a new tool for your agents
importer a new importer (a connector is an importer that runs on a schedule)
settings.page the plugin’s own settings page
The app window with five slots marked: a timer pill at the end of the top bar, a section in the left sidebar, a new tab on the page, a button on a card, and a Pomodoro panel in the right sidebar.top bartopbar.end24:59left sidebarHubsCollectionsHabit streakssidebar.sectionTableFocuspageWorkoutsMorning run5.2 kmFocus on itcard.buttonPomodoropanel.right24:59Task: Write reportToday: 3 sessions
Five slots in the app window. The app draws the frame around each one.
  • The app draws the frame around every slot. A plugin panel opens, closes, resizes, docks flush to its edge and remembers its size like a built-in panel. It also follows your theme’s colours and keyboard focus. The plugin needs no code for this.
  • A plugin lives in the app’s frame, not in one page. A running timer keeps running when you change pages.
  • Protected screens are never a slot. A plugin cannot reach inside the app’s own screens. It adds things in slots, and restyles named parts only through designs, like anyone else.
  • On a phone, the same plugin shows in the matching place: a right panel opens as a sheet, and a top bar pill shows at the top. A plugin that needs a desktop-only slot says so in its manifest. On iPhone, Apple’s rules add limits: you agree to each plugin, plugin code gets no phone features, and there is a public list where you can report or block a plugin.

Example: a Pomodoro timer

  1. You tell the AI: “Make a Pomodoro timer in the top right. When a session ends, log it in my Focus collection.”
  2. If you have no Focus collection, the AI makes one with three properties: Start, Length and Task.
  3. The AI makes the plugin: a pill in topbar.end and a panel in panel.right with the timer, the task, today’s sessions and the 25 and 5 minute lengths.
  4. The app runs the speed test on your data. The grade is Fast. The plugin shows live, and you keep it or undo it.
  5. You start a session. The timer stores the start time, not a ticking count, so it is right even after you close the app.
  6. The session ends. The plugin asks the engine to add an entry to Focus. The first time, the app asks: “Pomodoro wants to add entries to Focus. Allow?”
  7. On your phone, the timer shows as a pill at the top.

Your own plugins and other people’s

Made by Review How it switches on
You or your AI, in your account none The app shows what it reads, writes and calls, and you switch it on. Code the AI wrote waits for your Approve.
The Library or another person Every version is scanned. “Verified” only after our review. A person reviews protected permissions. It arrives off. You approve its permissions in plain words. Updates are pinned, and the kill switch applies.

Either way, a plugin runs only on your own devices and in your own cloud box. You can change its permissions later in Settings → Plugins.

To make one, choose Customize this in the ⋯ menu of any part of the screen. A chat opens with a request already drafted; you edit it and send it. The AI asks the app for the live list of slots, name tags, theme tokens, commands and your collections, so it writes against what really exists. A plugin file changed by another program waits until you choose Use it.

Fast by design

A plugin should run as fast as a built-in feature. The AI tries these in order and uses the first that works:

  1. No plugin at all. The app’s building blocks (collections, properties, views, Automations, designs) already do it. The Pomodoro’s log is a plain Focus collection.
  2. JSON screens and skins. The app’s own parts draw the plugin, so it runs at built-in speed, also on big collections.
  3. Code, in the right box:
    • a sealed worker for most logic: a background helper with no internet, no app storage and no screen, running at full browser speed;
    • compiled code (WASM) for heavy work, close to the engine’s own speed;
    • the small sealed engine only for tiny scripts that must start fast, such as card scripts.

Speed rules for every plugin:

  • Heavy work (search, totals, sync) stays in the engine. A plugin asks for the result.
  • One sealed frame per panel or block, never one per card or row.
  • Nothing loads until you use it. No plugins means no cost.
  • A click never waits for a plugin.
  • Each run has hard limits on time and memory. A run that goes over is stopped, and the default look stays.

The speed grade

Before you switch a plugin on, the app runs it on your real data in the background. It measures the start time, the time per event, the memory, and the frames it drops while you scroll. Then it shows a grade: Fast · OK · Slow. The limits for each grade are measured on a 3-year-old Android phone.

  • Slow shows a warning that says what is slow, for example “adds 40 ms to every tick in Habits”. You may still switch it on.
  • Fix with AI is offered with every Slow grade.
  • A plugin your AI makes is tested and fixed before you see it.
  • After it is on, the app keeps measuring. If a plugin turns Slow later (for example, your data grew), the app tells you once and offers Fix with AI. Settings → Designs shows each plugin’s grade and cost.

If a plugin breaks something

  • Safe mode turns off every plugin and design. It also starts by itself after two failed starts, on desktop, web and phone, and keeps a backup of what was on.
  • Find the problem turns half the list off, then half again, until it finds the bad plugin.
  • Your data is safe. Every write goes through the engine’s one write path: it shows in history, you can undo it, the pause before a mass delete applies, and a protected change still needs your own check on your device. A plugin can break how your app looks, but it cannot change your data past Undo.

How a plugin stays safe

Unlike an Obsidian plugin, a Kaizendex plugin cannot touch your whole computer.

A plugin runs inside a sealed engine. It can reach only what its approved permission list allows, and every change goes through the app’s one write path.Sealed enginethe pluginno direct accessPermissionsyou approvedshown in wordswrite Workoutsvia the one write pathcall one websiteonly from its list
A plugin reaches only what you approved.
Rule What it means
Sealed code Plugin logic runs in a sealed box: a sealed worker, compiled code (WASM) or the app’s small sealed engine. Plugin screens run in sealed frames, loaded from a separate web address.
Permissions you approve Which collections it may read or write, which websites it may call, which secrets it may use, and whether it may touch a folder on your computer. Shown in plain words before you install. You can change them later.
No websites by default A plugin lists the websites it may call. With no list, it calls none.
The same door as you Every write goes through the app’s one write path, so it shows in history and you can undo it.
Verified A plugin gets the “Verified” badge only after Kaizendex reviews and signs it. Every version is scanned. A person reviews any plugin that asks for a protected permission.
Unsigned plugins from other people need developer mode and show a clear warning. Your own plugins do not.
Pinned updates A new version shows what changed, in its code and its permissions, before it installs.
Kill switch If a plugin turns out to be harmful, we revoke its signature and it switches off on every device that has it.

Connectors are plugins

A connector brings data in from where it already lives. It says what the data is, how to connect and how often to fetch. The data lands in ordinary collections, with the raw data kept, so search, privacy and your folder work on it like any other entry. Mail and calendar connectors are future plugins. Google Health is the first connector; see Connectors.