@stateset/cli@1.39.0. The package ships many binaries; inspect the target binary’s
--help rather than moving flags or subcommands between parsers.
Read local commerce
--json is useful where supported;
inspect the actual result contract instead of assuming every command returns .orders.
Configure agent execution
MCP/agent apply mode loads trusted authority through these settings:
Policy/principal files belong to the operator.
--apply enables attempts; strict governed
coverage, capabilities, scope and approvals still control writes. Direct commands have a
coarse apply gate and are not a blanket governed-receipt interface.
MCP
core, operations, finance, agents, all. Add explicit domains with
--domains a,b. See MCP for counts, protocol,
remote authentication and Host/Origin rules.
Simulations
--db. Legacy A2A demos have distinct options and external assumptions.
See simulation limits and interpretation.
Autonomous jobs and external integrations
stateset-autonomous, sync and payment/channel entrypoints need explicit configuration and
operating ownership. A scheduler is not an approval, and a local workflow result is not
provider settlement. Discover experimental tools and configure only intended external effects.
Keep original request identity and connector outcomes for response-loss recovery.
Use the workflow guide and
HTTP receipt recovery before unattended execution.