doom loop. github co-pilot claude opus-4.6. Started to reproduce yesterday. I see it stucks on todo list write. #9274

Closed
opened 2026-02-16 18:12:03 -05:00 by yindo · 2 comments
Owner

Originally created by @dzianisv on GitHub (Feb 13, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

Image Image

/Users/engineer/workspace/codex

session-ses_3a7b.md

/Users/engineer/workspace/opencode
session-ses_3a7c.md

opencode % opencode --version
1.1.65

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @dzianisv on GitHub (Feb 13, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description <img width="4064" height="2294" alt="Image" src="https://github.com/user-attachments/assets/57b1590c-0cd5-4d64-80e0-ac297f389681" /> <img width="1472" height="972" alt="Image" src="https://github.com/user-attachments/assets/469044dd-330f-4217-b791-42a2f212a71f" /> /Users/engineer/workspace/codex [session-ses_3a7b.md](https://github.com/user-attachments/files/25298601/session-ses_3a7b.md) /Users/engineer/workspace/opencode [session-ses_3a7c.md](https://github.com/user-attachments/files/25298750/session-ses_3a7c.md) opencode % opencode --version 1.1.65 ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bugneeds:compliance labels 2026-02-16 18:12:03 -05:00
yindo closed this issue 2026-02-16 18:12:03 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 13, 2026):

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

  • Steps to reproduce is empty. Please describe how to trigger this doom loop and the exact steps taken when it occurs.
  • Operating System is empty. What OS are you running on?
  • Terminal is empty. Which terminal/shell are you using?
  • The issue should clarify the exact conditions that trigger the doom loop related to 'todo list write'.

For bug reports, it's important to provide system information and clear reproduction steps. This helps maintainers quickly identify and fix the issue.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.


This issue might be a duplicate of existing issues. Please check:

  • #12716: Doom loop is not caught when during reasoning or output
  • #12938: Subagents can't use 'todowrite' tool
  • #11112: Always stuck at 'Preparing write...'

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions[bot] commented on GitHub (Feb 13, 2026): <!-- issue-compliance --> This issue doesn't fully meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md). **What needs to be fixed:** - **Steps to reproduce** is empty. Please describe how to trigger this doom loop and the exact steps taken when it occurs. - **Operating System** is empty. What OS are you running on? - **Terminal** is empty. Which terminal/shell are you using? - The issue should clarify the exact conditions that trigger the doom loop related to 'todo list write'. For bug reports, it's important to provide system information and clear reproduction steps. This helps maintainers quickly identify and fix the issue. Please edit this issue to address the above within **2 hours**, or it will be automatically closed. --- This issue might be a duplicate of existing issues. Please check: - #12716: Doom loop is not caught when during reasoning or output - #12938: Subagents can't use 'todowrite' tool - #11112: Always stuck at 'Preparing write...' If you believe this was flagged incorrectly, please let a maintainer know.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 13, 2026):

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.

@github-actions[bot] commented on GitHub (Feb 13, 2026): This issue has been automatically closed because it was not updated to meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md) within the 2-hour window. Feel free to open a new issue that follows our issue templates.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9274