Malbox provides extensive configuration options for controlling how plugins operate. Both the plugin system itself and individual plugins can be configured to fit specific use cases and requirements.Documentation Index
Fetch the complete documentation index at: https://docs.malbox.app/llms.txt
Use this file to discover all available pages before exploring further.
Plugin Types
Plugins can run either on the host system or inside a sandboxed (guest) environment. This choice affects isolation, performance, and what resources the plugin can access.Execution Contexts
Execution contexts define how plugins coordinate with each other during task execution. Some plugins need exclusive access to resources, others can run alongside compatible plugins, and some have no coordination requirements at all. Choosing the right execution context balances isolation needs against throughput.State Management
State management controls how plugins maintain data across their lifecycle. Plugins can be completely isolated between tasks, share state globally, or selectively share context with specific plugins or tasks. The right choice depends on whether your plugin benefits from persistence (like keeping ML models loaded) or requires clean state for each execution.Runtime Configuration
Guest plugins carry their runtime settings in the[runtime] section of their plugin.toml. The SDK bakes these values into the plugin binary at build time.
To change a runtime setting, edit plugin.toml and rebuild the plugin. See the Plugin Configuration Reference for the full field list and defaults.