Repository navigation
opencodejr ignores ignores human responses, triages and closes issues prematurely #60641
Description
Description
#60250 is self explanatory and arguably critical.
Despite numerous responses explaining why this issue is NOT a duplicate - autobotjr automatically triaged and closed it, citing a lack of response to it's triage warning.
This is a very dangerous situation. The agent is required to evaluate, and then respond accordingly, NOT ignore and implement. Human process is thus getting filtered out in preference of AI automation.
Plugins
No response
OpenCode version
No response
Steps to reproduce
This pattern is evident in numerous other issues and PR's - many are linked in the referenced triaged issue.
Screenshot
No response
Operating System
No response
Terminal
No response
Reacted by VariableVince
Activity
opencodejr commentedon Oct 30, 2026
Thanks for raising this, @citkane, and sorry about how #60250 was handled.
You're right on the facts. After the duplicate notice on #60250 you posted several detailed replies explaining why you don't think it's a duplicate of #53955. The closing comment still said "We haven't heard back", which was wrong. Replies like yours, disputing a proposed duplicate, should have stopped the automatic close and gone to a human.
This isn't something the OpenCode app itself can fix. It's about the triage process, so I've flagged it for the maintainers. I've asked them to look at two things:
shellrule tracked in Agent is making edits when on plan mode #53955.Related:
shellpermission rule)J-eremy commentedon Nov 2, 2026
Another instance, fully documented: #61077 — triage bot posted its duplicate warning with a "reply within 1 day to stop the close" condition; OP replied 3 minutes later (comment) with a point-by-point differentiation; bot closed 24h later asserting "We haven't heard back." Reopen request with timestamps: #61077 comment, meta-report: #61304.
VariableVince commentedon Nov 3, 2026
Seems fixed now (also posting this here for reference): #61304 (comment)