tether

Tether

Keep Slack threads attached to the agents that created them.

This skill requires the separately installed private tether CLI and broker. It contains no runtime or installer. If the CLI or broker is unavailable, report that dependency and stop. Do not retrieve historical public source or packages as an installation fallback.

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.

Files: videos, images, PDFs

Post files natively, never as a link to a page: --file /abs/path.mp4 on notify, post or reply. The file lands in the channel or thread exactly like a person dragging it in, with the text as its comment (text is optional with --file). Do not upload to a docs host and link it; do not describe the file instead of sending it. Verify with tether thread that the message carries the file.

Send

Pass the message on standard input:

tether notify \
  --idempotency-key "<stable task-or-run key>" \
  --text-stdin <<'TETHER_MESSAGE'
Done: <outcome and useful evidence>
TETHER_MESSAGE

The notifier captures the current Codex or Claude Code session. For an explicitly headless job, add --run-id "$RUN_ID" to keep the thread available after that job exits. Do not use a headless declaration to recover a failed native binding. Report the failure and repair or rebind that exact session through the installed system's approved procedure.

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.

Completion criterion: the command returns a Slack thread timestamp. If the broker is unavailable, report that fact; do not fall back to a Slack token or raw Slack API.

Spawn a session for a task

tether spawn --task-stdin --channel C… --thread-ts T… [--harness claude|codex] [--cwd DIR] reads the task from standard input (never put it on argv), starts the harness in that directory, and binds it to that thread. A thread id without its channel is refused: Slack turns a reply to a thread it cannot find into a new channel message, and the session's report would land as a stray root. From inside Hermes prefer the tether_spawn tool, which carries the calling thread itself.