Telegram bridge lets me drive the local Claude Code tmux session from my phone — inbound messages are typed into the 'claude' session, pane diffs are streamed back as plain Telegram messages (TUI noise, tool-call blocks, echoed user input and already-sent lines are filtered so only the assistant's actual reply reaches the chat). Deployed as food-market-telegram-bridge.service, reads creds from /etc/food-market/telegram.env (not committed). Also committing the local docker-registry unit for reproducibility — registry:2 on 127.0.0.1:5001, data persisted in /opt/food-market-data/docker-registry. Setup docs in docs/telegram-bridge.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
20 lines
512 B
Desktop File
20 lines
512 B
Desktop File
[Unit]
|
|
Description=food-market Telegram <-> tmux bridge
|
|
After=network-online.target
|
|
Wants=network-online.target
|
|
|
|
[Service]
|
|
Type=simple
|
|
User=nns
|
|
Group=nns
|
|
WorkingDirectory=/opt/food-market-data/telegram-bridge
|
|
EnvironmentFile=-/etc/food-market/telegram.env
|
|
ExecStart=/opt/food-market-data/telegram-bridge/venv/bin/python /opt/food-market-data/telegram-bridge/bridge.py
|
|
Restart=on-failure
|
|
RestartSec=10
|
|
# Access tmux sockets under /tmp/tmux-1000/
|
|
Environment=TMUX_TMPDIR=/tmp
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|