Quick Diagnostics
Run the built-in diagnostic tool:For detailed output, use
bunx oh-my-opencode doctor --verboseInstallation Issues
OpenCode Version Too Old
Problem: Plugin requires OpenCode 1.0.150 or higher. Solution:Plugin Not Registered
Problem: Plugin doesn’t load after installation. Solution: Verify plugin registration in~/.config/opencode/opencode.json:
Configuration File Errors
Problem: JSONC parsing errors or invalid configuration. Solution: Check configuration syntax:- Missing quotes around keys
- Invalid trailing commas in arrays
- Incorrect comment syntax (use
//or/* */)
Provider-Specific Issues
Anthropic (Claude)
Authentication Failures
Problem: “Invalid API key” or authentication errors. Solution: Re-authenticate using OpenCode’s interactive auth:Rate Limiting
Problem: Hitting rate limits during heavy orchestration. Solution:- Check if you’re on max20 mode (20x higher limits)
- Configure agents to use alternative models:
OpenAI (ChatGPT)
GPT-5.3-codex Access Issues
Problem: Hephaestus agent fails with “model not found”. Solution: GPT-5.3-codex requires ChatGPT Plus subscription. Verify access:Google (Gemini)
Antigravity Authentication
Problem: Gemini models require special authentication setup. Solution: Install the Antigravity auth plugin:Antigravity supports multi-account load balancing. Add up to 10 Google accounts to avoid rate limits.
Model Name Mismatch
Problem: Using built-in Google auth model names with Antigravity plugin. Solution: Override model names inoh-my-opencode.json:
google/antigravity-gemini-3-pro(variants:low,high)google/antigravity-gemini-3-flash(variants:minimal,low,medium,high)google/antigravity-claude-sonnet-4-6
Ollama
JSON Parse Error: Streaming Issue
Problem: “JSON Parse error: Unexpected EOF” when using Ollama agents with tool calls. Root Cause: Ollama returns NDJSON (newline-delimited JSON) when streaming, but Claude Code SDK expects single JSON objects. Solution: Disable streaming in your Ollama provider configuration:Agent Issues
Sisyphus Not Working Properly
Problem: Main orchestrator agent produces poor results. Likely Cause: Not using Claude Opus 4.6. Solution: Check your model configuration:Hephaestus Model Errors
Problem: “The Legitimate Craftsman” agent fails to start. Cause: Hephaestus requires GPT-5.3-codex (OpenAI Plus subscription). Solution: Either:- Subscribe to ChatGPT Plus for GPT-5.3-codex access
- Use Sisyphus instead:
ulw <your task>
Hephaestus has no fallback model. It’s specifically designed for GPT-5.3-codex’s capabilities.
Background Agent Failures
Problem: Background agents timing out or not returning results. Solution: Check concurrency limits in configuration:Tool Issues
LSP Server Not Starting
Problem:lsp_rename, lsp_diagnostics tools fail.
Solution:
- Check if TypeScript/language server is installed:
- Verify project has proper language configuration (tsconfig.json, package.json, etc.)
MCP Server Connection Failures
Problem: Built-in MCPs (websearch, context7, grep_app) not responding. Solution: Check MCP configuration:- Network connectivity problems
- MCP server temporarily down
- Authentication issues (for websearch)
Hash-Anchored Edit Failures
Problem: Edit tool rejects changes with “hash mismatch” error. Cause: File was modified between read and edit operations. Solution: This is working as designed. The agent should:- Re-read the file
- Recalculate the edit based on new content
- Apply changes with updated hash references
Hash mismatches prevent stale edits from corrupting files. This is a feature, not a bug.
Performance Issues
Slow Response Times
Problem: Agent responses take too long. Solutions:- Use faster models for utility tasks:
- Disable unused hooks:
- Reduce background agent concurrency:
High Token Usage
Problem: Token costs are too high. Solutions:- Use cheaper models for simple tasks: Explore and Librarian agents intentionally use free/cheap models.
- Enable aggressive truncation:
- Disable context-heavy hooks:
Log Locations
Plugin Logs
OpenCode Logs
MCP OAuth Tokens
Getting Help
If you encounter issues not covered here:- Check the logs:
/tmp/oh-my-opencode.logoften contains detailed error messages - Run diagnostics:
bunx oh-my-opencode doctor --verbose - Search existing issues: GitHub Issues
- Report a bug: Include:
- Output of
bunx oh-my-opencode doctor - Relevant log excerpts (remove sensitive data)
- Steps to reproduce
- Your configuration (remove API keys/secrets)
- Output of
Join the Discord community for real-time help from contributors and users.