CLI and local event forwarding
Inspect resources and connect a running local harness.
Build the local SDK and CLI packages, then run node packages/cli/dist/index.js help. Public package publication is separate from this repository build.
export SQKII_BASE_URL="http://localhost:4000"
export SQKII_API_KEY="your-scoped-key"
node packages/cli/dist/index.js test
node packages/cli/dist/index.js numbersThe test command checks access without sending a message. To send, provide --number, --to, --text and a stable --idempotency-key explicitly.
Watch events
node packages/cli/dist/index.js events --watch \
--cursor-file .local/sqkii-events.cursor \
--forward-url http://127.0.0.1:8789/eventsA forward target must use HTTPS, except for an explicit loopback HTTP receiver. The original Sqkii key is never forwarded. Set a separate SQKII_FORWARD_TOKEN if your local harness requires bearer authentication.
The watcher persists its cursor only after a whole event page is handled. A crash may repeat events from that page, so the harness must deduplicate by event ID. The cursor file contains a checkpoint, not a credential; keep it with your consumer's persistent state.
Local configuration
config --base-url URL stores the origin. --store-key explicitly stores SQKII_API_KEY with file mode 0600. Prefer a secret environment and do not commit the configuration file.
The CLI is a transport helper. It does not run a model, implement your business rules, or make a stopped agent active.