Tether

Keep Slack threads attached to the agents that created them.

Use the local Hermes broker as the single Slack boundary. Create a bridge only when the user asks for a Slack notification or an operator automation is explicitly configured to publish one.

Send

Run:

python3 ~/.local/share/tether/tether_notify.py notify \
  --text "Done: <outcome and useful evidence>" \
  --idempotency-key "<stable task-or-run key>"

The notifier captures the current Codex or Claude Code session and adds Zellij metadata when present. For scheduled or otherwise headless work, add --run-id "$RUN_ID"; the explicit run ID takes precedence over ambient agent variables and keeps the thread alive as a Hermes conversation after the process exits.

Use --file /absolute/path for one attachment. By default every explicitly allowlisted Hermes operator may continue the thread; pass --owner U… to restrict one bridge to a single Slack member.