> ## Documentation Index
> Fetch the complete documentation index at: https://yellowhammer.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure the schedule

> Understand the scheduling choices for local unattended Nights.

Yellowhammer's schedule generates three local LaunchAgents per Project: author, build, and land. Choose the Night window, install the jobs, and verify them before relying on unattended execution.

## Choose the timing window

Open **Settings**, choose the Project, and select **Configuration**. Under **The Night**, edit **Starts**, **Ends**, and **Build every**, then choose **Save**.

| Setting | Default | Meaning |
| - | - | - |
| Starts | 22:00 | The configured start of the Night window. |
| Ends | 06:00 | The configured closing time; the window can cross midnight. |
| Build every | 15 minutes | The interval used to generate periodic Act firings. |

The generated LaunchAgents use the Mac's local calendar time. There is no per-Project timezone selector. The time pickers display the stored hour and minute without converting them to another zone. Equal start and end times are refused because a 24-hour window cannot close its Night unambiguously.

Setup records a per-Project `stagger_minutes` offset so Projects need not fire together. It assigns offsets in three-minute steps; the recorded offset stays with the Project. Actual firings add that offset to the configured window.

The author Act fires at the start. Periodic land ticks are followed by build one minute later and author two minutes later when the interval permits; the offsets shrink for one- or two-minute intervals. This allows a landed Feature to be followed by another Feature within the same Night. A closing land firing runs at the end. Later flush firings at 15 minutes, one hour, and three hours after closing retry pending board delivery when they fit before the next Night.

## Install and check the schedule

Saving schedule changes regenerates that Project's already installed LaunchAgents. Read the regeneration result shown in **The Night**; a saved configuration and a successful job installation are separate results. Exported launchd or cron files must be exported again after a change.

To install jobs from saved configuration, use:

```bash theme={null}
yh setup --install-jobs
```

This operation installs jobs for eligible configured Projects. To inspect the illustrative Project afterwards:

```bash theme={null}
yh doctor --check launchd --project acme-checkout
yh status --project acme-checkout
```

The jobs are named `dev.yellowhammer.<project-id>.author`, `.build`, and `.land`. Their logs are under `~/Library/Logs/Yellowhammer/`, named `<project-id>.<act>.log`.

## Keep the Mac available

Keep the macOS account logged in, the Mac awake, local repositories available, and network access available to Linear, GitHub, and your agents. The app itself can be closed. Schedule installation does not arrange a wake time. If the Mac slept through a Night, use `yh status` to inspect its sleep history and missed-Night diagnosis before running work manually.

Setup records the tool search path in the scheduled jobs. If a tool works in your interactive shell but fails overnight, check its configured executable and regenerate the jobs after fixing the path.

## Confirm it worked

The launchd check should show the expected Project jobs without failures. Review `yh status` for job state and recent invocations. After the next window, inspect the Project's Night Card and Summary.

## Next steps

[Choose agents and routes](https://yellowhammer.dev/docs/run/choose-agents-and-routes.md) · [Troubleshoot Nights and missing results](https://yellowhammer.dev/docs/reference/troubleshoot-nights-and-missing-results.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.