Once you flag a card as successfully installed, you can execute post-setup procedures. These include downloading supplementary plugins, enabling automatic updates, setting startup argument presets, or defining launch behaviors.
Access these configurations using the stepper.postInstall namespace. Call them after invoking stepper.setInstalled(targetDir) in your installation stepper script.
Install supplementary extensions
If your card supports extension directories (e.g. ComfyUI or Stable Diffusion WebUI), you can automate cloning a list of extensions during the installation wizard.
- Method:
installExtensions(extensionURLs: string[], extensionsDir: string): Promise<void>
- Responsibility: Clones an array of Git repository URLs to the specified target directory.
Example
Configure auto-update policies, pre-launch dependencies, execution arguments, and browser parameters.
- Method:
config(configs: ModuleConfigOptions): void
- Responsibility: Saves launch and configuration presets for the card.
Enable automatic updates
Configure whether the card or its installed extensions should check for and apply updates automatically on startup.
Pre-defined arguments presets
You can register custom CLI argument configurations for your card.
Custom launch commands
If you need to execute a custom CLI sequence when running the card, define customCommands to override the default runner commands.
Pre-launch commands and path opening
Execute setup shell commands or open folder locations in the OS file explorer before booting the card process.
Last modified on June 21, 2026