# Quick start

From nothing to a first correct result, and then to your agent running it. About ten minutes.

## 1. Install

One command, for your user only (no administrator rights). The installer sets up
[uv](https://docs.astral.sh/uv/), which brings its own Python when the machine has none recent enough, and then
the `recipe360` command.

| System | Command |
| --- | --- |
| macOS, Linux | `curl -LsSf https://recipe.pulso360.ai/install.sh \| sh` |
| Windows (PowerShell) | `powershell -ExecutionPolicy ByPass -c "irm https://recipe.pulso360.ai/install.ps1 \| iex"` |

The installer takes the latest release from `https://recipe.pulso360.ai/download`, whose package index offers a
compiled package for each system (macOS, Linux and Windows) and Python 3.11 to 3.13. Prefer your own tools?
`uv tool install --extra-index-url https://recipe.pulso360.ai/download/simple recipe360` does the same. Pre-release:
until the first release is published there, run the installers from a copy of the repository,
`RECIPE360_SOURCE=. sh install.sh` on macOS and Linux, or `$env:RECIPE360_SOURCE="."; .\install.ps1` on Windows.

Or ask your agent to install it and connect it to itself: [When your agent installs it](agents.md#when-your-agent-installs-it).

Open a new terminal afterwards and check:

```bash
recipe360 --version
```

## 2. Run the example

The example runs without a licence, on its own data.

Recipe360 ships with one example: a card portfolio risk and compliance review in 13 steps, on 400 invented
cards. It reads the card file, checks its quality, masks the card numbers and deletes the CVVs, looks at expiry,
PIN, chip and each client's exposure, scores the risk, proposes credit-limit cuts, decides what to do with each
card, writes the committee report and the letters to clients, and gives a compliance verdict.

```bash
recipe360 example
```

This copies the recipe and its test sample into your workspace (`~/.recipe360/recipes`), the data into
`~/.recipe360/examples/card-review`, and prints the exact commands to run it. Then:

```bash
recipe360 run card-review --data ~/.recipe360/examples/card-review --param cutoff=2026-10-31
```

The answer is the recipe's closing message, then the values the run used:

```text
Done: I ran the card portfolio review, all 13 steps verified. I reviewed 400 cards from 110 clients: 13 are
reissued with a chip, 137 must change their PIN and 19 credit-limit cuts await committee approval. I wrote 99
letters to clients. Compliance verdict: compliant.
Parameters: cutoff = 2026-10-31.
```

Run it again: the delivery fingerprint is the same, on any computer. Then look at what it left:

```bash
recipe360 runs                   # past runs, newest first
recipe360 record --format pdf    # the run record of the latest run, as a PDF in its run folder
recipe360 test card-review       # the recipe against six hand-made cards and 24 answers worked out by hand
```

## 3. Activate your licence

Your own recipes and data need an active licence. Activate this computer with the key that came with your
subscription:

```bash
recipe360 activate R360-XXXX-XXXX-XXXX-XXXX
```

The licence renews itself while the subscription is paid. Only the key, this installation's id, the computer's
name and Recipe360's version are ever sent; never data, recipes or results. See [Your licence](licence.md).

## 4. Connect your agent

Pick your agent program in [Agent programs](agents.md). For Claude Code, for example:

```bash
claude mcp add recipe360 -- recipe360 mcp
recipe360 skill --dest ~/.claude/skills
```

Then ask your agent, in your own words:

> Run the card portfolio review on ~/.recipe360/examples/card-review with cut-off October 31, 2026.

The agent calls Recipe360 once and answers with the same closing message. It never sees the cards.

## 5. Your own workflow

This is what Recipe360 is for; the example is optional. Ask your agent in your own words, for example: "I want a
recipe for our monthly supplier reconciliation; the file is in Downloads." If the process is written down
somewhere (a procedure, a list of steps), give it to the agent. It asks you a few questions at a time, writes
the recipe, tests it with answers you already know, and reads every rule back to you for your approval. Then
the process is fixed: run it whenever you want, on the same file or next month's, whatever the file is called.
See [Building recipes](building-recipes.md).