how to fix "e.diffs.map is not a function" bug

[natewill]

Description

temporary fix:

1. Open DevTools.
2. DevTools ⋮ → More tools → Request conditions
3. In that drawer, add:
   ://127.0.0.1:4096/vcs/diff
   ://localhost:4096/vcs/diff
4. Turn on “Enable blocking and throttling”
5. Reload the page

That should fix the bug

The problem is that the opencode binary and the hosted ui are out of sync. Once a new release is out the bug should be totally gone.

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

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• Most required fields are empty (_No response_): OpenCode version, Steps to Reproduce, Operating System, and Terminal are all missing
• The description provides a workaround rather than describing the bug itself — please describe what the bug is and how to reproduce it
• The title starts with "FIX" but this should be filed as a Bug Report describing the problem

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:

• TypeError: e.diffs.map is not a function when reopening old browser session #19217: Same TypeError: e.diffs.map is not a function error when reopening old browser sessions — this issue already has active discussion and an assignee

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

[github-actions]

Thanks for updating the issue! The description now has useful content explaining the root cause and a workaround.

However, a few required fields are still missing:

• OpenCode version — which version were you on when you hit this bug?
• Steps to reproduce — what did you do to trigger the e.diffs.map is not a function error? (e.g. opened an old session, did X, saw Y)
• Operating System and Terminal — helpful context for the team to reproduce and verify the fix

Please fill these in so the issue can be properly triaged. The description workaround is great, but maintainers need reproduction context to confirm the fix lands correctly.

[github-actions]

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.