Open-source macOS public beta candidate

Bring your desk back, deliberately.

Save available values from seven display and sound setting kinds as a local profile. Review the exact plan before you apply anything.

  • Local only
  • No account
  • No cloud
  • No auto-switching
Public beta in preparation · no supported download yetView source on GitHub
Synthetic empty tray with the Capture Current Settings action

Current profile scope

Display + Sound

  • Main display and resolution
  • Output device, volume, and mute
  • Input device and volume

Seven settings · no Network or automatic switching

Synthetic product data · no personal device identifiers

One decision at a time

Capture → Edit → Review & Apply

Nothing switches automatically. Each step has one clear purpose, and Apply remains a separate confirmation.

01

Capture

Read the Mac’s current Display and Sound values into a local profile. Capture itself changes nothing.

02

Edit

Name the profile and set any available values across the seven current settings. Missing values stay absent.

03

Review & Apply

Inspect planned changes, omissions, and risk. The Mac changes only after the separate Apply Profile or Apply Available Settings confirmation.

Honest support boundary

Two areas. Evidence shown plainly.

Current-source read-only group paths passed on Apple Silicon. Apply and rollback paths remain deterministic mock evidence; no live setting mutation has been hardware verified.

Display

Main display and resolution. Resolution keeps the current refresh rate; an unavailable combination is skipped.

Current-source group live-read · apply/rollback mock-only

Sound

Output device, volume, and mute; input device and volume. Selecting an input device does not record audio.

Current-source group live-read · apply/rollback mock-only

Planned v0.1.0 platform: Apple Silicon with a macOS 14 deployment target. Exact-candidate lifecycle testing on Sonoma remains a release gate. The packaged Intel slice is not a physical Intel support claim.

Safety before speed

High-risk changes get a recovery step.

Protected display changes remain temporary during a 15-second review. Keeping them requires explicit confirmation; timeout, window close, or confirmation failure requests restoration of the preflight snapshot. Rollback is best-effort, and hardware mutation remains labelled unverified until independently tested.

  • Fresh snapshot before execution
  • 15-second Keep / Revert window
  • Itemized success, failure, omission, and rollback result

Private by architecture

Your desk profile stays on your Mac.

No outbound app service

No account, sync server, updater, product analytics, ads, or telemetry path.

No capture permission prompt

Current Capture reads Display and Sound only. It does not request Location or microphone access.

Review before sharing

Exports can contain device labels, stable identifiers, and dormant legacy data. Review and redact them before sharing.

This project code sets no cookies and contains no project analytics or client-side tracking. Its hosting provider still processes requests and may retain aggregate operational metrics.

Install

Public beta in preparation.

There is no supported public download today. The canonical GitHub Release will open only after the unsigned release gate—including exact artifact verification, a published SHA-256, and clean external beta installs—passes.

FAQ

Know the boundary before you install.

Does it switch profiles automatically?

No. Capture reads, Edit changes a draft, Review explains, and only Apply can start a system change.

Which settings can a profile save?

Main display, resolution, output device, output volume, output mute, input device, and input volume. Network is not a current profile feature.

What happens if a risky display change is wrong?

Protected display changes offer Keep or Revert and request rollback on timeout, close, or confirmation failure.

Is Intel supported?

Not in the initial beta. The build contains an x86_64 slice, but physical Intel install and runtime verification are still missing.

Open source

Small product. Public evidence.

Contributions are welcome when they preserve the local-only, explicit-apply, public-API safety boundary. Follow the current SECURITY.md instructions for sensitive reports; private vulnerability reporting must be enabled and tested before release.