Voice and Gateway Channel Readiness

Rocky can operate across terminal and messaging channels. Gateway readiness means the platform is connected, message delivery is tested, voice settings are understood, and failures have a recovery path.

Official messaging docs: https://hermes-agent.nousresearch.com/docs/user-guide/messaging/

Readiness checklist

Confirm the target platform adapter is configured.
Confirm the bot or account has the required platform permissions.
Send a harmless test message through the actual delivery channel.
Test voice transcription or text-to-speech only when that workflow is needed.
Document the restart/status command for the gateway service.

Voice notes

Speech-to-text provider availability depends on local packages or configured API keys.
Text-to-speech provider limits vary by backend.
Voice messages should avoid reading secrets, raw URLs with tokens, or private records.
For client-facing updates, use short plain-language scripts.

Pitfalls

Assuming CLI success means gateway delivery works.
Forgetting platform-specific permissions such as message-content access.
Making long voice responses that are hard to review or replay.
Sending operational errors to a client channel without a human-safe summary.

Verification steps

Run hermes gateway status or the documented status command.
Check gateway logs when messages do not arrive.
Send and receive a small test on the target platform.
For voice, verify the actual audio or transcript output before relying on it.