-
Notifications
You must be signed in to change notification settings - Fork 14.2k
Description
Background
First, I want to express my gratitude to the team for the excellent work on OpenCode so far. The project has tremendous potential, and I'm eager to make it my primary AI TUI for development work.
Problem Statement
I'm experiencing challenges with model selection and reliability that are impacting my productivity:
- Inconsistent model performance: Tool call failures are frequent with certain models, leading to unproductive sessions
- Lack of guidance: Without clear documentation on which models work best with OpenCode, I'm essentially guessing
- Switching costs: Mid-conversation model switching often fails, making it crucial to select the right model upfront
- Time and cost waste: Failed interactions result in both wasted API credits and development time
Proposed Solution
I'd like to request the creation of a Model Compatibility Chart that includes:
Core Information
- ✅ Compatibility Status: Fully supported, partially supported, or experimental
- 🧠 Intelligence Level: Relative capability comparison
- 💰 Cost Efficiency: Price per token or relative cost ranking
- 🔧 Tool Call Reliability: Success rate or reliability rating
- 📏 Context Window: Maximum supported context length
- ⚡ Performance: Response speed characteristics
Additional Context
- Known limitations or issues with specific models
- Recommended use cases (e.g., "best for code generation", "best for debugging")
- Community testing results and feedback
Expected Benefits
This would help users:
- Make informed model choices from the start
- Reduce frustration and failed interactions
- Optimize for their specific use cases (cost vs. performance vs. reliability)
- Contribute to community knowledge about model performance
Community Input Welcome
I'd love to hear from other users about:
- Which models have worked best for you?
- Any specific patterns you've noticed with tool call reliability?
- Workarounds or tips for model selection?
Acknowledgment
I understand that model compatibility can be complex and may depend on various factors beyond the project's control. I'm hoping this discussion can lead to better documentation and shared knowledge that benefits the entire community.
Thank you again for your continued work on this project. I'm committed to using OpenCode more consistently and would love to help contribute to its improvement.