docs how pastor works today
Short pages, one topic each, for people learning pastor. New here? Start with install and first run. The concepts explain each part, deployment modes show how to set it up, and the examples are real workflows to copy.
Then pick what you came for. Each page does one thing from start to end: another machine to share the load, a PR fix round from one command, urgent work first with priorities and the queue, a job every morning on a schedule, board cards that become branches, and a sandbox for untrusted work.
start
install, a first run, and how it fits together
- installone binary, and herdr on each machine
- first runone machine, one task, one answer
- architecture overviewthe parts and how they talk
concepts
what each part is and how it behaves
- headthe one pastor serve that keeps track
- machineswhere agents run
- flocksgroups of machines that keep work apart
- tasksone prompt, one agent, one machine
- queue and prioritywho runs next when machines are full
- jobswork that finds itself on a schedule
- connectorssmall programs that find work
- agents and modelswhich coding agent a task starts
- profiles and trustwhat an agent may do, and where
- orchestratorsagents that watch other agents
deployment modes
one machine, many, or a head elsewhere
- soloone machine is the head and the worker
- flocka head plus machines over ssh
- remotethe CLI here, the head somewhere else
- as a servicekeep the head and herdr running
examples
real workflows, with the config to copy
- hand board cards to agentsa tagged card becomes a branch
- answer questions in a notean agent carries out your answer
- a PR fix roundreview comments fixed from one command
- urgent work firstpriorities, the queue, preempting
- a job every morninga schedule that starts an agent
- untrusted work in a sandboxoutside PRs and issues, away from your credentials
- keep PRs moving overnighta night watch that merges what is ready
- let your agent drive pastorthe skill, JSON, and orchestrators
reference
commands, files and events to look up
- clievery command, argument and flag
- pastor.tomlthe head's settings and defaults
- flock.tomlflocks and machines
- job filesone TOML file per job
- eventswhat happened, and when