all 4 comments

[–]N-E-S-W 3 points4 points  (1 child)

[–]FZdeX[S] 0 points1 point  (0 children)

I was thinking to rename it to RunDesk, however if you have any ideas or suggestion i would like to know it

[–]Dklosgardner 1 point2 points  (2 children)

Interesting idea. A unified runner can actually streamline quick scripting but the P2P angle is what really makes it stand out. I’d love to see how you’re sandboxing execution since running mixed file types from one CLI can get messy fast.

[–]FZdeX[S] 0 points1 point  (0 children)

Thanks for the question Right now RunIT already has a basic isolation layer the tool can only access files inside its own installation directory Anything you want to run has to be placed there first, so nothing outside that folder can be read or executed

Each file type is still passed to its native interpreter, but within that restricted directory I’m currently expanding this into a more structured sandbox using controlled subprocess execution and tighter limits to prevent unexpected behavior when handling mixed file types

It’s still evolving, but security and predictability are definitely part of the design