Hi, thanks for the project! I have been using this bot for the pass few days, and it worked great.
Here is an issue I found:
OpenCode can emit duplicate equivalent permission requests for concurrent tool calls. I opened an upstream issue with details here:
anomalyco/opencode#36055
In the Telegram bot, this shows up as a confusing stale-button UX:
- The bot renders two identical permission prompts.
- I click
always on the first one.
- When I continue the session, the bot still appears blocked by the second prompt.
- Clicking
always on the second prompt fails with Permission request not found.
- The session can continue afterwards, but the UX is confusing.
Could the bot handle this case more gracefully, for example by coalescing equivalent pending prompts, disabling stale duplicate buttons, or treating Permission request not found from a stale prompt as a stale UI state instead of a user-visible error?
This may be an upstream OpenCode issue rather than a bot-side bug, but the Telegram UI currently exposes the stale duplicate prompt very directly.
Hi, thanks for the project! I have been using this bot for the pass few days, and it worked great.
Here is an issue I found:
OpenCode can emit duplicate equivalent permission requests for concurrent tool calls. I opened an upstream issue with details here:
anomalyco/opencode#36055
In the Telegram bot, this shows up as a confusing stale-button UX:
alwayson the first one.alwayson the second prompt fails withPermission request not found.Could the bot handle this case more gracefully, for example by coalescing equivalent pending prompts, disabling stale duplicate buttons, or treating
Permission request not foundfrom a stale prompt as a stale UI state instead of a user-visible error?This may be an upstream OpenCode issue rather than a bot-side bug, but the Telegram UI currently exposes the stale duplicate prompt very directly.