Some pipeline jobs need to run more than once with different values: the same check for several target configurations, or the same agent step with Claude and with Codex. Version 1.1.0 of the Unstoppable desktop app adds matrix jobs to pipelines, in the shape GitHub Actions uses: list the values, and the job runs once for each combination.
Write a matrix
Put a strategy on the job. Each key under matrix is an axis. The job expands into one variant per combination, and each variant sees its own values as matrix.<axis>:
jobs:
process:
strategy:
matrix:
os: [macos, windows]
provider: [claude, codex]
exclude:
- os: windows
provider: claude
include:
- os: linux
provider: codex
experimental: true
max_parallel: 3
fail_fast: false
name: ${{ matrix.os }} / ${{ matrix.provider }}
steps:
- id: emit
run: echo "target=${{ matrix.os }}-${{ matrix.provider }}" >> "$PIPELINE_OUTPUT"Expansion is predictable: every combination in the order the axes are declared, then exclude removes matches, then include adds or extends variants. Here, four combinations minus the excluded one, plus a Linux variant, makes four variants.
Two settings control the run:
max_parallelcaps how many variants run at once, from 1 to 256. A variant paused for input gives up its slot.fail_fastis on by default and cancels the group's unfinished variants when one fails. Set it tofalseto let every variant finish.
Names, conditions, environment and continue_on_error resolve per variant, so continue_on_error: ${{ matrix.experimental == true }} tolerates failure only in the variants you marked. A job that needs the matrix job waits for every variant.
Build the list at run time
The matrix doesn't have to be written by hand. An earlier job can output JSON, and the matrix can read it:
strategy:
matrix: ${{ parseJson(needs.prepare.outputs.matrix) }}
max_parallel: 4Single axes and the include and exclude lists can be expressions too. Expansion is all or nothing: invalid JSON, the wrong type or too many variants creates none, and the group shows Expansion failed with Retry expansion.
Watch and retry variants
The run view groups variants under their job, with the variant count and the Max parallel and Fail fast settings. Cancel variant stops one that is running. Once the run and the group have finished, Retry all variants, Retry failed variants and Retry variant rerun only what you choose and keep the variants that succeeded.
Several variants, or several jobs, can also wait for input at the same time, and you answer each one separately or all together. Before 1.1.0, a pipeline could wait on only one input at a time.
Where it stops
A run can generate at most 256 variants across all its matrix jobs. Axis values are data: os: windows does not move a variant to a Windows machine. Variants share one checkout and output directory, so two variants writing the same file can collide; put a matrix value in artifact paths. Matrix jobs replace the older foreach field. A pipeline that still uses foreach or a top-level max_parallel is rejected with a message pointing to strategy.matrix, so it needs rewriting; the pipeline-writing skill bundled with the app documents the new syntax for agents that edit pipelines.
Tommy Irish built matrix jobs.
Update (2026-11-13): The retry buttons now read Try all variants again, Try failed variants again and Try variant again. Cancel variant is unchanged. Runs are now on the Workflows page.
Try it
Matrix jobs are in version 1.1.0 of the Unstoppable desktop app. Download it and add a strategy.matrix to a pipeline job.
