This is a partial user and operations guide. The full guide is available to platform subscribers and active users only. We publish this public selection so evaluators get an initial sense of capabilities and workflows. Private guide content may change with ongoing product improvements.
Channels
The live channel today is a messaging channel, and only on the reference client installation.
Host: society-agents-host-operaciones (institution ldteam / operations). Profile: ld-chief-of-staff. The gateway runs as PID 1 (agent harness gateway run): one messaging session sticks to the process. That is why a second host exists — do not bloat the Primary.
Source of truth
Config lives in the profile .env, not in infra/:
/opt/sis/data/agents-operaciones/profiles/ld-chief-of-staff/.env
Example (reference client):
MESSAGING_CHANNEL_ENABLED=true
MESSAGING_CHANNEL_MODE=bot
GATEWAY_ALLOW_ALL_USERS=false
MESSAGING_CHANNEL_ALLOWED_USERS=18299865669
It persists on the data/ volume and survives client upgrades. Infra compose is regenerated on every deploy: anything you put there is lost.
Session (secret, never versioned):
…/profiles/ld-chief-of-staff/messaging-channel/session/creds.json
Do not copy creds.json to two machines: they kick each other off. A careless deploy loses the channel. The session is not reproducible (manual QR pairing).
Pair
Inside the operations agents-host container:
- Select profile
ld-chief-of-staff. - Run the agent harness messaging-channel command to show the QR in the terminal.
- Restart
society-agents-host-operaciones.
On the phone: linked devices. Test from another account: the QR links your number; messaging yourself is invisible to the gateway.
Profile selection is not re-read by PID 1 while running: recreate or restart the container after switching.
Group observe (read-only): overlay messaging_bridge_observe: true in the institution spec; sync with the ops script under tools/ops/.
Console view (screenshot): operar-vistas/channels.