Skip to content

Handle bridge timeouts and improve Telegram error reporting #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
boly38 merged 2 commits into from
Oct 18, 2026
Merged

Handle bridge timeouts and improve Telegram error reporting #19

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8e941a5
fix: improve Telegram timeout reporting (#18)
boly38 Oct 18, 2026
fa037f4
fix: use valid OpenCode message IDs (#18)
boly38 Oct 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,15 @@ without reviewing it.
```

6. Send a message from an authorized chat. If there is an error,
`make logs SERVICE=telegram` shows the HTTP details returned by OpenCode.
Telegram returns a short reference. Search for `request_failed ref=<reference>` in
`make logs SERVICE=telegram` to find the client, phase, elapsed time, timeout, and safe error
details. Prompts, credentials, session IDs, and raw OpenCode response bodies are not logged.

The bridge acknowledges a request immediately, then edits that message with the result. It may
also show generic thinking or tool-progress updates when OpenCode emits matching events; raw
reasoning content is never forwarded. At startup, logs show the effective OpenCode and Telegram
timeouts. OpenCode requests have a 300-second deadline; Telegram HTTP requests use 70 seconds,
with long polling configured for 50 seconds.

If Telegram replies `Invalid Opper API key` or the logs mention `401`, regenerate the
key in your Opper AI project and replace only the
Expand Down
Loading
Loading