anomalyco / anomalyco/opencode
[BUG] File modifications from other sessions appear unexpectedly in current session version1.18.13
@nexxeln is already working on this.
Since Aug 5, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
When working across multiple OpenCode sessions simultaneously, file modifications made in one session unexpectedly appear or get reflected in another session's workspace. This creates confusion and potential data inconsistency issues, as each session should maintain its own independent file state unless explicitly synced through version control.
The bug manifests when:
- User has Session A and Session B open (either in separate windows or tabs)
- User modifies files in Session A
- User switches to Session B and observes that the file changes from Session A are already reflected in Session B's editor/file tree
- This happens without explicit file synchronization or version control operations
This violates the expected isolation between concurrent sessions and can lead to accidental overwrites or confusion about which session owns which file state.
Plugins
No response
OpenCode version
No response
Steps to reproduce
- Open OpenCode and create or select a project
- Create two separate sessions (Session A and Session B) in the same project
- In Session A, open a file (e.g., src/app.ts or any text file)
- Modify the file content in Session A (add text, change lines, etc.)
- Switch to Session B
- Observe that the same file in Session B now shows the modifications made in Session A
- Verify that no explicit save/sync operation was performed between sessions
Expected behavior:
- Session B should show the original file content or at least require explicit sync
- File changes should be isolated per session unless synchronized through version control
Actual behavior:
- Session B immediately reflects changes made in Session A
- This creates unintended cross-session dependencies
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.