@autoswarm/steward

Swarm Steward — the Auto Swarm terminal cockpit and agent-first steering copilot — distributed as a self-contained CLI.

Install

npm install -g @autoswarm/steward
steward --version

The binary is delivered as a platform-specific optional dependency (@autoswarm/steward-<platform>-<arch>) that npm installs only when it matches your OS/CPU. The binary therefore travels inside npm — no external download, no auth — so the package installs cleanly regardless of source-repo visibility. Supported: linux/macOS/Windows on x64/arm64.

Local install from a checkout

Inside an auto-swarm checkout with Go, build the binary in place — the launcher prefers a source build, so no published platform package is needed:

node packages/steward-cli/scripts/source-build.cjs
node packages/steward-cli/bin/steward.cjs --version

Run

steward                 # zero-config: discovers the local .autoswarm project
steward --readonly      # monitor-only
steward login           # device-code sign-in (identity only; never prints the token)
steward --resource-monitor

steward --help lists surfaces and keys. The cockpit is read-only by construction until a steering endpoint is configured; every governed action is composed and requires the operator's typed keyboard confirmation.

Releasing

Push a steward-v<version> tag (matching package.json's version). The steward-npm-release workflow builds the OS/arch matrix, publishes one @autoswarm/steward-<platform>-<arch> package per binary, then the main package that pulls the matching one in as an optional dependency, and cuts a checksummed GitHub Release for provenance. It uses the org NPM_TOKEN secret (an npm Automation token). The main package's optionalDependencies, the platform-package generator, and the launcher's resolve target must agree — scripts/resolver.test.cjs fences that contract, and the workflow runs it before publishing.