> ## 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.

# sauce runtime

> Install or check what sauce mcp and Solana simulations load, on a machine where the first run cannot install it or that must stay offline.

`sauce runtime` reports where the MCP server and Solana simulations load their dependencies. Use it to inspect or install those runtime packages.

## Synopsis

```bash theme={null}
sauce runtime [status] [--json]
sauce runtime install [--json]
```

## Description

Two commands load packages that an install of `@eco-incorp/sauce` leaves out, because they are its optional peer dependencies:

| Command | Packages |
| - | - |
| `sauce mcp` | `@modelcontextprotocol/sdk` and `zod` |
| A Solana simulation in a local copy of the cluster | `litesvm` |

Each command uses your own copies where the package resolves them at exactly the versions it pins. Otherwise it uses this version's runtime folder, `~/.sauce/runtime/<version>`. The first command that needs the folder installs it and says so on stderr.

The install runs `npm ci` on the lockfile the package ships, so every package is the pinned one, checked against its integrity hash. npm runs with no install scripts, in a temporary directory that is renamed into place only when npm succeeds, so a failed install leaves nothing half-installed. The folder is created owner-only, and the command refuses to install into it or load from it when another user owns it or can write a folder above it. npm reaches the registry your npm configuration names, a mirror or proxy included. After an install, the folders of older versions are removed, except the newest of them.

[`sauce mcp setup`](https://docs.eco.com/sauce-sdk/cli/mcp) and [`sauce update`](https://docs.eco.com/sauce-sdk/cli/update) install the folder before its first use. `sauce mcp --offline` installs nothing.

| Subcommand | What it does |
| - | - |
| `status` (the default) | Prints where each command's packages come from, and whether the folder is installed. |
| `install` | Installs the folder now, if it is not installed. |

## Options

| Option | Description |
| - | - |
| `--json` | Print one JSON object instead. |
| `-h, --help` | Show the help. |
| `--no-update-check` | Print no notice of a newer `sauce`, and do not read the registry for one. |

## Output

`status` prints the folder, whether it is installed, and for each command its packages and their source: `your own copies`, `the runtime folder`, or not installed yet (the first use installs them). A copy of your own at another version than the pinned one is named, with a note that it is not used. `install` prints the packages and the folder it installed them in. With `--json`, `status` prints:

| Field | Meaning |
| - | - |
| `dir` | The runtime folder of this version |
| `installed` | Whether the folder is installed |
| `packages` | Each package: its `pinned` version, and `own`, your own copy where one resolves, else `null` |
| `uses` | For `sauce mcp` and `Solana simulations`: `own`, `runtime` or `missing` |

## Examples

### Show where the packages come from

```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
```

### The same, as JSON

```bash theme={null}
sauce runtime status --json
```

```json theme={null}
{
  "dir": "~/.sauce/runtime/<version>",
  "installed": true,
  "packages": {
    "@modelcontextprotocol/sdk": { "pinned": "<version>", "own": null },
    "litesvm": { "pinned": "<version>", "own": null },
    "zod": { "pinned": "<version>", "own": null }
  },
  "uses": {
    "sauce mcp": "runtime",
    "Solana simulations": "runtime"
  }
}
```

## Next steps

* [`sauce mcp`](https://docs.eco.com/sauce-sdk/cli/mcp)
* [`sauce update`](https://docs.eco.com/sauce-sdk/cli/update)
* [Solana](https://docs.eco.com/sauce-sdk/cli/solana.md)
* [Installation](https://docs.eco.com/sauce-sdk/installation.md)


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