You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -407,6 +407,8 @@ CODEX_WORKDIR=.
407
407
Common options:
408
408
409
409
```bash
410
+
TELEGRAM_API_BASE=https://api.telegram.org
411
+
TELEGRAM_PROXY_URL=
410
412
CODEX_COMMAND=codex
411
413
CODEX_ARGS=
412
414
CODEX_BACKEND=sdk
@@ -537,6 +539,7 @@ Telegram can manage runtime usage of Bot-side MCP and skills, but not install ar
537
539
## Troubleshooting
538
540
539
541
-**Bot not responding**: verify `BOT_TOKEN` and `ALLOWED_USER_IDS`
542
+
-**Telegram API blocked**: set `TELEGRAM_PROXY_URL` (HTTP proxy like `http://127.0.0.1:7890`) or run a local Bot API server and set `TELEGRAM_API_BASE`
540
543
-**Codex not producing output**: verify `CODEX_BACKEND`, `CODEX_COMMAND`, and `CODEX_WORKDIR`
541
544
-**SDK backend cannot resume**: verify the host still has access to `~/.codex/sessions` and that the saved thread id belongs to the same working directory
542
545
-**Markdown parse errors**: reduce output size/context; check special characters in tool output
0 commit comments