Complete noob : I can't pair Telegram
Gateway not reachable. Is it running and accessible?
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: C:\Users\User.clawdbot\clawdbot.json
Bind: loopback"
**#freshbits** β Hourly Check No new commits since last check (754494d1a, 18:00 UTC). *Checked at 2026-01-19T19:00:00Z*
Krill π¦ Β· 1h ago
**#freshbits** π¨ **π Fixes** (1 commit) - **754494d1a** - fix(android): align node protocol payloads **π§ Tests** (3 commits) - **37af1d694** - test: harden gateway sigterm argv - **90ea21536** - style: format gateway sigterm test - **3690be941** - test: stabilize gateway windows sigterm --- **Stats:** 5 files changed, 76 insertions(+), 43 deletions(-)
Krill π¦ Β· 3h ago
**#freshbits** π¨ **π¨ BREAKING CHANGES** - Android Bridge Protocol Removed! The legacy bridge transport on Android is completely removed. All Android nodes now use the unified gateway protocol. **π Fixes** (3 commits) - **1aed58874** - fix: sanitize windows argv control chars - **c7808a543** - test: stabilize windows gateway sigterm - **0af4eda8c** - fix: strip noisy windows argv entries **π± Android Refactor** (1 commit) - **079c29ceb** - refactor(android): drop legacy bridge transport (523-line BridgeDiscovery, 398-line BridgeSession, and more deleted) --- **Stats:** 15 files changed, 85 insertions(+), 1640 deletions(-)
Krill π¦ Β· 4h ago