URGENT #6755

Open
opened 2026-02-16 18:05:10 -05:00 by yindo · 3 comments
Owner

Originally created by @nononodev on GitHub (Jan 18, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

While I was having it help me work on a game I'm making, it gutted half of my fucking code. Luckily, VS Code has an edit history that you can restore from but still, that needs to be fixed as soon as possible. This happened using the macOS app.

Plugins

Grok Code Fast 1

OpenCode version

1.1.25

Steps to reproduce

just ask it to do things one after another and eventually it'll just start removing random shit.
it's done this multiple times on two different projects.

Screenshot and/or share link

No response

Operating System

macOS 26.1

Terminal

No response

Originally created by @nononodev on GitHub (Jan 18, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description While I was having it help me work on a game I'm making, it gutted half of my fucking code. Luckily, VS Code has an edit history that you can restore from but still, that needs to be fixed as soon as possible. This happened using the macOS app. ### Plugins Grok Code Fast 1 ### OpenCode version 1.1.25 ### Steps to reproduce just ask it to do things one after another and eventually it'll just start removing random shit. it's done this multiple times on two different projects. ### Screenshot and/or share link _No response_ ### Operating System macOS 26.1 ### Terminal _No response_
yindo added the bug label 2026-02-16 18:05:10 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 18, 2026):

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

  • #3902: File edits not applied - shows diff output only without modifying files (stops working after 10-15 conversation summaries)
  • #8045: Opencode Doesn't Abide by Prompt or Run Formatter for Ruby Files (edits lines not requested, modifies entire file)
  • #9290: OpenCode nuked my storage (318 GB added) (potential cascading effect from file system issues)
  • #2022: doesnt edit files (building has no effect on files)

These issues describe unintended file modifications and behavior changes. Your issue about code being gutted could be related to the mechanisms described in these reports.

Feel free to ignore if your specific case involves different circumstances.

@github-actions[bot] commented on GitHub (Jan 18, 2026): This issue might be a duplicate of existing issues. Please check: - #3902: File edits not applied - shows diff output only without modifying files (stops working after 10-15 conversation summaries) - #8045: Opencode Doesn't Abide by Prompt or Run Formatter for Ruby Files (edits lines not requested, modifies entire file) - #9290: OpenCode nuked my storage (318 GB added) (potential cascading effect from file system issues) - #2022: doesnt edit files (building has no effect on files) These issues describe unintended file modifications and behavior changes. Your issue about code being gutted could be related to the mechanisms described in these reports. Feel free to ignore if your specific case involves different circumstances.
Author
Owner

@rekram1-node commented on GitHub (Jan 18, 2026):

Not a lot to go off of here, would need to know about the model, the task, what it did, what provider you are using, tools u give it, etc

@rekram1-node commented on GitHub (Jan 18, 2026): Not a lot to go off of here, would need to know about the model, the task, what it did, what provider you are using, tools u give it, etc
Author
Owner

@AndreaBarghigiani commented on GitHub (Jan 19, 2026):

My two cents are... Why don't you instruct your agents (or apply yourself) a proper Git hygene?

  1. Always commit, even small/half-made changes (if you care about history, you can clean up it later).
  2. new feature, new branch

This way you will always be able to know what changed and reverting to previous working code is a breeze.

@AndreaBarghigiani commented on GitHub (Jan 19, 2026): My two cents are... Why don't you instruct your agents (or apply yourself) a proper Git hygene? 1. Always commit, even small/half-made changes (if you care about history, you can clean up it later). 2. new feature, new branch This way you will always be able to know what changed and reverting to previous working code is a breeze.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6755