OpenCode bug: lossy read output pushes agents to fall back to bash/PowerShell for file edits
nimao33 · ghdev · 2026-10-11
- A bug report against opencode v2.0.26 on Windows shows the read tool returns content with leading indentation stripped (especially on large files), while edit/write require oldString to byte-match the file exactly, including whitespace and line endings.
- Since agents can't trust read output for edits and edit fails with oldString must byte-match errors, they abandon the dedicated file tools and fall back to bash/PowerShell (cat, Get-Content, Set-Content, heredocs/redirects) to read and write files.
- The reporter suggests read should return faithful content or document normalization, and edit should fuzzy-match whitespace or return a helpful diff on mismatch. The issue has 7 comments and is pending close/triage.
More from coding & agent
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- How do you audit AI agent decisions in regulated workflows? A field survey — Ok_Way_1993 · 2026-10-23