The published @stateset/cli@1.39.0 package includes commerce commands, MCP transports,
agent workflows, simulations and channel gateways. Each entrypoint has its own flags and
permissions. It is not a single hosted service or a requirement for using the native library.
Use Node 20.20+ and npm 10+, keeping native optional dependencies enabled. A local embedded
store needs no StateSet account. Natural-language execution needs its configured model
provider; sync, wallets, channels and external integrations need their own credentials.
Select the entrypoint
Begin with one store
Complete the local quickstart, then read
that same file explicitly:
A wrong working directory can create/open another store. Use an absolute path when connecting
an external MCP host. A local order or payment record is separate from an external shipment
or provider transfer.
Profiles and execution authority
The 1.39 source catalog has 209 core tools and 966 tools in all, before strict/read-only
filtering. Operations, finance and agents profiles expose selected domains; curated profiles
include tools across stability tiers. Discovery is authoritative for the running endpoint.
--apply grants intent to attempt a write; it does not itself provide business policy or
idempotency. Configured MCP/agent endpoints require operator-owned kernel policy, principal
and store scope. Deterministic direct commands are a separate coarse-gated native interface.
Use governed execution for typed policy decisions
and durable same-key receipts.
Test a hypothesis before live execution
Use native simulations for demand, supplier delays, stockouts,
replenishment constraints and exact cash. They operate in private episode stores and make no
live purchases. Their outputs are conditional projections, not validated forecasts or
permission to apply a policy in production.
Continue
Last modified on October 20, 2026
