-
#1
Model Provider Configuration and Integration Fixes
14 issues · 0.3 demand · Integration
Users want improved configuration support for various AI model providers including OpenRouter, Ollama, Kimi K2, GCP Anthropic, and Azure OpenAI. They also need fixes for issues with environment variables, endpoint configuration, and provider selection loops that prevent smooth integration with these providers.
-
#2
Improve Installation, Configuration, and CLI Flexibility
12 issues · 0.1 demand · Configuration
Users are experiencing installation and setup issues across different platforms (npm, WSL/Linux) while also seeking more flexibility in how they configure and interact with the CLI. Key requests include adding alternative installation methods, fixing 'agent coder not found' errors, improving model configuration options, and enhancing input handling for special characters and multiline content.
-
#3
Provider Integration, Model Support, and Tool Improvements
13 issues · 0.1 demand · Integration
Users want expanded support for AI providers (GitHub Models, Kimi k2, Ollama, Copilot) along with fixes for tool calling, shell timeouts, and install scripts. These improvements address integration gaps and configuration limitations that prevent smooth operation across different environments and use cases.
-
#4
Expand AI Provider Support and Error Handling
6 issues · 0.1 demand · Integration
Users are requesting expanded support for new AI models and tools (Claude WebSearch, Sonnet 4, Opus 4 in Vertex AI) while also asking for better error handling and robustness (MCP timeouts, token limit handling, Ollama validation fixes). These needs focus on improving integrations with various AI providers and preventing application failures during provider interactions.
-
#5
Ollama Local LLM Integration Support
2 issues · 0.1 demand · Integration
Users want official support for using Ollama as a local LLM provider, enabling privacy-focused and cost-effective AI capabilities. They also need graceful handling when Ollama models don't support tool/function calling, rather than experiencing errors or unexpected behavior.
-
#6
Enhanced Authentication Methods and CLI Support
4 issues · 0.1 demand · Developer Experience
Users want more flexible and secure authentication options across different services. This includes supporting environment variable authentication (OPENROUTER_API_KEY), Google Auth tokens for Gemini API, and encrypting stored credentials in auth.json. Additionally, users prefer authentication commands that work directly from the terminal instead of opening a separate UI.
-
#7
Terminal Integration and Compatibility Issues
2 issues · 0.1 demand · Integration
Users are experiencing rendering and keybinding issues when using opencode's terminal with popular terminal emulators (iTerm2) and multiplexers (tmux), as well as alternative shells (fish). These compatibility problems disrupt developer workflows and prevent seamless integration with existing terminal environments.
-
#8
Fix text input and file search usability issues
2 issues · 0.0 demand · Developer Experience
Users are encountering usability issues with basic interactions in the development tool. One issue involves text input behavior where Shift+Enter should create new lines but doesn't work as expected. The second issue relates to file search functionality opening from the wrong directory (/home/ instead of the project directory), making it difficult to find relevant files. Both issues impact developer productivity and workflow efficiency.
-
#9
Fix external LLM model provider integrations
2 issues · 0.0 demand · Integration
Users are encountering bugs when integrating with external LLM model providers like OpenRouter and Ollama. Issues include Zod validation errors and incorrect API endpoint paths that prevent these providers from working correctly. Fixing these integration issues will allow users to successfully use their preferred model providers.
-
#10
Windows Installation and Extraction Compatibility Fixes
2 issues · 0.0 demand · Platform Support
Users are experiencing installation issues on Windows and need better support for bsdtar extraction by avoiding the --wildcards option. These issues stem from cross-platform compatibility problems that prevent smooth installation and extraction on Windows systems using bsdtar.