Repository navigation
OPENBOTJR CLOSES ISSUES THAT HAVE RESPONSES WITH "HAVEN'T HEARD BACK", PLEASE SOLVE #61304
Closed as duplicate
Description
Description
Sorry for the caps but this keeps happening. People reply, comment. Openbotjr just closes stating "we haven't recieved a response". You can't @ the bot either. And it doesn't see or read comments clearly. The bot coding has bugs, please fix at least this one.
Plugins
No response
OpenCode version
v2
Steps to reproduce
Open issue. Openbotjr will respond. You answer with additional info. Openbotjr will close the issue anyway after some days stating there was no response while there was (no matter if multiple people responded).
Screenshot
No response
Operating System
No response
Terminal
No response
Activity
opencodejr commentedon Nov 2, 2026
Thanks for reporting this, @VariableVince, and sorry for the frustration. You're right that closing an issue with "we haven't heard back" when people did reply is wrong.
I think this is a duplicate of #60641, which reports the same problem with the triage bot and has already been flagged to the maintainers. Possible duplicates, ordered by likelihood:
If you have specific issues that were closed this way, please add links to them on #60641. That will help the maintainers see how often it happens.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. A reply here will be read and will stop the automatic close.
J-eremy commentedon Nov 2, 2026
Reproduced for me as well: the bot set a 1-day reply deadline, I replied 3 minutes later, and it closed at the 24h mark claiming it never heard back. Full timestamp chain: #61077 reopen request, also logged on #60641.
citkane commentedon Nov 2, 2026
Exhasperating...
VariableVince commentedon Nov 3, 2026
It really feels like everything is vibe coded around here, without much human thought or testing or thinking of more than just the happy path. Including this bot.
J-eremy commentedon Nov 3, 2026
This is partially what is to be expected considering what the company does, but its getting a bit ridiculous IMHO.
citkane commentedon Nov 3, 2026
I am new to this, and it's a GREAT tool, but so are guns, and most of us have feet...
jlongster commentedon Nov 3, 2026
This was a mistake: we had a feature where you could mention the bot to pull it into a PR or other threads and interact with it and ask it questions directly. We meant to turn only that off but that accidentally made it ignore comments meant for replies for our inbound processing system. We've turned all of them back on so it should work better now!
citkane commentedon Nov 3, 2026
Also to consider @jlongster, sometimes us humans submit an issue, then edit it furiously for at least an hour... It would help if the triage bot waited a bit longer before starting to do its thing. Thanks, I am enjoying opencode!
VariableVince commentedon Nov 3, 2026
Thanks, seems to be working again even reopening issues it closed #60739 (comment)
opencodejr commentedon Nov 3, 2026
Closing this as a duplicate of #60641. That issue tracks the same problem: the triage bot closes issues saying it hasn't heard back when people did reply. It has already been flagged to the maintainers.
We waited a day for a reply explaining how this one is different, and none was recorded. Given what this issue is about, if you did reply and it was missed, I'm sorry. Please say so and a maintainer can reopen it. Examples of issues closed this way are most useful on #60641, where the maintainers are tracking this. Thanks again for raising it, @VariableVince.