rrrrnmtsu

Mirrors Hermes Desktop, CLI, TUI and ACP conversations into Discord: one public thread per session in a channel you choose, one post per turn (your message and the reply), so work started on a desktop can be followed from the phone. Posting runs on a background thread and never delays or breaks a turn. Disclosure — register() adds one post_llm_call hook; every turn's text (your message and the final reply, not tool calls or outputs) is sent to the Discord REST API (discord.com) using the bot token you configure, after Hermes's redact_for_egress plus a local token-pattern filter (fail-closed: nothing is sent if the redactor is unavailable); mentions are disabled. The bot token is read only via agent.secret_scope.get_secret (an UnscopedSecretError under multiplexing skips the turn); no external command is ever run. Each turn reads the session's title and source from $HERMES_HOME/state.db read-only; session-to-thread ids are stored (mode 0600) in $HERMES_HOME/state/session-mirror.json. The optional `hermes session-mirror backfill` CLI command reads $HERMES_HOME/state.db read-only and replays past sessions through the same redaction. No other files, telemetry or long-running processes beyond one daemon sender thread.