cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

JMP Wish List

We want to hear your ideas for improving JMP. Share them here.
Choose Language Hide Translation Bar
0 Kudos

Safe mode - for Vibe Coding

☑ cool new feature
☑ could help many users!

☑ removes something that feels like a „bug“

☐ nice to have

☐ nobody needs it

 

#myTop10_2026

 
 
What inspired this wish list request?
While using Vibe Coding to generate and run JSL, I want to ensure that automatically produced code cannot accidentally perform destructive file operations. AI‑generated code is extremely helpful, but it can also introduce commands such as deleting directories or modifying files without the user noticing. Just think of 
  • Delete Directory(...)
  • Delete File(...)
  • Rename File(...)
applied to the main data storage directory of your company - You will get famous!



What is the improvement you would like to see?
I would like JMP to provide a JSL‑controllable Safe Mode that can be enabled programmatically with a shortJSL command - but can only be disabled after explicit user confirmation via a modal dialog (a dialog that cannot be bypassed or confirmed through JSL). While Safe Mode is active, JMP should intercept potentially destructive operations (e.g., deleting files or directories, renaming files, or similar filesystem‑modifying actions) and require user approval before execution. Which action is destructive? Just list the common 40 in the preferences - and let the user decide.
 
 
Why is this idea important?
This feature would make Vibe Coding for JMP/JSL significantly safer by preventing unwanted file deletions or modifications when experimenting with AI‑generated scripts. It reduces the risk of data loss, increases user confidence when testing automatically generated code, and provides a controlled environment in which potentially dangerous actions can only occur with clear user intent.