Scripts
Save your most-used commands as one-click Scripts with variables, tags, and colours, available across every server you connect to.
Scripts are your personal library of shell commands. Save the things you run all the time (restart nginx, tail an error log, check disk usage) and run them with one click on any server. Scripts live on your computer, not the server, so they follow you around to every connection.
Open the Scripts panel
In the AI Terminal header → Click Scripts (file icon)
A panel slides in showing your saved scripts with a search box at the top. Scripts are stored on your computer and available across every server you connect to.
If you have none yet, you'll see "No scripts yet" with a "Create your first script" link.
Create a script
Open the new-script form
In the Scripts panel header → Click + (New script icon)
The script editor opens.
Fill in the basics
| Field | What to enter |
|---|---|
| Name | A short name like restart-nginx or tail-error-logs |
| Description | Optional. A line about what the script does. |
| Tags | Optional. Comma-separated, helps you filter the list later. |
| Color | Pick a card colour for visual grouping. |
Write the script
In the content area, write your commands. Use {{variable_name}} placeholders for anything you want to be prompted for at run time:
sudo tail -f /var/log/{{service}}/error.logSave
The script appears in the Scripts panel list immediately. It's available across every server, so you only have to write it once.
Run a saved script
Find the script
In the Scripts panel, scroll or use the search box to find it.
Click the Run icon (play)
If the script has no variables, it runs immediately in the terminal. You'll see a success toast when it finishes.
Fill in variables (if any)
If the script uses {{variable}} placeholders, a Run Variables modal opens with a text input for each one. Fill them in and click the Run button (green) to execute.
See the output
The command runs in the terminal area. Output appears live. A success toast confirms "<script_name> completed". If it fails, the toast says "Script failed, check terminal output".
Tips
Save your three most-used troubleshooting commands as Scripts (tail -f your app log, pm2 restart, df -h). One click beats typing them out every time.
Use tags to group scripts by domain (nginx, db, monitoring) and filter the list with the search box when you have a lot of them.
Use {{variable}} placeholders liberally. A single tail-log script with a {{service}} variable beats writing one script per service.