Installing and enabling modules

PathWise loads modules from one folder. Installing a module means placing its folder there and pressing reload.

The general shape

PathWise loads every module it finds in one modules folder when it starts up. Installing a module means placing its folder there. There is no separate registration step: if the folder is present and the manifest is valid, the engine loads it.

PathWise reads the folder named modules, relative to its working directory. In the shipped container that resolves to /app/modules. In a source checkout it resolves to the modules folder at the repository root. Point it somewhere else with the MODULES_DIR environment variable or the Modules directory field in Settings, under Modules.

Enabling and disabling a module

Settings, under Modules, lists every installed module with the layer it reads and an on-off switch. The switch saves your choice and shows it in the list.

A module you switch off does not load. It takes no part in investigations, the engine never offers its tools to the model, and it frees the module slot it was occupying. It stays in the list so you can switch it back on, and your choice survives a reload and a restart. You do not have to remove the folder to keep a module out of an investigation.

Picking up a new module

No restart is needed. The Modules panel in Settings has a Reload modules button that re-reads the modules folder while the engine runs, so a module you add or remove is picked up on the next reload.

Checking that it loaded correctly

A verify step checks a module folder before you rely on it. From a source checkout, run npm run troubleshoot -- module verify <folder> from the repository root. From an installation that exposes the PathWise CLI, run troubleshoot module verify <folder>. Replace <folder> with the module folder path.

A valid module prints module at <folder>: OK and its inferred tier. Errors print the reasons and exit with status 1.