anomalyco / anomalyco/opencode
[BUG] File changes in multi-stack subdirectory repositories not detected in session (Maven backend, Node frontend, H5 external, Mini WeChat)
@kitlangton 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 in a parent directory containing multiple independent repositories with different technology stacks (Maven backend, Node.js frontend, H5 external browser app, WeChat Mini Program), file modifications within these subdirectory repositories are not detected or displayed in OpenCode session conversations.
Project structure example:
my-project-root/
├── backend/ (Maven/Java project)
│ ├── pom.xml
│ ├── src/
│ │ ├── main/
│ │ └── test/
│ └── .git (or no git)
│
├── frontend/ (Node.js/React/Vue project)
│ ├── package.json
│ ├── src/
│ │ ├── components/
│ │ └── pages/
│ └── .git (or no git)
│
├── h5-external/ (H5 application)
│ ├── package.json
│ ├── public/
│ └── src/
│ └── views/
│
└── mini-wechat/ (WeChat Mini Program)
├── app.json
├── pages/
└── components/
When a session is opened pointing to my-project-root/, and files are modified in any of these subdirectories (e.g., backend/src/main/java/App.java, frontend/src/App.tsx, h5-external/src/index.html, or mini-wechat/pages/index.wxml), these changes are NOT reflected or detected in the OpenCode session conversation.
The issue manifests as:
- File monitor fails to detect changes across different technology stacks
- Session does not show awareness of file modifications in subdirectories
- Users cannot see or reference changes made in backend, frontend, H5, or Mini programs in the same conversation context
- This breaks cross-stack development workflows where a single session should coordinate work across multiple repositories
Plugins
No response
OpenCode version
1.18.13
Steps to reproduce
-
Create or clone a project with multiple subdirectories containing different technology stacks:
backend/with Maven (Java) project structure (pom.xml, src/ directory)frontend/with Node.js (React/Vue/etc) project structure (package.json, src/ directory)h5-external/with H5 application (package.json or plain HTML/JS)mini-wechat/with WeChat Mini Program (app.json, pages/, components/)
-
Open OpenCode and point to the parent project root directory
-
Start a new OpenCode session at the root level
-
Modify files in different subdirectories:
- Edit
backend/src/main/java/App.java(or any Java file) - Edit
frontend/src/App.tsxorfrontend/src/index.js - Edit
h5-external/src/index.htmlorh5-external/src/App.vue - Edit
mini-wechat/pages/index.wxmlormini-wechat/app.json - Save these changes to disk
- Edit
-
Switch back to OpenCode and check if file changes are reflected in the session
-
Try to reference or ask about these modified files in the conversation
Expected behavior:
- OpenCode file monitor should detect changes in all subdirectory repositories regardless of their technology stack
- Session should be aware of file modifications across
backend/,frontend/,h5-external/, andmini-wechat/directories - User should be able to reference and discuss these changes in the conversation
- All subdirectory repositories should be indexable and searchable in the session context
Actual behavior:
- File changes in subdirectory repositories are NOT detected
- Session remains unaware of modifications in
backend/,frontend/,h5-external/, ormini-wechat/ - No indication in file tree or conversation that these files have been modified
- When requesting analysis or explanation of code changes, OpenCode cannot see the modifications from subdirectories
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.