Create and run saved scripts
Save a repeatable project command and launch it from Run.
Last updated 16 September 2026
Save a repeatable project command and launch it from Run.
Before you start
Choose a command that already works for this project and understand its working directory. Saved scripts are useful for recurring development tasks such as starting a preview.
The demo saves Preview and Verify as separate named commands. Both Name and Command must be filled before a row can be saved.
Step by step
Select the project and open its Run scripts controls. Inspect existing scripts before adding a duplicate.
Choose Edit scripts… from the Run menu, then Add script. Enter a clear Name and the Command to run. The demo uses Preview and Verify to distinguish its server from its check.
Set the command to match the project’s documented run instructions. The editor has Name and Command fields, not a separate working-directory field. If the command needs a subdirectory, make that explicit in the command.
Save the script and launch it from Run. Read the terminal output and wait for any readiness message before opening the page.
If the command prints a service URL, select it in Preview and verify the expected app appears. Keep the script updated when the project’s run command changes.
What to expect
The project has a repeatable run action with its output available in Choro. Saving a script does not install the command’s dependencies.
Troubleshooting and useful details
If the script exits immediately, read the first error and test its prerequisites. If it starts in the wrong directory, fix the saved configuration rather than repeatedly changing directories by hand. A successful process start does not necessarily mean the service is ready.