anomalyco / anomalyco/opencode
Usage issue with OpenCode+BMAD+Ollama+Qwen3.5 in VSCode
@kitlangton is already working on this.
Since Aug 1, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Describe the bug
Prompting to BMAD agents in OpenCode chatbox hosted in VSCode. It resulted in "directory not found" issue.
Steps to reproduce
- Install BMAD method (npx bmad-method install) (Version: 6.10.0) with OpenCode selected.
- Install Ollama (Version: 0.32.5).
- Install qwen3.5-9b via Ollama.
- Increase Ollama qwen3.5-9b token window to 256k.
- create Modelfile, with
FROM qwen3.5:9b
PARAMETER num_ctx 256000 - run
ollama create qwen3.5-9b-256k -f ./Modelfile
- create Modelfile, with
- Install OpenCode CLI (Version: 1.18.10).
- Launch VSCode (Version: 1.131.0).
- Open VSCode terminal, enter
ollama launch opencode --model qwen3.5-9b-256k - Enter the following prompt in the OpenCode (Build mode) chat box:
bmad-agent-analyst , I prepared the project context in docs/project_context.md for you to have a brainstorming session. - Observed the following interactions:
- Thought: 1.9s
The user wants a brainstorming session and has prepared project context - I should first read this documentation file to understand what we're
working with before facilitating the session.
I'll help you facilitate this creative problem-solving and brainstorming session! Let me start by reading your project context document, then activate all the requested experts for our
discussion.
→ Read docs/project_context.md
+ Thought: 4.9s
▣ Build · qwen3.5-9b-256k:latest · 51.7s
┃
┃ Please continue.
┃
+ Thought: 3.6s
Excellent! I can see we're tackling a significant technology project.
Let's launch our brainstorming session by activating all your requested panelists:
→ Skill "bmad-party-mode"
+ Thought: 27.9s
│ General Task — Activate AI Panelists
ctrl+x down view subagents
+ Thought: 34.5s
┃
┃ $ python3 << 'EOF'
┃ import subprocess, json
┃ from pathlib import Path
┃
┃ # This project uses Python (uv) - let's try a simpler approach
┃ print("Ready for brainstorming session")
┃ print("\nPanel assembled:")
┃ panelists = [
┃ ("Creative Problem Solver", "Bringing disruptive thinking and alternative approaches"),
┃ ("Innovation Strategist", "Focusing on business model innovation strategies"),
┃ ("Brainstorming Coach", "Facilitating creative ideation techniques"),
┃ ("Analyst", "Data-driven governance metrics & legal framework analysis"),
┃ ("Architect", "Technical design for the monorepo structure"),
┃ ("UX Designer", "Making political accountability appealing and accessible"),
┃ ("Product Manager", "Feature prioritization & user journey mapping") +
┃ ]
┃
┃ print(f"\nContext loaded from: docs/project_context.md ({Path('docs/project_context.md').stat().st_size} bytes)")
┃ EOF
┃
┃ File "", line 15
┃ ]
┃
+ Thought: 22.4s
┃
┃ $ ls /Users/me/Projects/myprj/.bmad/scripts/.py 2>/dev/null | head -5 || echo "scripts directory not found" && ls .agents/skills/bmad-party-mode/references/mode-auto.md 2>/
┃ dev/null | head -1
┃
┃ zsh:1: no matches found: /Users/me/Projects/myprj/.bmad/scripts/*.py
┃ .agents/skills/bmad-party-mode/references/mode-auto.md
┃
+ Thought: 49.0s
▣ Build · qwen3.5-9b-256k:latest · 3m 19s
Expected behavior
I at least expect to see no error like this, at best expect the same experience with BMAD in Cursor.
Environment (if relevant)
- Model(s) used: Ollama + qwen3.5-9b
- Agentic IDE used: VSCode + OpenCode
- BMad version: 6.10.0
- Project language: N/A.
Additional
I am exploring the localized agentic software development setup. So, it is quite new to this configuration. Few troubleshooting resource for reference. Not sure what actual cause, but looks like a misalignment between OpenCode and BMAD. Any help will be appreciated. Thanks.
Plugins
No response
OpenCode version
1.18.10
Screenshot and/or share link
No response
Operating System
Macbook M5 Pro
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.