Best forSelected shell commands
ResultRuns in Terminal/iTerm
InternetNot required

What Run in Terminal does

ActionClip recognizes common commands, path invocations, shell operators, environment assignments, and user-added command names. Blocked rules stop matching commands; alert rules require confirmation first.

How to use it

  1. Select a shell command you intend to run.
  2. Choose Run in Terminal.
  3. If an alert rule matches, review and confirm it. ActionClip then runs the command in the configured terminal destination.

Example

Selected command

git status

Destination

Runs in the selected Terminal or iTerm tab/window

Settings

Open the action's settings from:

ActionClip Settings → Actions → Run in Terminal → gear
ActionClip Run in Terminal settings showing terminal target and recognized commands
Run in Terminal keeps its destination, recognized commands, and safety rules together in one scrollable sheet.

Terminal

Choose where the selected command should run.

  • Current tab
  • New tab
  • New window

Recognized commands

Add one custom command name per line so ActionClip can recommend this action for your own tools.

  • Example: mycli
  • Example: deploy

Blocked rules

Add one case-insensitive pattern per line. Matching commands never run. Wildcards * and ? are supported.

  • Default: rm -rf
  • Default: curl * | sh

Alert commands

Add patterns that should display a confirmation before execution.

  • Default: sudo
  • Default: brew install

Display

Choose how this action appears in the floating widget. This changes only its presentation, not what it does.

  • Icon with Label
  • Icon only
  • Label only

Changes are saved automatically.

You can also replace this action's icon from ActionClip → Actions. See change an action icon.

When ActionClip suggests it

It is promoted when the cleaned selection is non-empty, at most 1,000 characters and eight non-empty lines, and resembles a recognized shell command.

Enabled actions remain available in your Actions list even when Smart Suggestions do not promote them for the current selection.

Requirements and privacy

  • Works locally and does not require Online Actions.
  • Command execution is always triggered by an explicit user-selected command.
  • Review selected commands before running them; custom blocked and alert patterns are part of the safety policy.
Back to all built-in actions