npm package

Sailor ships as a single published package — @sail.money/sailor (latest 1.3.0, MIT). It contains both the sailor CLI and the SDK; the SDK is exposed as a subpath export. There is no separate @sail.money/sdk package — @sail.money/sailor is the one package you install.

Install & scaffold

bash / zsh (macOS, Linux)

mkdir my-agent && cd my-agent && npm i @sail.money/sailor && npx sailor init

PowerShell (Windows)

Requires Node.js ≥ 18. sailor init scaffolds the project from the default template (agent code, a Foundry workspace for custom permissions, worked example permissions, AGENTS.md, and the skills).

Running the CLI

Inside a scaffolded project the sailor binary is available via npx:

npx sailor <command>      # e.g. npx sailor status, npx sailor run --once

Prefer a global command instead:

npm install -g @sail.money/sailor
sailor <command>

The full command surface is in the CLI reference.

Using the SDK

The SDK is imported from the @sail.money/sailor/sdk subpath — this is what scaffolded agent code uses, and it's injected as a dependency by sailor init:

import {
  SailorClient,
  LocalKeyring,
  getSailDeployment,
} from "@sail.money/sailor/sdk";
import type { Agent, AgentContext, Dispatch } from "@sail.money/sailor/sdk";

To add it to another project, install the package and its viem peer:

npm install @sail.money/sailor viem

Everything — SailorClient, the Agent interface, EIP-712 builders, template encoders, ABIs, and the deployment/chain registries — imports from that single @sail.money/sailor/sdk entry point. See the SDK reference.

One package, no standalone SDK. Always import the SDK from @sail.money/sailor/sdk. A standalone @sail.money/sdk distribution with granular subpaths is planned but not yet published to npm — do not depend on it; install @sail.money/sailor.

No Node.js?

Run the same CLI from the pre-built container instead — see Docker.