Run Shell Commands from Flow Launcher Safely

Daily use · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

The Shell plugin can launch commands through a configured Windows shell. Confirm the command, quoting, working directory, and privilege level before execution. Test with a read-only command first; a launcher does not make an unfamiliar script safer.

Steps to follow

  1. Open Shell plugin settings and inspect the action keyword and selected shell or terminal.
  2. Try a harmless command such as whoami or echo Flow test, using the configured keyword.
  3. For paths containing spaces, check the quoting rules of the chosen shell. Distinguish CMD syntax from PowerShell syntax.
  4. Use elevated execution only when a specific, understood task requires it. The usage guide documents Ctrl+Enter for Shell commands as an administrator action.
Read-only test commands:
whoami
echo Flow test

Check the result

The command runs in the intended shell with the expected user identity. A quoting test should preserve a multi-word argument as one argument.

Limits and common pitfalls

Do not paste commands that disable protection, download and execute unknown scripts, or erase files. Review a command independently of the launcher before running it.

Make the check repeatable

Release 2.1.4 addresses quoted paths, multi-word arguments, and Windows Terminal command launching. Check your version when reproducing such failures. Capture the exact harmless command and shell choice; redact tokens or private paths instead of posting a command containing credentials.

Questions and answers

Why does a command work in Terminal but fail in Flow?

The selected shell, arguments, working directory, or quoting may differ. Compare those settings rather than assuming Flow uses your current Terminal session.

Sources and scope

Documentation-based guidance, with source review on October 30, 2026. What was and was not tested.

Related guides

Daily use

Configure Web Searches in Flow Launcher

The Web Searches plugin sends a query to a configured search provider and opens the result in a browser. It is separate from local file search. Use a.