Skip to main content
Each Yellowhammer Night belongs to one Project, with local tools executing its author, build, and land Acts. Different Projects can run independent Nights concurrently. Prepare the execution settings before leaving a Night unattended.

Prepare a Night

Rehearse before scheduling

Exercise the real board and Worktrees without dispatching agents or publishing code.

Configure the schedule

Set the Night window and install its scheduled jobs.

Choose agents and routes

Choose workers, fallbacks, authoring, and independent Verification.

Set limits and protected paths

Bound repeated effort and refuse overlapping declared scopes.

A Night at a glance

The author Act selects and prepares a Feature. The build Act coordinates its Work Cards and review. The land Act verifies and publishes eligible results as pull requests. A Project has one Feature in flight at a time, but can advance through multiple Features sequentially in the same Night. The Night Summary reports the result, including Nights that produced no work. The installed LaunchAgents invoke the engine independently of the app. Quitting Yellowhammer does not stop a Night; keeping the Mac available is still necessary. Yellowhammer leaves merging to you.
Planned workflow
Run a Night safely

Show the learning path from rehearsal through schedule, Routes, limits, and Protected Paths.

Planned workflow: rehearse, verify local readiness, review the schedule and Routes, then check limits before unattended runs.

Next steps

Rehearse before scheduling · The lifecycle of a Night