You can now create Swif commands in the Web App that pull your scripts directly from a Git repository and execute them via our Makefile runner, across Mac, Windows, and Linux.

This release also introduces a clearer command‑creation flow with three execution options: Run by Command Script, Run by File, and Run by Git Repo.

What’s new

1. New execution types in Command creation

When you go to Commands → Create new command, Step 1 is now organized into:

• Basic Information

• Execution Type

• Execution Settings

Under Execution Type, you’ll now see:

1. Run by Command Script (existing behavior, unchanged)

   • Same custom script flow you used before.

   • Now includes a Run Security Risk Analysis action in the UI.

2. Run by File (new)

   • Paste or upload a single script file (e.g. .py, .js, .go, .sh) and run it directly.

   • Filename and File content are required; you can’t proceed without both.

   • For this mode:

     • Run Schedule, Command status, and Webhook configuration are hidden to keep it focused on ad‑hoc runs.

   • Includes an inline Security Risk Analysis notice.

   • Review step shows a dedicated Run by File summary.

3. Run by Git Repo (new)

   • Connect a Git repository and run commands via a Makefile target.

   • You configure:

     • Repository URL (and provider, if applicable)

     • Branch

     • Path / Makefile location

     • Target (Makefile entrypoint)

   • All required Git/Makefile fields validate and block progress when missing or invalid.

   • For this mode:

     • Run Schedule, Command status, and Webhook configuration are hidden.

   • Review step clearly summarizes:

     • Repo URL and provider

     • Branch

     • Path / Makefile and target

     • Any platform‑specific execution settings

Full user help is available here:
Run Commands by Script, OSQuery, File, or Git Repo | Help Center | Swif.ai

2. Cross‑platform support (Mac, Windows, Linux)

Git + Makefile commands are now supported from the Web App for:

• Mac

• Windows

• Linux

For all three platforms:

• You can create a command that:

  • Uses a Git repo as the script source.

  • Uses the Makefile runner as defined in the underlying backend work (ST‑7296).

• The UX and field set are consistent across OSes, with platform‑specific nuances (paths, shells, prerequisites) reflected in helper text or copy where relevant.

• A prior issue where template‑based commands did not correctly create Mac variants has been fixed; templates that show all three OS configurations now create commands for Mac, Windows, and Linux as expected.

3. Execution, status, and error handling

When you execute a Git‑backed command from the Web App:

• Swif dispatches the run via Makefile runner for the selected platform(s).

• The existing command/job detail view shows:

  • Normal status progression (queued → running → succeeded / failed)

  • Logs and output from the run

• Git / Makefile specific errors (e.g. bad repo URL, missing branch, or Makefile target not found) are surfaced as clear, user‑friendly messages, rather than opaque generic failures.

Learn more at Run Commands by Script, OSQuery, File, or Git Repo.