Overview
Turn any coding agent into a money agent. Sailor is the open-source harness for Sail Protocol: it deploys your SMA, builds your permissions, and runs your strategy on your own machine.
Sailor is the operator layer for building and running money agents on Sail Protocol. It ships through the coding agents developers already use (Claude, Cursor, Codex, Gemini, Grok, Hermes, and other compatible agents): from a scaffolded project, it deploys a separately managed account, authors and registers the mandate, and runs the strategy, all locally. No single agent is required.
Funds remain in your own separately managed account (SMA). The agent never holds your owner key and acts only through a mandate — deterministic on-chain permissions the protocol checks on every transaction. That bound is what makes a Sailor agent safe to run with real capital.
What you can build
Section titled “What you can build”Autonomous money agents for any use case:
- Trading — spot, DCA, rebalancing.
- Yield — lending, borrowing, liquidity providing, staking, looping.
- Payments — transfers, scheduled moves, operational flows.
These are examples, not a boundary. Permissions are arbitrary Solidity, so anything in DeFi can be expressed as a permission and operated by an agent. When no shared template fits, you author your own IPermission — see Build & register a mandate.
How it works
Section titled “How it works”Open the scaffold in Claude Code, Cursor, Codex, or any AI coding agent and say start. The agent walks the journey with you — set up the SMA, define the strategy, build and sign the mandate, write the tick loop, then launch and operate — with a direct CLI equivalent for every step. See Operate Sailor with a coding agent, or point your assistant at the docs with the ready-made prompt on For AI agents.
Components
Section titled “Components”| Piece | What it does |
|---|---|
SDK (@sail.money/sailor/sdk) | SailorClient, the Agent interface, encrypted keyring, EIP-712 signing, dispatch submission, deployment + chain registries, template encoders. See the SDK reference. |
CLI (sailor) | Everything from sailor init to sailor run: keys, SMA deployment, the full mandate lifecycle, the agent loop, session control, doctor. See the CLI reference. |
Dashboard (sailor ui) | A local web app for onboarding, wallet gas balances, mandate health, activity, and owner signing — read from the project’s .sail/, no hosted backend. See the Dashboard. |
Shipyard (sailor sandbox) | A simulation sandbox that forks the real chains onto your own machine with fake money, against the real deployed contracts, so you can rehearse the whole setup and prove a mandate permits what you think it permits. Real market state, frozen at fork time; fully isolated from live. Needs Foundry. See Shipyard. |
| Skills | 22 curated procedures under .agents/skills/, organized by the five stations — onboarding and diagnostics, strategy definition, mandate construction (one skill per shared template plus the full custom-permission lifecycle), agent construction with a verified code skeleton, and unattended operation through exit. The skills are the harness: any coding agent reads them natively and follows the same verified path in every project. See Skills. |
Install
Section titled “Install”Requires Node.js ≥ 18, or run it from Docker with no Node.js at all. The exact commands are on the npm package and Docker pages, and the Quickstart walks the whole first run.
Where to go next
Section titled “Where to go next”- Quickstart — install and go from zero to a dispatched transaction.
- Operate Sailor with a coding agent — the flagship workflow: scaffold, open in your assistant, say start.
- Install and run: npm package · Docker · Skills · Dashboard · Shipyard.
- Chains: Deployment addresses · Multi-chain operation.
- Reference: Concepts · Guides · CLI reference · SDK reference · Security · Troubleshooting.
- Community: Discord · X · GitHub · npm.