> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Package updates

> Check for package updates and keep the CLI, project dependency, agent skills and MCP configuration in sync.

The `sauce update` command checks and updates the installed package. Project dependencies, agent skills and MCP configuration have their own checks below.

## Prerequisites

* The `sauce` command or the package installed. See [Installation](https://docs.eco.com/sauce-sdk/installation.md).
* Node.js 24 or newer.

## Check for an update

```bash theme={null}
sauce --version
sauce update --check
```

`sauce update --check` reads the npm registry. It prints the installed version, how the command was installed, and the version an update would install. It installs nothing:

```text theme={null}
@eco-incorp/sauce <version>, <project>'s own copy (npm); the latest is <latest>
```

### The update notice

After a command, one line on stderr says when a newer release is published:

```text theme={null}
sauce <version> → <latest> is available: run `sauce update`
```

The line comes from a cache, `~/.sauce/update-check.json`, which is refreshed from the npm registry at most once a day, in a background process that no command waits for. The first command after a release may not show the line yet. It goes to stderr only, so `--json` output and stdout pipes are unaffected.

To turn the notice off:

* pass `--no-update-check`, which every command takes, before or after the command name;
* or add `"updateCheck": false` to the `--config` file a command is given.

`--offline` also turns it off. `sauce mcp` prints no notice: it adds a note to its first tool result instead.

## Update

**Global install**

```bash theme={null}
sauce update
```

npm, pnpm, yarn or bun installs the new version globally, as the command was installed, and prints the version before and after. The new `sauce` then updates the agent skills installed in the current directory and prints what changed. Where the replaced version had its runtime packages installed, the new version installs its own.

**A project's dependency**

In a project that depends on `@eco-incorp/sauce`, `sauce update` runs nothing. It prints the command for the project's package manager, pinned exactly:

```bash theme={null}
npm install --save-exact @eco-incorp/sauce@latest
```

Run that command, then commit the updated `package.json` and lockfile. A project made with `sauce init` pins the package to one exact version, so every machine and CI job runs the same command and compiler.

**npx**

```bash theme={null}
npx -y @eco-incorp/sauce@latest <command>
```

`@latest` makes npx fetch the latest release instead of reusing the copy in its cache.

`sauce update --version <version|tag>` installs a given version or dist-tag instead of `latest`. From any other kind of installation, `sauce update` refuses and prints npm's global install command.

## Check after updating

### Agent skills

The skills in a project are copies from one version of the package.

```bash theme={null}
sauce skills status
```

```text theme={null}
claude (.claude/skills): up to date (<version>)
```

`status` exits 1 while any target is outdated or not installed. Run it in CI to catch a package upgrade the skills have not followed. To bring the skills to the installed version:

```bash theme={null}
sauce skills update
```

`update` adds new skill files, replaces changed ones and removes retired ones. A file you edited since it was installed is kept and its diff is shown, unless you pass `--force`. See [sauce skills](https://docs.eco.com/sauce-sdk/cli/skills.md).

### Runtime packages

`sauce mcp`, and a Solana simulation in a local copy, load packages each version installs for itself in `~/.sauce/runtime/<version>`.

```bash theme={null}
sauce runtime
```

```text theme={null}
Runtime packages, in ~/.sauce/runtime/<version> (installed):
  sauce mcp          @modelcontextprotocol/sdk <version> and zod <version>: the runtime folder
  Solana simulations litesvm <version>: the runtime folder
```

A new version installs its folder on first use, or at once with `sauce runtime install`. Older versions' folders are then removed, except the newest of them. See [sauce runtime](https://docs.eco.com/sauce-sdk/cli/runtime.md).

### The MCP entry

`sauce mcp setup` writes `npx -y @eco-incorp/sauce@<version> mcp` into each agent's project file. Rewrite it for the new version, then restart the agent's session:

```bash theme={null}
npx -y @eco-incorp/sauce@latest mcp setup --force
```

An entry that runs a global `sauce mcp` uses the global version after `sauce update`.

### Programs and transactions

Compile and simulate with the package your application uses. The SDK checks that an engine is recorded for its pinned compiler; more than one compiler can share an engine and Kitchen. Pot addresses are keyed to the Kitchen, owner and salt, not to the compiler version. See [V12](https://docs.eco.com/sauce/v12.md) and [Deployments](https://docs.eco.com/sauce-sdk/reference/deployments.md).

Before sending funds, check the deployment with `sauce pot --chain <chain> --owner <address>` and follow the [production checklist](https://docs.eco.com/sauce-sdk/operating/production-checklist.md).

For settlement verification, import `SETTLE_WIRE` from `@eco-incorp/sauce/verify` rather than copying its values. The default validator accepts that pin only; an explicit `{ hash, bytes }` record or `sauce verify --pin <hash:bytes>` defines another accepted payload. See [Verification](https://docs.eco.com/sauce-sdk/typescript/verification.md).

## Next steps

* [Production checklist](https://docs.eco.com/sauce-sdk/operating/production-checklist.md): before running the upgraded version with funds.
* [Troubleshooting](https://docs.eco.com/sauce-sdk/operating/troubleshooting.md): when something stopped working after the update.
* [sauce update](https://docs.eco.com/sauce-sdk/cli/update.md): every flag of the command.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.