Getting started

In short

Install Saer once, then run saer scan --free in your project with no account. The preview shows up to five exact colour-drift findings and stays offline after installation. For complete analysis, accept the beta terms at /beta and run saer login, then saer scan --full.

1. Check the requirements

A Mac with Apple Silicon (M1 or later). Intel Macs, Linux and Windows are not in the beta yet.
Node 18 or newer.
No Python installation or repository access. Installation and updates need internet once to download verified software. Free scans then work offline; premium use needs internet for account checks.

2. Install and try it free

Install the launcher and the separate free engine. No account, key or beta agreement is required for the limited free preview. Open a new Terminal tab if the installer asks you to, then run the scan from your project folder.

Terminal

curl -fsSL https://saer.app/install | sh

In Terminal, open the folder containing your project. Run this from that folder:

Terminal

saer scan --free

The free preview writes summary.json, report.md and a designed report.html inside .saer. It shows up to five exact colour replacements, source context and coverage limits. It does not provide the full system model, reference, component analysis, agent tools or CI access. Use saer and /free, then /report if you prefer the interactive workspace.

3. Enable full beta analysis when ready

Request early access, then sign in and accept the beta terms. Use the same installed command to connect your account. Saer verifies and downloads the separate protected engine automatically; there is no ZIP or repository invitation.

Terminal

saer login
saer scan --full

Full beta includes every implemented local analysis domain, detailed reports, reference.md, all ten coding-agent tools and optional CI/cloud history. Run another scan after signing in; an existing free report does not expand automatically.

saer scan ./apps/web scans a path; in a monorepo Saer finds the workspace root and the relevant packages.
--output <dir> writes the report somewhere other than .saer.
--json prints a machine-readable summary to stdout.
--no-experimental leaves out near-match drift and conflicts.

4. Open the report

Open .saer/report.html, or use /report in the interactive workspace. In a full report, start with exact drift: each finding is a raw value identical to a token, with the token to use instead and the files. Then read the experimental section, which is inference and labelled as such. See reading the report.

Tip

Add .saer/ to your .gitignore, or delete it whenever you like. Account credentials and optional cloud connections are kept separately in your private user configuration.

See it on your own codebase.

Request early access