Auto-discovery for local custom actions

[ChemistAion]

It would be very useful if custom actions could be automatically discovered from the current session directory, for example by picking them up from an "actions" subfolder within the session.

...I believe something like this may have been mentioned before, but I could not find the reference.
This would significantly improve usability when working with local or session-specific setups.

[ChemistAion]

...to add some context, e.g.: I currently have a "workbench" directory with multiple side-by-side sessions, some containing its own custom-actions inside an "actions" subdirectory; at the moment, I need to copy or sync these into the global gpupad "actions" directory (via scripting), which pollutes(!) the global scope.

It would be much cleaner if the tool could automatically pick up custom-actions from the current session directory.

Even better, if these could be optionally exposed in the UI (e.g., bound or placed in the toolbar), that would significantly improve the workflow.

[ChemistAion]

It would also be great if the usage of such "local" custom-actions could be preserved within the session itself.

For example, storing the last used settings and making them available by default when the session is reopened, if those actions were used previously. This would make session-based workflows more consistent and reduce the need for repeated setup.

[houmain]

Thank you very much for the valuable input and helping with advancing the custom action capabilities!
Session local actions and saving/reapplying active actions in the session state are implemented now.
Next I will think about a way to store action specific data to the session/items.

[ChemistAion]

Super happy to help 🖖🏻 really appreciate the time you put into implementing this, and the tool overall.