Skip to content
Khadim Plugin SDK

Plugin SDK Overview

Khadim plugins let you add new tools to the app without changing the core runtime. A plugin is packaged as a WebAssembly module plus a plugin.toml manifest that describes metadata, config, permissions, and optional desktop UI tabs.

What a plugin contains

Section titled “What a plugin contains”
  • plugin.toml for metadata, configuration fields, and permission declarations.
  • plugin.wasm for the compiled plugin code.
  • Optional ui.js and [[ui.tabs]] manifest entries for desktop plugin panels.
  • Optional source files and build scripts used to produce the final WebAssembly bundle.

What plugins can do

Section titled “What plugins can do”
  • Register one or more tools that the host can call.
  • Read plugin config values provided by the app.
  • Use host capabilities such as HTTP or filesystem access when permissions allow it.
  • Add desktop sidebar/content tabs by registering custom elements from a plugin UI bundle.
  • Stay isolated from the main application process behind a narrow host API.

Plugin author workflow

Section titled “Plugin author workflow”
  1. Start from one of the example plugins in examples/plugins/.
  2. Edit plugin.toml to define the plugin identity and permissions.
  3. Implement your tool behavior in AssemblyScript or Rust.
  4. Build plugin.wasm.
  5. Install or copy the plugin into the Khadim plugins directory.

Docs map

Section titled “Docs map”