The
curfew-ctl CLI is in beta. Commands and output may change. The updated CLI beta ships with
the next Curfew release. Run curfew-ctl --help to check the commands supported by your installed
build.Install the command
Homebrew installs Curfew and puts its bundled commands on PATH.curfew-ctl --help.
The installer links the bundled command into ~/.local/bin and adds that directory to PATH for zsh, bash, or fish when needed. Repeating installation preserves existing settings and creates no duplicate PATH entries. The command follows app updates at the same installation path. No source checkout or Swift installation is needed.
Run this command to upgrade a Homebrew installation.
Read information
--json for structured output:
schema_version: 1 and a status such as ok or error.
Collections appear under named fields, including events, reflections, and claims.
Request decisions appear in request_status. A JSON error still has a nonzero exit status.
Keep stderr separate when piping results into another program.
The schedule command shows your saved rules and whether automatic scheduling
is on. It includes pending changes in plain text and JSON. Each time pair is work ends → work resumes. Reflection
output contains your answers; take care when saving it to files or
sending it to another program.
status reports the app’s most recent enforcement observation. It reports unknown when that
observation is missing or stale. Budgets use Curfew’s persisted grant counters and reset rules.
Missing or unreadable runtime state produces an error instead of a remaining budget.Export older reflections
The Journal interface exports only the current calendar week. The CLI can save older entries still stored on this Mac. Run this command after installing the CLI.--days to cover all entries you want to keep. Choose an unused output filename:
the command replaces an existing file at that path. Open the file afterward
and check that it contains the expected answers before uninstalling Curfew.
The file contains private reflection content, so store and share it deliberately.
Request an extension
Curfew processes these requests through its existing approval policy. Check the request status to see whether Curfew granted it. Complete setup and turn on Allow assistants on this Mac in Settings → Integrations first. Curfew must be running to process the request.--id when retrying the same request. Curfew keeps one request
for that ID and rejects a retry with different content. Result lookup reports
pending, approved, denied, or not_found. Add --dry-run to preview an
extension request without submitting it.
If the request queue fills up, run curfew-ctl request prune to preview cleanup
of outcomes older than 30 days. Use --all-resolved to consider newer outcomes
too. Add --apply and confirm to remove the selected records. For scripts,
use --apply --yes. Pending requests and records Curfew needs for recovery
stay in the queue. Save any outcomes you need before removing them.
Request a schedule change (beta)
This example previews a change to a weekday with a time-based rule.--dry-run to submit it through the same approval policy. Schedule changes
follow Curfew’s cooldowns. Use Curfew Settings to edit rules with hours limits.
If Curfew quits before reporting a result, reopen it and check
curfew-ctl request status REQUEST_UUID. Reuse the same --id to retry.
Curfew recovers the saved decision and preserves any later edit.
Protect background work
--dry-run.
Read the audit log
--limit omitted older matching records. Use the original log segments to
verify the audit hash chain. Audit exports can contain private details.
Request an override
The legacyoverride command returns an error. Use
Need to get back in? on the lockout screen for an
emergency override.
Stop an emergency shutdown
Usebreak-glass when a pending shutdown would interrupt urgent work. It preserves
the lockout and its scheduled end. It does not grant an override or unlock the display.
curfew-ctl break-glass --revoke safely removes the release;
add --dry-run to preview removal.
If Terminal reports “no such file,” check the installation path. If reflections
or activity are empty, check the app under the same macOS user account.
Update scripts for schema 1
The next CLI beta returns a JSON object withschema_version: 1 and status on
both success and failure. Collections remain under names such as events,
reflections, and claims. Request decisions use request_status; the outer
status: "ok" means the command completed, even when a request is still pending.
Failures also return a nonzero exit code and print their error code to stderr.
Duration values now use seconds. Update scripts that read these earlier beta
fields:
Human commands still accept minutes. Your saved settings, activity, and audit
records keep their existing formats.