@dev.sail.money/sailor 1.2.1-202 → 1.2.1-204

package/README.md

@@ -102,6 +102,18 @@ npm install -g @sail.money/sailor
 sailor init my-agent
 ```
 
+### Docker (no Node.js required)
+
+Run sailor from a pre-built image — useful when you don't want to install Node.js or want an isolated environment:
+
+```bash
+mkdir my-agent && cd my-agent
+docker run -d --name agent -P -v "${PWD}:/workspace" sailmoney/sailor
+docker exec agent sailor init
+```
+
+Then open the folder in your AI coding assistant and say **"start"**. See the [Docker Hub](#docker-hub-publish-dockeryml) section below for full usage details.
+
 ---
 
 ## Quickstart
@@ -382,6 +394,57 @@ Or pin in `package.json`:
 
 Either way, `@sail.money/sailor/sdk` imports work unchanged.
 
+### Docker Hub (`publish-docker.yml`)
+
+A pre-built image is published to Docker Hub so you can run the CLI without installing Node.js locally. The image uses Alpine Linux and includes `tsx` (required to compile TypeScript agent code at runtime).
+
+| Trigger | Tag |
+|---|---|
+| Merge to `main` or manual dispatch | `sailmoney/sailor:dev` |
+| Tag push (`v*`) | `sailmoney/sailor:<version>` + `sailmoney/sailor:latest` |
+
+#### Starting the container
+
+Run this from your project root. `-P` publishes all exposed ports to random available host ports; use a fixed `-p <host>:3334` if you want a stable UI port.
+
+```bash
+docker run -d --name agent -P -v "${PWD}:/workspace" sailmoney/sailor
+```
+
+- `-d` — detached, runs in the background
+- `--name agent` — container name used in all `docker exec` calls
+- `-P` — maps container ports (UI: 3334, station: 3141) to random host ports
+- `-v "${PWD}:/workspace"` — mounts the current project into the container
+
+#### Running sailor commands
+
+All sailor commands run via `docker exec`:
+
+```bash
+docker exec agent sailor --version
+docker exec agent sailor init
+docker exec agent sailor ui start
+docker exec agent sailor run --once
+```
+
+Project files are on your **local filesystem** — read and write them directly from local paths. Only `sailor` commands need the `docker exec` prefix; the volume mount makes files accessible to both sides.
+
+#### Opening the dashboard
+
+The UI always binds to port **3334 inside the container**, but the host-side port depends on how `-P` mapped it. Resolve it before opening the browser:
+
+```bash
+docker port agent 3334
+# → 0.0.0.0:49201   (open http://localhost:49201 in the browser)
+```
+
+#### Stopping
+
+```bash
+docker stop agent    # stop the container
+docker start agent   # restart it later (project files and state are on the host)
+```
+
 ---
 
 ## Security model

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dev.sail.money/sailor",
-  "version": "1.2.1-202",
+  "version": "1.2.1-204",
   "description": "Operator toolkit for Sail Protocol",
   "bin": {
     "sailor": "packages/cli/dist/index.cjs"

package/packages/sdk/dist/intelligence.d.ts

@@ -5,7 +5,7 @@
  * Do not edit manually — run `pnpm build` to regenerate.
  *
  * Spec version : 1.2.0
- * Generated at : 2026-06-20T18:00:07.965Z
+ * Generated at : 2026-06-20T19:09:38.935Z
  */
 export declare const SAIL_INTELLIGENCE_BASE_URL = "https://api.sail.money";
 export declare const SAIL_INTELLIGENCE_DOCS_URL = "https://api.sail.money/docs";

package/packages/sdk/dist/intelligence.js

@@ -5,7 +5,7 @@
  * Do not edit manually — run `pnpm build` to regenerate.
  *
  * Spec version : 1.2.0
- * Generated at : 2026-06-20T18:00:07.965Z
+ * Generated at : 2026-06-20T19:09:38.935Z
  */
 export const SAIL_INTELLIGENCE_BASE_URL = "https://api.sail.money";
 export const SAIL_INTELLIGENCE_DOCS_URL = "https://api.sail.money/docs";

package/templates/default/.agents/skills/sail-onboarding/SKILL.md

@@ -14,6 +14,35 @@ description: Walks the agent through setting up a new Sailor project or resuming
   `docker exec <containerName> sailor <command>`
   Project files are on your **local filesystem** (mounted at `/workspace` inside the container) — read and write them normally from local paths. Do NOT use `docker exec` to read files; the volume mount makes them directly accessible.
 
+### Starting the Docker container
+
+If the container is not running, start it from the project root:
+
+```bash
+docker run -d --name agent -P -v "${PWD}:/workspace" sailmoney/sailor
+```
+
+- `-d` — detached, runs in the background
+- `--name agent` — names the container; use a different name with `-e SAILOR_CONTAINER_NAME=<name>` if needed
+- `-P` — publishes all exposed ports to random available host ports (UI: 3334, station: 3141)
+- `-v "${PWD}:/workspace"` — mounts the current project directory into the container
+
+After starting, resolve the host port before opening the UI in the browser:
+
+```bash
+docker port agent 3334
+# → 0.0.0.0:49201   (use 49201, not 3334, in the browser URL)
+```
+
+All `sailor` commands run via `docker exec`:
+
+```bash
+docker exec agent sailor --version
+docker exec agent sailor init
+docker exec agent sailor ui start
+docker exec agent sailor station start --json &
+```
+
 The published package is **`@sail.money/sailor`** — always use the scoped name with the registry. The bare name `sailor` is a different, unrelated npm package; never `npx sailor@<version>` or `npm i sailor`. Install it (`npm i -g @sail.money/sailor`, or as a project dep), after which the `sailor` bin works bare (`sailor <command>`) and `npx sailor <command>` resolves the installed bin. Every `sailor …` command in these skills assumes it is installed. Confirm the toolchain up front and pin a recent version — `npx @sail.money/sailor@latest --version` — because an old cached `npx` build can be missing newer commands (e.g. `mandate simulate`); if a documented command reports "unknown command", you are on a stale version, not hitting a missing feature.
 
 After upgrading the CLI, run `sailor update` from the project root to pull in updated skills, `AGENTS.md`, `Dockerfile`, and other tooling files. User files (`src/`, `mandates/`, `.sail/`, `package.json`) are never touched.

package/templates/default/.agents/skills/sail-servers/SKILL.md

@@ -50,7 +50,17 @@ docker exec agent sailor station status --json
 docker exec agent sailor station stop --json
 ```
 
-The UI always binds to port **3334** in Docker (the image sets `ENV PORT=3334`). Project files at `/workspace` are your local directory — read and write them directly from local paths; only `sailor` commands need the `docker exec` prefix.
+The UI always binds to port **3334 inside the container** (the image sets `ENV PORT=3334`), but the host-side port depends on how the container was started. Before giving the user a URL, resolve the actual host port:
+
+```bash
+docker port <containerName> 3334
+# → 0.0.0.0:3334   (host port matches)
+# → 0.0.0.0:8080   (host port is different — use 8080 in the URL)
+```
+
+The URL to open in the browser is `http://localhost:<host-port>` where `<host-port>` is what `docker port` returned, not necessarily 3334. Never hard-code the port — always resolve it first.
+
+Project files at `/workspace` are your local directory — read and write them directly from local paths; only `sailor` commands need the `docker exec` prefix.
 
 ## Troubleshooting