# Set up a project with saer init

Source: https://saer.app/docs/init
Updated: 2026-11-12

**Short answer.** Run `saer init` once in a project. It runs a full scan, shows the system it found, then asks before each change: connect Claude Code, Cursor or Codex, add a short Saer section to `AGENTS.md` or `CLAUDE.md`, and add the pull-request check with a `saer.config.json` policy. Nothing is written without a yes, and you can run it again to add what you skipped.

## Before you start

Install Saer and connect your account first: see [getting started](https://saer.app/docs/getting-started). `saer init` asks questions, so run it in a terminal. In scripts and CI, use the commands underneath it: `saer scan`, `saer agent` and `saer ci`.

Set up the project in this folder:

```
$ saer init
```

## What it shows

- Your palette as colour swatches in the terminal, with drift per area: colour, type, the other foundations and components.
- What to fix first, from the same evidence as the report.
- The components your agents should reach for.

Coverage limits and unknowns stay visible, as in the report. Open `.saer/report.html` for the full detail.

## What it offers to change

1. Connect your coding agents. Saer lists Claude Code, Cursor and Codex, marks the ones it finds on your machine, and connects the ones you choose. To check, change or remove one connection later, use `saer agent` ([agent setup](https://saer.app/docs/agents)).
2. Add the Saer section to your agent instructions: three lines in `AGENTS.md`, or `CLAUDE.md` if that is the file you have, telling the agent to ask Saer before building UI and to check its changes before finishing.
3. Add the pull-request check: a GitHub workflow that runs `saer ci` on every pull request, and a `saer.config.json` with the default policy. Raw values equal to a token block; hand-built UI warns until you set it to block. The workflow needs a CI runner key stored as a repository secret: see [CI checks](https://saer.app/docs/ci).

Each step is a separate question. A file that is already there is kept and says so. Running `saer init` again updates the Saer section in place rather than adding a second one.

## Afterwards

Run `saer` on its own to reopen your system at a glance in the interactive workspace. Run `saer ci --base main` before you push to see what the pull-request check will say, and see [everyday use](https://saer.app/docs/everyday-use) for the rest of the loop.
