You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three persistent bugs fixed via source-level patches:
1. oldString === newString throws error (FIXED)
File:packages/core/src/tool/edit.ts
The edit tool now treats identical strings as a no-op instead of throwing ToolFailure. When the LLM generates an edit where oldString equals newString (e.g., to verify current state), it returns a successful no-op response with 0 replacements.
Test updated:packages/opencode/test/tool/edit.test.ts — changed from expecting error to expecting no-op success.
2. SchemaError(Missing key at ["content"]) (FIXED)
File:packages/opencode/src/session/message-v2.ts
Added guard in toModelMessagesEffect to skip assistant messages that only contain reasoning parts with no renderable content (text or tool output). This prevents provider schema validation errors when messages have empty/missing content fields.
3. Reasoning display (ALREADY CORRECT)
Analysis: The CLI already gates reasoning display with --thinking flag (default true in interactive mode, false in non-interactive). The web/desktop UI gates it with showReasoningSummaries prop, defaulting to hide via thinking_mode KV storage.
No source changes needed — the behavior is already correct. Users can disable with --no-thinking in CLI or toggle in UI settings.
Files Changed
packages/core/src/tool/edit.ts — no-op for identical strings
The issue does not use the bug report template. Required fields such as Description, Steps to reproduce, OpenCode version, Operating System, and Terminal are missing.
The content reads like a patch summary or PR description ("FIXED", "Files Changed", "Testing") rather than a report of a bug you are experiencing. Please describe the actual problem you encountered, including how to reproduce it.
Three separate topics are bundled into one issue. Please open separate issues for each distinct bug.
No system or environment information is provided (version, OS, terminal).
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:
Activity
github-actions commentedon Sep 14, 2026
This issue does not fully meet our contributing guidelines.
What needs to be fixed:
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:
SchemaError: Missing key(bash/write/webfetch) #48258: SimilarSchemaError: Missing key at ["content"]on tool callsIf you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Sep 14, 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.