install

Additional install commands

macOS

Homebrewverified · 100%

brew install pitchfork

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#pitchfork

nixpkgs package indexes · pkgs/by-name/pi/pitchfork/package.nix · source: api.github.com

overview

Package summary

CLI for managing daemons with a focus on developer experience

Project links

Commands and aliases

pitchfork

history

Project history and usage

Pitchfork is a process supervisor for managing development services and other background daemons from a command-line interface.

Project history

Pitchfork was created by jdx as a developer-focused daemon manager. Its feature set expanded to include readiness checks, automatic restart, directory-aware sessions, scheduled commands, proxying, log management, a TUI, and a web interface.

Adoption history

Pitchfork is available through Homebrew and is designed primarily for developer workstations and project-local workflows.

How it is used

Projects define daemons in TOML files and use commands such as `pitchfork start --all`. Pitchfork can start services when a user enters a project directory, stop them when sessions leave, monitor readiness, retain logs, and retry failed processes.

Why package nerds care

Pitchfork occupies the space between shell background jobs, production service managers such as systemd, and container-based development stacks. Package enthusiasts may value its language-neutral, project-scoped supervision without requiring containers.

Timeline

Early development: jdx created Pitchfork as a developer-experience-oriented daemon manager.
Later releases: project sessions, automatic restart, cron scheduling, proxy routing, structured logging, and cross-platform support broadened its scope.

Related projects

The official documentation compares Pitchfork with systemd, PM2, Docker Compose, and ordinary shell background jobs. It is also part of jdx's family of developer tools alongside mise.

Sources

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for pitchfork. Package metadata is still published here so future coverage has a stable package URL.

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Installs with 1 runtime dependencies.
Build metadata lists 3 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: /etc/pitchfork/config.toml~/.config/pitchfork/config.toml.config/pitchfork.toml.config/pitchfork.local.tomlpitchfork.tomlpitchfork.local.toml

executables

Installed executables

Command	Kind	Exposure	Note
`pitchfork`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-09-19

manager version2.25.0

manager updated2026-09-11

local dataok

upstreamcurrent

latest detectedv2.23.0

https://github.com/jdx/pitchfork

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:pitchfork
Version	2.25.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/pitchfork
Homepage	https://pitchfork.jdx.dev
Repository	https://github.com/jdx/pitchfork
Upstream docs	https://pitchfork.jdx.dev
License	MIT
Source archive	https://github.com/jdx/pitchfork/archive/refs/tags/v2.23.0.tar.gz
Last updated	2026-09-11T17:48:51Z
Pulse	updated
Dependencies	usage
Build dependencies	node, pnpm, rust
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	pitchfork
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

pitchfork

nix profile install nixpkgs#pitchfork

normalized package name match
Matched by: Pitchfork

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/pi/pitchfork/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/pitchfork.yml

Used sources

cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment
pkg.so package database
pkgdb category and tag curation

Install pitchfork with Homebrew, Nix