Terminal Scripts

Overview

A terminal script is a reusable terminal launch: a name, one or more shell commands, an optional working directory, and a launch mode. Run it from any matching workspace with one click or a keyboard shortcut.

Terminal scripts are different from project lifecycle scripts:

Older versions of Paradev called terminal scripts presets. preset still appears in old links, CLI aliases, and some API and storage fields.

Create a Terminal Script

Go to Settings → Terminal → Terminal Scripts, then click Add Script.

You can also add one from a terminal:

superset scripts add --name dev --command "bun run dev"

Repeat --command for a grouped script. Use --execution-mode to set the layout:

superset scripts add \
  --name services \
  --command "docker compose up" \
  --command "bun run dev" \
  --execution-mode split-pane

To change or remove a script, use its id from superset scripts list:

superset scripts list
superset scripts edit <id> --command "gh pr view --web"
superset scripts delete <id>

superset scripts add --upsert replaces the script with the same name instead of adding a copy. CLI changes reach the app the next time it opens or refocuses with the same organization active, and a running app picks them up immediately. Scripts created in Settings live in the app profile only, so superset scripts list does not show them.

superset presets add remains an alias for compatibility. See the CLI reference for every option.

Launch Modes

• New tab: open the command in a new terminal tab
• Split pane: open grouped commands as parallel panes in the current tab
• New tab with split panes: create a new tab containing parallel panes
• Sequential: run grouped commands in order in one terminal

Import an Agent

Use Import agent in Terminal settings to create a terminal script linked to an agent configuration. The script uses the agent's current command and icon. Edit the launch command in Settings → Agents.

The bundled Claude and Codex configurations default to their most permissive bypass flags (for example claude --dangerously-skip-permissions). Review the launch command in Settings → Agents before importing if you want a stricter permission mode.

Scripts Bar

The Scripts bar appears above terminal tabs and shows visible terminal scripts for one-click access.

• Show or hide a script: use its visibility control in Terminal settings or the gear menu
• Launch: click a script to open it in the current workspace
• Choose a target: right-click to use the current terminal, current tab, or a new tab
• Reorder: drag scripts to change their order
• Manage: use the gear menu to browse scripts or open Terminal settings
• Keyboard shortcuts: press Control+1 through Control+9 to open visible scripts 1 through 9

The bar includes a built-in Paradev CLI script that runs superset --help. Built-in scripts can be hidden and restored, but not edited or reordered.

Workspace Actions

A terminal script can participate in three workspace actions:

• Workspace Run: the Run button launches this script for matching projects
• Workspace creation: launch the script when a new workspace is created
• New terminal tab: launch the script when a terminal tab opens

These are per-script controls. Launching a script from the bar, menu, or keyboard shortcut always works, whatever its workspace-action settings. On v1 desktop builds, the global auto-apply settings (such as autoApplyDefaultPreset, visible in superset settings list) also gate auto-run behavior.

If more than one Run source matches a workspace, Paradev uses the first of these:

1. A project-targeted terminal script marked Use as workspace run
2. The project lifecycle Run command
3. The first matching global terminal script

Keep only one matching script enabled for Run to avoid ambiguity.