# open-cli-tools/concurrently

Run commands concurrently. Like `npm run watch-js & npm run watch-less` but better.

Repository: https://github.com/open-cli-tools/concurrently
Canonical: https://ross.abutalabs.com/products/concurrently
Homepage: https://www.npmjs.com/package/concurrently
Language: TypeScript
License: MIT
License Family: permissive
Topics: cli, command-line, concurrently, parallel, process, spawn
Last push: 2026-08-18T10:03:34+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 98, longevity 100
- inputs: {"age_days": 4227, "days_push": 15, "days_rel": 18, "gap_med": 16, "n_releases_24m": 16}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 7839, forks 278 (observed 2026-08-28T04:10:06.153887+00:00)

## What it is
concurrently is an npm-distributed CLI tool (written in TypeScript) that runs multiple shell commands in parallel from a single terminal, with prefixed output to keep interleaved logs readable. It is cross-platform including Windows, and supports options like --kill-others to terminate all commands when one exits or fails.

## Use cases
- run multiple npm scripts at the same time
- run frontend and backend dev servers together from one terminal
- run watch tasks in parallel like watch-js and watch-less
- kill all background commands when one process fails
- read parallel command output with per-command prefixes
- run multiple commands concurrently on Windows where shell & behaves differently

## When to choose
- you need to run several long-running commands (watchers, dev servers) in a single terminal
- you want readable interleaved output from parallel processes with prefixes and color coding
- you need cross-platform parallel command execution in npm scripts, including Windows
- you want all spawned processes terminated when one exits unexpectedly (--kill-others)

## When to avoid
- you only need simple backgrounding on POSIX shells where &, wait, or job control suffices
- you need dependency-aware task orchestration, sequencing, or caching rather than pure parallelism (consider a task runner like Make, nx, or turbo)
- you are orchestrating containers or distributed services rather than local shell commands
- your environment has no Node.js runtime available to install and run the tool

## Facets
- artifact type: cli-tool
- maturity: stable
- function: cli, concurrency, developer-tools
- domain: developer-tools, web-development
- platform: cross-platform, cli, windows
- tags: process-management, npm-scripts, parallel-commands, command-runner, spawn, prefix-output, kill-others, watch-tasks, dev-servers, command-line, automation, nodejs, linux, macos

## Member repositories
- open-cli-tools/concurrently (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:06.153887+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:33:58.092652+00:00, confidence not recorded.
  - readme: https://github.com/open-cli-tools/concurrently (fetched 2026-08-28T04:10:06.153887+00:00, sha a34c361855c2)
  - registry_npm: https://registry.npmjs.org/concurrently (fetched 2026-08-29T08:30:45.403855+00:00, sha ceb8f2979849)
- Data as of 2026-08-30T08:39:29.467469+00:00.
