YogevKr

Agent Tether — Development skill for Claude Code

Development community

Telegram handoff for local coding agent sessions.

How to install Agent Tether

This entry records only its repository, not the path inside it, so there is no exact command to give. Open YogevKr/agent-tether and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agent Tether does

Telegram handoff for local coding agent sessions.

Alternatives in Development

Resume Work From A Handoff Document — You are tasked with resuming work from a handoff document through an interactive process 10k ★
Mulmoterminal — Run multiple Claude Code and Codex sessions in parallel — a browser terminal grid that shows which agent needs 187 ★
Poirot — 96 macOS app for browsing Claude Code sessions, viewing diffs, and re-running commands 104 ★

README

Agent Tether

Run coding agents on your machine as usual. Global Codex and Claude Code hooks index sessions locally. Telegram lets you bind one of those sessions to a forum topic and continue it remotely.

Model

Local Codex and Claude Code sessions are indexed by global hooks.
Telegram General topic is the main control plane.
Telegram DM remains available as fallback control.
A Telegram forum topic is the work surface for one agent session.
Sessions stay headless until you bind one from /sessions.
Sessions are owned by one host_id, so one bot can route work to multiple computers.
Telegram can also create a fresh session: choose node, choose place, browse directories, open topic, send first prompt. Before node/place selection, Telegram asks which provider to use for the new session.

Requirements

Node 20+
codex and/or claude CLI installed and logged in
Telegram bot token from BotFather
A Telegram supergroup with Topics enabled
The bot added to that supergroup as admin with topic management rights
Global agent hooks enabled in ~/.codex and ~/.claude

Setup

Copy env file:
```
cp .env.example .env
```
Fill these values in `.env`:
- TELEGRAM_BOT_TOKEN
- AUTHORIZED_TELEGRAM_USER_IDS
- TELEGRAM_FORUM_CHAT_ID
- CODEX_DEFAULT_CWD
- RELAY_START_ROOTS
- optional but recommended: RELAY_HOST_ID
- optional: STATE_FILE if you want a custom persistence path; default uses an OS app-data location instead of the repo checkout
  - for deployed/stateless environments, point this at a mounted persistent path
  - if RELAY_HOST_ID is unset, Agent Tether persists a generated host id next to STATE_FILE
For multi-host mode:
- On the hub machine, keep RELAY_HUB_URL empty and run npm run bot
- On every non-hub machine, set:
  - RELAY_HUB_URL=http://:8787
  - RELAY_HUB_TOKEN=
  - RELAY_HOST_ID=
- On