# Troubleshooting and feedback

Source: https://saer.app/docs/troubleshooting
Updated: 2026-10-29

**Short answer.** Check which Saer command you ran and whether your CLI is signed in. A browser sign-in alone does not connect the CLI. Use the full scan command when you want the complete beta output, and send feedback if a problem remains.

## I only see a free preview

A free preview is deliberately limited. Beta access includes full local scans, reports, the design-system reference and all ten MCP tools. Check your CLI account, then request a full scan:

Check access and require a full scan:

```
$ ~/.local/bin/saer whoami
$ ~/.local/bin/saer scan --full
```

If access is missing, run `~/.local/bin/saer login`. Approve the matching terminal code in the browser and return to Terminal until installation finishes. If you are already using the browser account but the CLI has another account, sign the CLI out and sign in with the beta email. The old report does not change when you sign in; run a new scan.

## My sign-in link or connection code expired

Request a new email link on [your beta page](https://saer.app/beta). For a CLI code, run `~/.local/bin/saer login` again and use the new browser page. Compare the code with your terminal before approving. The browser confirms when your connection has been approved.

## Terminal cannot find saer

Use the full command path in these docs. The installer does not edit your shell settings, so `saer` may not be on your command path yet.

Use the installed command directly:

```
$ ~/.local/bin/saer --help
```

If that file is missing, follow [getting started](https://saer.app/docs/getting-started) to install the launcher. Node 18 or newer and an Apple Silicon Mac are required.

## My beta is connected to another installation

Open [your beta page](https://saer.app/beta) and disconnect the previous CLI, then run login on the installation you want to use. Beta supports one connected CLI. Disconnecting revokes the previous session; it does not restart the trial.

## The report is old or a finding looks wrong

Run a fresh scan in the intended project. Check the file paths and theme or mode attached to the finding. Unknown or unresolved evidence should not be treated as a confirmed error. If something still looks wrong, share the smallest safe example through [feedback](https://saer.app/feedback), with the command and installed version. Reports can contain private paths and code excerpts; review them before sharing.

## Send feedback

[Open the feedback form](https://saer.app/feedback). Tell us what you tried, what you expected and what happened. Add your version from `~/.local/bin/saer --version` if relevant. Feedback is optional and separate from marketing consent. If you cannot sign in, email [hello@saer.app](mailto:hello@saer.app).