Runtime process
Run gateway under a supervisor and persist logs for debugging and auditability.
Getting started with Resonix-AG
This guide gives you a stable first run path: verify environment, install, onboard, start gateway, and validate runtime health.
Prerequisites
- Node.js 22+ runtime
- Terminal shell access (zsh/bash or PowerShell)
- Internet access for provider/channel auth
- Git (if installing from source)
First run workflow
resonix onboard
resonix gateway start
resonix channels status --probe
Tip: run onboarding first so model auth, gateway mode, and default settings are generated
predictably.
Validation checklist
- Gateway process is running and listening on expected port.
- At least one model/provider auth path is configured.
- Selected channel routes can send and receive messages.
- Config file was generated and persisted in expected location.
Production baseline
For production, treat the gateway as a managed process, keep credentials isolated, and configure channel allowlists before exposing network access.
Credential policy
Store tokens securely and avoid embedding secrets in scripts or docs.
Channel controls
Start with strict route/command constraints, then broaden gradually.
Upgrade path
Pin release channel and test upgrades on staging before production rollout.