1. Run the downloaded installer
bash install.shReview the script, then run it. It installs to a user-local destination, validates prerequisites, and prints PATH guidance. On Windows, run install.ps1 in PowerShell instead.
Website-owned release downloads
Install Day Shift and plan your first handoff in minutes.
Download a checked release, initialize a repository, and hand your first scoped task to a coding agent. Everything runs locally: no signup, no license file, and no online activation for evaluation.
Quickstart
Three steps from download to first agent handoff.
Canonical documentation owns the detailed verification, installation, and PATH procedure; this is the short path.
2. Initialize your repository
day-shift init
day-shift doctorRun inside any git repository. init creates the .day-shift workspace beside your code; doctor confirms the workspace is healthy before any planning starts.
3. Plan your first handoff
day-shift spec add --entry-file .day-shift/specs/spec-entry.<name>.jsonRegister a spec, break it into implementation-sized tasks, and hand the task definition to the coding assistant you already use. Evidence lands back in the repository.
What appears in your repository
One visible workspace directory, nothing hidden.
Day Shift stores every artifact as plain files in your repository so humans and agents can read, review, and version them.
.day-shift/config.toml
Marks the repository as an initialized Day Shift workspace.
.day-shift/specs/
Durable intent: the specifications your planning traces back to.
.day-shift/planning/
Slices, phases, milestones, task definitions, and implementation summaries.
.day-shift/workflows/
Guided workflows, including the canonical first-project walkthrough.
Release assets stay here
Archives, installers, manifests, checksums, and release notes remain versioned website-owned release outputs.
Detailed guidance lives in docs
Use the canonical installation page for exact-version selection, verification, platform execution, PATH checks, and next steps.