leeyang1990 c5acc6edb6 feat(telegram): add dedicated TELEGRAM_PROXY env var and config.yaml proxy_url support ... Pass platform_env_var="TELEGRAM_PROXY" to resolve_proxy_url() in both telegram.py (main connect) and telegram_network.py (fallback transport), so a Telegram-specific proxy takes priority over the generic HTTPS_PROXY. Also bridge telegram.proxy_url from config.yaml to the TELEGRAM_PROXY env var (env var takes precedence if both are set), add OPTIONAL_ENV_VARS entry, docs, and tests. Composite salvage of four community PRs: - Core approach (both call sites): #9414 by @leeyang1990 - config.yaml bridging + docs: #6530 by @WhiteWorld - Naming convention: #9074 by @brantzh6 - Earlier proxy work: #7786 by @ten-ltw Closes #9414, closes #9074, closes #7786, closes #6530 Co-authored-by: WhiteWorld <WhiteWorld@users.noreply.github.com> Co-authored-by: brantzh6 <brantzh6@users.noreply.github.com> Co-authored-by: ten-ltw <ten-ltw@users.noreply.github.com>		2026-04-15 22:13:11 -07:00
..
developer-guide	docs: update tool-adding instructions for auto-discovery	2026-04-14 21:12:29 -07:00
getting-started	fix: include telegram dependency in termux bundle	2026-04-15 17:54:10 -07:00
guides	docs: document register_command() for plugin slash commands (#10671)	2026-04-15 19:55:25 -07:00
integrations	docs: clarify hermes model vs /model — two commands, two purposes (#10276)	2026-04-15 04:39:34 -07:00
reference	feat(telegram): add dedicated TELEGRAM_PROXY env var and config.yaml proxy_url support	2026-04-15 22:13:11 -07:00
user-guide	feat(telegram): add dedicated TELEGRAM_PROXY env var and config.yaml proxy_url support	2026-04-15 22:13:11 -07:00
index.md	fix(bluebubbles): add missing integration points and documentation (#6460)	2026-04-09 00:19:05 -07:00